is there a license for this library? #5

RandomEtc opened this Issue Sep 2, 2010 · 3 comments

3 participants


I may have overlooked it but I don't see one. Perhaps the MIT license as used by node.js itself would be appropriate?


it is MIT, I keep forgetting to add the headers :(


Excellent, thank you!


Your response to this issue makes your intent clear -- this is an MIT licensed project. But the code does not make that as clear. Someone just asked me today what the license for this was (since we want to use it), and it took me a while to figure this out.

People will be more inclined to use this if you make it clear. so let me suggest that you include the text of the MIT license in a file (call it LICENSE) that you put it in the project root.

Also, you might want to add a header on each text file that has your copyright statement (why not - it's yours to do):
Copyright (c) [year] [your name or your company's name]. All rights reserved. Copyrights licensed under the MIT License.

You could then add other copyrights to it (e.g. this file contains code that is Copyright (c) [year] [another name]). And if this gets too complicated (e.g. you have many files in your project), then just create one file (call it readme, authors, copyrights etc.) where you list the names of all the 3rd party entities which you have to credit in this code. And then keep that in the project root too.

I hope this helps.

@ciaranj ciaranj added a commit that referenced this issue Apr 8, 2012
@ciaranj Addresses issue #93, adds *explicit* licensing information
This library has always been MIT licensed (see issue #5 for the earliest
question on this.)  This commit merely adds an explicit complete licence file in
the root of the sourcetree, and adds a line to the package.json file
(thus coupling the sourcecode to github *sigh* )
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment