-
-
Notifications
You must be signed in to change notification settings - Fork 33
Description
As far as I see, this project does not specify the license of its source code, nor does it include a LICENSE file. According to the copyright laws (Berne convention) and the GitHub TOS, one cannot modify this project's code without the danger/liability of being prosecuted by violating the implicit "All rights reserved" copyright.
This includes not only the source code of the website, but also the snippets published there. Technically speaking, everyone who copies those snippets could be breaking a law, since they are not explicitly open-source. One could argue that snippets of this size cannot be protected by copyright, but I believe it's better to be safe than sorry.
I propose this project adopts an open-source license. I noticed that it used to be open-source, but the license was removed in c01695b. Is there a reason why?
Making the project open-source is not as simple as one might think. Given that there is no license file AND no contributors' agreement (DCO or similar), every contribution belongs to their respective contributor. You cannot, legally speaking, relicense the whole project as MIT, because some people might be against it and would want to keep the restrictive copyright. Such contributions must either be marked as such (making the project not 100% open-source), or removed. You'll have to get individual permission from every contributor.
I can help you with the whole ordeal; I have been collaborating on the relicensing of a bigger project in the past.
P.S. I am not a lawyer.