Open Source Stack Exchange is a question and answer site for people organizing, marketing or licensing open source development projects. It only takes a minute to sign up.
Sign up to join this community
I have written a simple shell in C. I started my work when I had an OS lab. I did this as an assignment. I tried to implement cd, pipe, I/O redirection, background process, jobs, running system binaries, exit etc. Now, I want to open a project on my shell in GitHub so that anyone can contribute and beginner students can get help to start.
But, I don't want anyone to copy my code for his/her assignment. Is there any license that prohibits copying the code for assignment?
It seems like you want the legal power to bring a lawsuit against any student who uses your code in any capacity related to schoolwork. I think this is a bad idea for two reasons.
First: this would not a FOSS license: it violates Freedom 0 ("The freedom to run the program as you wish, for any purpose") and point 6 of the OSD ("The license must not restrict anyone from making use of the program in a specific field of endeavor.") It will be incompatible with any copyleft license like the GPL and only add to license proliferation. There are existing licenses that will meet your needs without FOSS-incompatible terms (see below).
Second: I understand you want to discourage plagiarism, but schools and universities already have academic honor codes and cultural norms that strongly prohibit plagiarism. It is not your responsibility to enforce this, and any anti-academic licensing terms will likely only cause harm by disallowing innocent cases: what if a course instructor wants students to build off of your work for an assignment so they can learn how to read and extend existing code?
In any case, virtually any FOSS license will require redistributors to preserve your original copyright notices. If a student removes those in an attempt at plagiarism, then they will be in violation of the license anyway. There is no need for you to target plagiarism specifically. (And if the student doesn't remove those copyright notices, then I suspect the instructor will have a lot of questions about why someone else's name is on the project!)
I don't like that someone copy my code for his/her assignment. Is there any license that prohibit copying the code for assignment?
This question seems to conflate plagiarism with the overlapping but distinct concept of copyright infringement. Briefly:
A given act can be plagiarism, copyright infringement, both, or neither. Here is a Venn diagram showing the intersection between the two concepts:
/-----------\ /--------------\
/ \/ \
/ /\ \
/ / \ \
/ / \ \
| Plagiarism | Both | Copyright |
\ \ / infringement /
\ \ / /
\ \/ /
\ /\ /
\-----------/ \--------------/
For your purposes, preventing plagiarism is all that you need. For the sake of a complete answer, however, I will also discuss the prevention of copyright infringement. This will allow you to take a "belt and braces" approach.
As apsillers already indicated, any reputable educational institution will have policies against plagiarism and will enforce those policies. Any student who cheats by submitting your work as though it were their own should be caught and punished (e.g. by having their grade for that assignment reduced to zero).
In other words, preventing students from committing plagiarism in their assignments is a responsibility that rests with the students and the school, not with you.
In most countries, copyright exists in any sufficiently original work that has been placed into a fixed form (e.g. written down). By default, this legally bars people other than the copyright holder (e.g. the author, or the entity that commissioned the work) from copying or adapting that work for any purpose except for the very limited purposes of "fair use" or "fair dealing".
In order to give people greater access to (copies of) that work, the copyright holder must typically license the work in some way.
With proprietary software, this is done with a EULA, which typically grants very limited rights to the licensee, such as the right to perform (run) the work, for some limited purposes. I personally would not recommend the use of such a license in general, and especially not in your case, as its restrictions would be excessive. Many free software licenses (see below for examples) would meet your needs just as well, and would be more beneficial to the community.
For a student to submit proprietary software as though it were their own would typically be an act of plagiarism and of copyright infringement.
With free (libre) software, this is done with a license that upholds the Four Freedoms:
None of these freedoms allows a recipient to claim authorship or copyright in the original work. As such, most popular free software licenses (e.g. the AGPLv3, the GPLv3, the ALv2, the 2-, 3-, and 4-clause BSD licences, or the MIT License) are suitable for satisfying a copyright holder's wish that a recipient should not be able to claim authorship or copyright of the work. I would suggest you use one of these licenses: preferably one of the first three, as they are the ones that best account for edge cases.
For a student to submit free software (i.e. software provided to them under such a license) as though it were their own would typically be an act of plagiarism and of copyright infringement.
The most permissive possible license is a public domain dedication. This waives the right of the author or copyright holder to the fullest extent permitted by law. In the context of software, you could view this as meaning that arbitrary additional freedoms are granted in addition to the Four Freedoms above, i.e. as a very permissive form of free software licensing.
This is still quite rare, but you can do it if you want to, e.g. by applying the CC0 license.
For a student to submit a public domain work as though it were their own would typically be an act of plagiarism, but not of copyright infringement.
When publishing code to GitHub, you grant GitHub a license to use that code in certain ways. This license exists in addition to any other license (e.g. the GPLv3) that you might have applied to the work, and has been the subject of debate in the free software community.
For example, if you publish your work to GitHub, other GitHub users are in turn licensed to fork that work on GitHub's website, regardless of any other copyright restrictions on the work.
This is unlikely to affect your concern about plagiarism, for the reasons given earlier. Even so, as you stated you hope to publish to GitHub and expressed concerns about copying of your work, it seemed appropriate to mention it.