Re:Write libraries instead of services, where possible
by mhh__ on Tuesday March 09, 2021 @11:39AM
(#26400518)
GPLv3 with a commercial exception. Corporate suits don't like the GPL, so if they buy a commercial licence they support the project without having to redistribute (You can also offer support)
[ Parent
| on HN ]
Re:Write libraries instead of services, where possible
by sokoloff on Tuesday March 09, 2021 @02:12PM
(#26402579)
I think AGPL is the much more effective open source license if your intention is to have corporations too afraid to use it under the open license and to negotiate a commercial exception license.
Plenty of companies will use GPL code, especially for hosted software.
Re:Write libraries instead of services, where possible
by alcover on Tuesday March 09, 2021 @11:54AM
(#26400695)
GPLv3 with a commercial exception
Thx. Do you mean GPL + my custom addendum ? How do you write it if you're not versed in `legalese` jargon ?
Re:Write libraries instead of services, where possible
by mhh__ on Tuesday March 09, 2021 @11:59AM
(#26400765)
https://www.fsf.org/blogs/rms/selling-exceptions for a little philosophy behind it, however it will always be the GPL OR a commercial licence rather than an amalgam of the two
Re:Write libraries instead of services, where possible
by ben509 on Tuesday March 09, 2021 @12:20PM
(#26401022)
Notably, the FSF recommends against[1] modifying the GPL. And, you'd want to hire a lawyer to go over whatever scheme you're thinking of.
It's easier to draft a separate license agreement if you're the sole copyright holder.
If you're not the sole rights holder, if your project contains other GPL code, you'll need permission from the authors to license under terms other than the GPL. That would include patches from other authors, unless they sign the rights over to you.