Tuesday, April 12, 2016

Your code on Github - What itz worth?

I am an open source proponent and contributor. As a hobbist I build lot of cool tools and apps which I keep posting onto my GitHub handle. However, to be frank with you so far I never posted any license agreement along with my code. May be I am bit lazy to spare time and research on the open source license models and identifying one which is suitable for me.

Recently while searching in Open Source Licensing models and implications I came across Steven Burnap  answer on stack exchange thread "Open source code with no license… can I fork it?". Further exploration of GitHub opensource license page  I found...

What happens if I don't choose a license?

You're under no obligation to choose a license. It's your right not to include one with your code or project, but please be aware of the implications. Generally speaking, the absence of a license means that the default copyright laws apply. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work. This might not be what you intend.

Even if this is what you intend, if you publish your source code in a public repository on GitHub, you have accepted the Terms of Service which do allow other GitHub users some rights. Specifically, you allow others to view and fork your repository within the GitHub site.

If you want others to use, copy, modify, or contribute back to your project, we strongly encourage you to include an open source license.

This made me realize the code I was posting on GitHub with the intent of attracting tech enthusiast to use it in the best interest of technical community was not serving the purpose.

No comments:

Post a Comment