▲ | matheusmoreira 5 days ago | ||||||||||||||||||||||
The maintainer's leverage is severely diminished due to the fact MIT licensed versions of the software exist. Only new code will be copylefted so it will be easier to cut him out of the picture. This is why developers should AGPLv3 their personal projects from day one. Then others can't fork it under another license. Even if they choose AGPLv3, the creator still maintains full freedom since they own the copyrights. They can make a commercial version if they want to. They can even relicense it under favorable terms to companies for a licensing fee. Everyone else must abide by the copyleft rules. If they don't like it, let them pay hundreds of thousands of dollars a year for their own developers to make their own in house proprietary version. | |||||||||||||||||||||||
▲ | rlpb 4 days ago | parent | next [-] | ||||||||||||||||||||||
> Even if they choose AGPLv3, the creator still maintains full freedom since they own the copyrights. Only if they either refuse all contributions, require contributions to be made under an MIT license or similar (and then immediately relicense back to AGPLv3 before publishing), or require a CLA. I'm all for personal projects to be licensed AGPLv3, but we must acknowledge that the moment you take others' AGPLv3 contributions, in practice you won't be able to do those other things. | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | overfeed 4 days ago | parent | prev [-] | ||||||||||||||||||||||
> This is why developers should AGPLv3 their personal projects from day one. That would be detrimental to "growth hacking" GitHub stars and gaining traction. One can't be paid without baiting users first. | |||||||||||||||||||||||
|