4 ms·
My suggestion was to add a page allowing maintainers to sell licenses. I think dual licensing can work really well if 1) there’s a very easy and trusted way to
by sudhirj 8y ago
My suggestion was to add a page allowing maintainers to sell licenses. I think dual licensing can work really well if 1) there’s a very easy and trusted way to buy licenses -with strong predefined terms set by a trusted third Party like Github, and 2) if there are well written and understood commercial licenses available for use that businesses can trust on sight.
Every oss project trying to make money by dual licensing currently sets up their own payment system, and winds up writing their own commercial license because the well known ones like MIT, Apache or BSD don’t work (if a business buys one of those licenses they can just make a competitor to your project). Because each project writes their own license, businesses need to waste time reviewing each license carefully. It’ll be so much easier if there’s a Github Commercial License that’s Apache 2.0 plus a non compete and no resale clause.
- fxfan 8y agoThis is the best suggestion I've seen and yet the one which Microsoft cannot do for tear of people running after then with pitchforks.
- sudhirj 8y agoGithub could do it. Doesn't look they're rebranding into Microsoft Code Office Space (TM) any time soon. And one would assume they'd put the licenses on Github as well, so you could suggest changes and sell your project on whichever version of the license you want. What Github would bring to the table are easy marketplace dynamics, trust, and a team of lawyers capable of writing good licenses. Also, the same code analysis tools that check for security problems in your dependencies could also license checking. There's a very compelling use case for businesses if all their code hosted on Github can 1) automatically check for license violations and 2) just pay for all licenses on a single screen with a single click.