Hacker News new | ask | show | jobs
by benatkin 4709 days ago
Nope. AGPLv3 is very different from GPLv2. Also the wishes of the creators of Linux and git make the GPLv2 more comfortable to me. Companies that have a dual-licensing model with GPLv2 and a paid proprietary license may try to stretch the meaning of the GPLv2 to make it more restrictive.

The problem with oauth.io is I could spend time learning it to use it on a personal project and then not be able to apply the same knowldege on a client project where the client doesn't find the copyleft situation acceptable.

2 comments

You like to get to use some software for free, but you also want to use it so others might not see your modifications.

How exactly is this different from GPLv2, if the web service you were writing was going to be shipped on a router? and why should you be allowed to use someone else code but then prevent others to see your modifications?

May be they will go like MongoDB, RethinkDB, OpenERP, SugarCRM as well as WURFL, they all now utilize the AGPLv3 as a vehicle for dual commercial licensing.
Doing what SugarCRM is doing would be better than what they're doing right now. Many companies would find both AGPL and SaaS against their policies but would be OK with paying for non-copyleft software that they can install on their own server.