|
|
|
|
|
by sqs
3864 days ago
|
|
Sourcegraph CEO here. Fair Source is intended to allow companies to distribute both the product and source code, and still charge for the product. Fair Source is not an open-source license. Just as with GPL, there are restrictions around your usage of the code that are intended to produce longer-term benefits (in our case, making sure we can build the best product and have a sustainable business). We have had it reviewed thoroughly by multiple lawyers in several countries, and it was drafted by Heather Meeker, who is extremely well respected. I am not a lawyer myself, but the "hypothetical loophole" scenario you described would involve you making a derivative work of our code—kind of like photocopying Harry Potter and adding some doodles in the margins, and reselling that. That would not circumvent any license or copyright situation. |
|
So you're comparing someone who forked your project to add what could be major features, to someone doodling in the margins of Harry Potter? That's a really optimistic view of the open source community there. But I understand what you're saying, I'm just used to forks being a common practice in the FOSS community, so I expected them to be better accounted for.
You still haven't made it clear what would happen in the case of a fork. Even if they kept it under your license, who gets the money? How do they get paid? How are terms agreed to? Can it not be forked at all?
EDIT: This really applies to any modifications, essentially, say I make some modifications to your code, under what terms am I allowed to distribute them? Is the only way I can go to license them back to you without seeing any of this "fair" profit myself? What if you don't like them and decide not to use them can I redistribute them for free or fee on my own? Is there any way to make the forking and distribution of modifications as casual as it is with so many open source projects under other licenses today?