4 ms·
> if an open source tool can't do X well, then whenever somebody needs or wants or gets paid to do X, that can be committed to that tool by the people whose car
by squeaky-clean 4y ago
> if an open source tool can't do X well, then whenever somebody needs or wants or gets paid to do X, that can be committed to that tool by the people whose career involves applying that tool.
More recently it seems like the plan is to fork the project, apply your change, and offer it an AWS branded alternative
- specialist 4y agoYup. If someone's profitting from my work, I want my cut. That's why I keep asking about royalty schemes. Common for all other forms of IP. Curiously absent from FOSS.
- PeterisP 4y agoWell, nothing "curiously" about it, it's because "FOSS" is a label we explicitly made to refer to the forms of IP where this is absent, where it's free as speech and they don't need to ask your permission to run the code for any purpose. You definitely can have a royalty scheme that ensures you get a cut if someone's profiting from your work, that's a reasonable desire, but then we wouldn't say that your work is FOSS.
- specialist 4y agoWhat about dual licensing? That's already pretty common. I'd like someone smart about these things to create the boilerplate royalties license complimenting, or compatible with, or whatever, some FOSS licenses. Say Apache License v2.0. IIRC, it was ElasticSearch that recently tried to thread this needle. Maybe I'm overthinking this. I tried to read up about royalties, find some model language, etc. Alas, IANAL, so got lost pretty quickly.