2 ms·
>Major respect for recognizing that and not doing anything like dual licensing or CLAs It's nice, but in my opinion there is nothing wrong with doing it either
by Hitton 6y ago
>Major respect for recognizing that and not doing anything like dual licensing or CLAs
It's nice, but in my opinion there is nothing wrong with doing it either. It might be even good thing if it ensures stability of the developer. If it turns out the original developer with dual licence/CLA is no longer good, community can continue from the AGPL version on its own and if the original developer wants to incorporate these new community changes, the AGPL will "infect" the dual licensed version.
- wegs 6y agoMy opinion is that we've been burned by this enough times that it ain't worth it. Most recently, Oracle rolled back Java. If I'm buying into an open ecosystem, it's because I want an open ecosystem. I don't want a use-open-to-gain-market-dominance-and-than-milk-customers ecosystem. AGPL is ideal for things I don't need to link proprietary code to. What I most want is a plausible, paid, AGPL competitor to GSuite.