| > You can use a GPL library without making changes and contributing anything upstream which is fine - your usage of GPL software doesn't affect anyone else. If you decide to charge for it, that's OK too - since if the market exists for such software, the price would equalize to the break-even point of the cost of production. > You can use a GPL library internally and make changes without contributing anything upstream If it's "internal", aka, not visible to the outside world, then that's fine too. There's no effect from anyone else's perspective. > You can use a GPL library, make changes ... share the changes with the 3rd parties This is the point i was trying to make - in this case, where you make changes, you have to share it. Even tho it's just the 3rd party, this 3rd party has the right to distribute these changes. And anyone that has access to the software is also the 3r party. So, in other words, if you have visible effects to the outside world with your (changed) GPL software, you are effectively bound to contribute those changes for free, or relicense with the owner to hide those changes. |