2 ms·
It seems like a personal choice to me. If you want companies to use your code internally, and are okay with the fact that they might make improvements that they
by _delirium 15y ago
It seems like a personal choice to me. If you want companies to use your code internally, and are okay with the fact that they might make improvements that they don't release back (or think that voluntary releases will be sufficient), then GPL or BSD/MIT is fine. If you don't want to allow for proprietary forks of stuff used in webapp backends, then AGPL is a better choice. If you have a different set of preferences about how people use your code than either of those, you can keep it proprietary and just negotiate custom licenses with potential users.
AGPL seems like a particularly reasonable choice if you're running a SaaS and want to release your code, but also want to make sure no competitor can use your code as a starting point from which to leapfrog you without releasing the improvements back for your own use. That's the approach gitorious takes, for example. Of course, the other way to keep competitors from leapfrogging you with your own code is not to release it at all, or release it with a proprietary license--- the approach github and Dropbox and many other SaaS take. From that perspective, AGPL is at least more liberal a license than the "no code release" license.