Licence change

[lexoyo]

As I am rewriting a lot of code in Silex and all of what will remain will be code I wrote, I am thinking I should change the licence

1- GPL makes it impossible to write closed source application which embeds Silex
2- GPL makes it impossible to write closed source plugins to use in Silex
3- GPL is great but I read that it does not fit the SaaS model

What do you think?
cc @JbIPS @clemos @arielsom @yanhick @silexlabs/silex-labs-contributors @tariqbenezza

[clemos]

What other licence do you consider ? MIT ?
I guess it's the good old Free vs Open Source debate 😅

[JbIPS]

What about aGPL? -- Jean-Baptiste Richardet Le 18 mars 2020 16:46:59 GMT+01:00, "Clément Charmet" <notifications@github.com> a écrit :

…

What other licence do you consider ? MIT ? I guess it's the good old Free vs Open Source debate 😅 -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1012 (comment)

[lexoyo]

What other licence do you consider ? MIT ?

why not

I guess it's the good old Free vs Open Source debate sweat_smile

I would love silex to be foss but one should be able to create proprietary plugins

[lexoyo]

What about aGPL?

i thought it is not ok to create proprietary plugins ?

[lexoyo]

I believe that this is what we need

https://en.wikipedia.org/wiki/Mozilla_Public_License

https://git.libreoffice.org/core/+/refs/heads/aoo/trunk/automation/source/app/testbasi.cxx

https://hg.mozilla.org/mozilla-central/file/tip/uriloader/prefetch/OfflineCacheUpdateChild.cpp
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=blob;f=modules/swfutils/src/java/flash/util/StringJoiner.java;h=3f85b2d4052006f8d35b7f1fb741ca758fa744f3;hb=refs/heads/develop

[JbIPS]

LGTM