4 ms·
No problem. Yes, I never thought of that! What is the practical benefit of having a license here and which one should I choose?
by darajava 2y ago
No problem. Yes, I never thought of that! What is the practical benefit of having a license here and which one should I choose?
- Jitnaught_ 2y agoWithout a license your repo is technically not open-source, only source-available. A license says what people are allowed to do with the code, so if you don't add a license, they're not allowed to do anything.
- darajava 2y agoThat's great, I've added an MIT license. https://github.com/darajava/reel-control/commit/4d014f578b935e4267da727b483c8762f65f0ced https://github.com/darajava/reel-control/commit/4d014f578b93...
- captn3m0 2y agoHaving a license clarifies what permissions are you giving to someone who downloads your code. The practical benefit is that others can clearly contribute back or build on your work without any legal concerns. Something like MIT gives them permission to do anything as long as attribution is maintained, while avoiding liabilities. But there are others you can pick: https://choosealicense.com/ https://choosealicense.com/
- darajava 2y agoThank you! MIT license added. https://github.com/darajava/reel-control/commit/4d014f578b935e4267da727b483c8762f65f0ced https://github.com/darajava/reel-control/commit/4d014f578b93...
- freedomben 2y agoWithout a license, legaly nobody can do anything with the code. The license is essentially the way that you communicate what you will allow people to do with it. For a project like this, I would strongly recommend an MIT license. That will essentially allow people to use the code and modify it, contribute back to it, and otherwise distribute their changes.