3

For context, I have couple repositories on github, some of which showcase solutions to course projects or homeworks, while others - are created "for fun" (for example implementation of tail command in Python). They're by no means "high-grade" examples of code. There's no intent to distribute code in those repositories for commercial or non-commercial use. The entire goal is to just show to others what I've done.

According to Wikipedia definition,

[a] software license is a legal instrument (usually by way of contract law, with or without printed material) governing the use or redistribution of software.

So this reads to me that even if I don't intend to distribute my software for others to use, if someone does copy it off the repository and uses it, I may want to add a license to explicitly state what I am OK with and not OK with the licensee doing.

At the same time, github states:

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.

This by contrast seems to imply that I can showcase my code just fine, but if someone copies the code to try it out, they're therefore breaking copyright law (which kinda sounds like "look but don't touch").

Hence the question, for code that is intended to be showcased and not necessarily distributed or used by others, does the code still have to be licensed in some way, shape, or form ?

1

If your intention is to have a "look but don't touch" policy on your code, then you indeed don't need to choose a license for it.

You might want to make it clear that this is your code and that you hold all the rights, by adding a comment to your files like

Copyright (C) 2020 Sergiy Kolodyazhnyy
All rights reserved.

In fact, by putting your code up on GitHub, you have given out some license to it: You have given GitHub a license to store and reproduce your code and you have given other GitHub users a license to fork your code. Both of these licenses are granted by agreeing to GitHub's Terms-of-Service and subsequently uploading the code.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.