3 ms·
I've noticed that you didn't put any open-source license with your code, which is understandable since it's your first. :) So my question (likely to others) is
by Timothee 16y ago
I've noticed that you didn't put any open-source license with your code, which is understandable since it's your first. :)
So my question (likely to others) is this: when you do that kind of week-end projects, do you put a license with it and if so, which one?
The reason I'm asking is I also put some code on GitHub from little projects, but without any license for now, mostly because I didn't really care either way. But I imagine it'd make sense to know about a few good ones to go with and use that for most cases. (for example, it seems to me that the MIT license has got some popularity over the GPL, but I'm not sure why)
- jackolas 16y agoHonestly, any license is better than no license.
- Macha 16y agoMIT vs GPL in a nutshell: MIT: here's my code, you can do what you want, just don't be a dick. GPL: here's my code. If you use it to build something on top of, your code must be open source two. And here's a long list of ways of bypassing that that aren't allowed.
- joshholat 16y agoI hadn't even thought about that to be honest with you. What's the process for even putting a license on your code? Do you just say so in the README file or something?