On Tue, Feb 2, 2010 at 8:59 AM, A.L.E.C <[email protected]> wrote: > A.L.E.C wrote: >> Thomas Bruederli wrote: >> >>> What do you think about this? Please feel free to comment the above lines. > > And a list of libs that we're using in Roundcube with their licenses: > > PEAR PHP > Net_Socket PHP > Net_SMTP PHP > Mail_Mime BSD > MDB2 BSD > Auth_SASL BSD > Net_Sieve BSD > tnef_decoder GPL > Iloha libs GPL > html2text GPL > enriched GPL > jQuery GPL/MIT > TinyMCE GPL > googiespell GPL > others are "free" >
Good list, Alec. As for the RoundCube license. Even though I'm not a huge fan of anything-GPL, the license shouldn't be an issue. The only parts that are effected are plugins and skins which people write and even then, the GPL just forces them to release these bits to their customers with full source code. They don't have to release anything to the public. And they can even charge for GPL software. I don't see a real issue even for commercial entities, not sure what kind of IP some people would try to hide in a plugin or a wordpress skin. The only issue is that e.g. when I purchase a plugin or a skin, I'm allowed to distribute it free of charge as well - GPL. As for AGPL - I think even if we would get everyone to agree, that would be a huge setback for RoundCube's adoption, because then the "advantages" of the GPL (especially for commercial entities) would be void. All in all, I think it's next to impossible to switch RoundCube from the GPL to something more liberal or restrictive now because it requires that everyone who sent in a patch in the past will ACK the license change. I could totally see that we make the core LGPL, in factor, I'd +1 that right away because it would allow people to distribute plugins using their own maybe more liberal or more proprietary license. On the other hand, this kind of change could also create a license chaos because right now, it's all 1 - GPL. Till _______________________________________________ List info: http://lists.roundcube.net/dev/
