3 ms·

I'd go with GPL as many comments mentioned here. If you are slightly paranoid about someone stealing the code and making a commercialized version (which happen

I'd go with GPL as many comments mentioned here. If you are slightly paranoid about someone stealing the code and making a commercialized version (which happens a lot with VLC), then I suggest you separate some of the functionalities into modules, in which parts are GPL'ed, and others are made private. Perhaps the UI and basic functionalities (aka lite version) could be made OSS, but some more advanced features are not included in the source, such as filter or scrub view. It would make it virtually impossible to make a clone, but you also get the benefit of people contributing and learning from the code from the OSS version.

yboris 8y ago
Thank you for the advice. In my case it feels like it would take quite a bit of effort to pull out features from the software and make a stripped-down version available. My primary reason for wanting to share the code is that perhaps it will be a useful place for others to learn some things (though I don't think my code is stellar / exemplary and I know it has some serious shortcomings). I guess it isn't a big problem if someone releases a clone of my app for free as long as I somehow can require (request) they always link back to the original on their website and in the app itself. But I'm not eager to chase people around and pester them if they don't comply. I'm thinking I might wait for a full year since release (until February 2019) and just put out the whole code on GitHub with a 'free to do anything' license and a personal request that people always include a link to the original in the compiled app and on/through whatever websites they share it on.