2 ms·
That's interesting; so if I have a developer make $50K worth of changes to some GPLv2 program, I still can't charge more for distributing it than the cost of th
by kazinator 5y ago
That's interesting; so if I have a developer make $50K worth of changes to some GPLv2 program, I still can't charge more for distributing it than the cost of the distribution errand.
The way you get paid is not to do the changes until/unless you have some work contract in place beforehand. If you've already made the changes, you mustn't try to get paid for them.
I didn't even notice that all these years.
- fineIllregister 5y agoI think that's a misreading. That clause only limits additional fees charged to existing users for access to the source code. You can make the changes and charge whatever you want for the software. When the user requests the source code, as is their right, for that you can only charge the physical costs. The intent is to prevent expensive source code fees from being used as an end-around the source disclosure requirements. It also makes sure the distributor can cover the cosrs, but no more than that.
- kazinator 5y ago> I think that's a misreading. Right? But since that's a legal document, possible misreadings can end up exploited somehow. Even something like an ambiguous comma can be at the crux of a dispute https://www.nytimes.com/2018/02/09/us/oxford-comma-maine.html https://www.nytimes.com/2018/02/09/us/oxford-comma-maine.htm...
- GoblinSlayer 5y agoYou can release your changes under a proprietary license, then relicense as GPL when you receive money. If you don't release it into general availability, you can simply revoke it.