Hacker News new | ask | show | jobs
by thasian 2367 days ago
Thank you for the comment. I learned a few things about licensing. The main reason I chose GPL was because I don't want someone else building a commercial closed source application based on my app; others can still fork the project and modify it.

I don't intend to release this app on any other platform but others who want to may feel free - I think GPL allows for this. In the end, I don't really care what others do with my app as long as they consult me about what they want to do with it, which MIT is too loose for. If others want to release an app based on mine, they can feel free.

1 comments

> The main reason I chose GPL was because I don't want someone else building a commercial closed source application based on my app; others can still fork the project and modify it.

GPL is generally the best choice for that.

> In the end, I don't really care what others do with my app as long as they consult me about what they want to do with it

There’s no popular license that I know of that requires people to tell you about their fork. They can just release it and publish the code along with it.

Sure there is: CDDL. It requires one to give the changes back, as opposed to passing them to whoever they distribute to.