4 ms·
The vast majority of what I've written and released is under the Apache License, V2.0. I've also put some stuff out under the LGPLv2. I tend to favor fairly l
by mindcrime 16y ago
The vast majority of what I've written and released is under the Apache License, V2.0. I've also put some stuff out under the LGPLv2. I tend to favor fairly liberal licenses, but I could see the merits of going GPL at some point.
What I don't ever intend to use are any "badgeware" licenses (CAPL, I'm looking at you) or the Affero GPL. The AGPL just seems wrong to me. I get what they're trying to do, but I just don't see hosting a service running software "X" as constituting "distributing software X."
- _delirium 16y agoI'd use the AGPL if I open-sourced a non-trivial webapp most likely, especially if it were a business rather than a side project, but probably not if it were just libraries or something of that sort. It makes sense to me as a GPL analog in the webapp/SaaS space. I think of the GPL as informally saying that you can do whatever you want with my code, but once you ship a derivative work, you have to release source to your modifications too. In webapp space, what does it mean to "ship" a derivative app? Seems like "launch a public service" is the way you ship, since nobody is selling CD-ROMs with thick-client apps on them. In practical terms, a common alternative to AGPL is just to not release at all, because many SaaS providers are worried that releasing their code will make it too easy for someone to set up an improved rival service, beating them using their own code as a starting point. For example, Gitorious is AGPL, but Github is closed-source.
- mindcrime 16y agoI'd use the AGPL if I open-sourced a non-trivial webapp most likely, especially if it were a business rather than a side project, but probably not if it were just libraries or something of that sort. Fair enough. I could see how someone in that position would find the AGPL appealing.