2 ms·
Well, I contributed to the dual licensed project, only to see the company increasing the price of their (somewhat related) monetized project 7 fold or so, screw
by megous 10y ago
Well, I contributed to the dual licensed project, only to see the company increasing the price of their (somewhat related) monetized project 7 fold or so, screwing people over on the related product. Of course the contributors get nothing for their copyright assignment. It's like thank you for your contribution to our documentation system, now pay 7 times more for our main product you're also using.
I'm wary of these schemes as a potential contributor. It limits the reciprocity.
I'm much happier with projects that don't require free copyright assignment from their contributors.
- geokon 10y agoMaybe I'm not understanding your point... you only pay if you want to use it in a closed source capacity. The alternative (just a vanilla copy-left license) would mean it's simply impossible to use in a closed source project at all. So if all you do is write open source software, there is no difference for you. And if you write closed source software (or some project/client suddenly requires it of your for some reason) then you have something you can do. It seems like a win-win?