Source
Veteran OT User
"Bruh!" indeed. I suggest you read and understand that license. I actually screenshotted your reply as I find it incredibly comical. You can edit and redistribute the code. You can even charge users for a binary. But the source codes have to be released. By making it public, it means you make it available to others and not just yourself (that includes if anyone is able to purchase it from you). You can use modified GPL 2.0 and GPL 3.0 licensed software by yourself. But if you ever(!) plan to share it with anyone, either for free or paid, the source codes has to be made available. And it's not just to the buyer of the software, but anyone who will use it as the end customer. In other words, everyone, as it can not be guaranteed it's never shared by the customer.
View attachment 84295
Forking GPL project: Do I have full rights on the new fork or still dependencies with the original owner(s)
I am considering the creation of a fork to a small project licensed under GPLv2, and I have some very specific questions I did not manage to answer in my research on various sites and forums. When I
softwareengineering.stackexchange.com
The short answer: When you fork an existing project, you generally do not have permission to change the license nor do you get copyright on the code you copied over.
You do have the copyright on any (nontrivial) modifications or additions that you make.
Couple of my own points:
1. In my case I don't use TFS, and otclient is licensed under MIT, so I'm not at all worried for myself. However,
2. If any license told me to strip naked and give away all my properties, or equally if it "just" told me to release all source code that I've chosen to distributed to some either as a binary or source code in part or as a whole for sale or for free, sorry but you can meet me in court.