A license is something that is granted by the author at distribution-time, it need not be included in the package contents. If an author wholly owns the copyright on their work, they can offer the program to you under any license they want, regardless of what the file inside the repository or package says.
So that paragraph doesn't actually, really, do anything - it's not a clause/stipulation (that is to say, it has no "teeth"). Granted that the author is able to make the full text of the license available upon request, a package that the author says is MIT licensed, even without including the full text, is still MIT licensed. On Wednesday, March 27, 2013 9:12:03 AM UTC-7, kapouer wrote: > > Hi, > saying the author's work is MIT licensed is not enough, > the full text of the license must be there too, as written > in its second paragraph : > > The above copyright notice and this permission notice shall be > included in all copies or substantial portions of the Software. > > I write this here because i see countless node modules in this case, > whose authors probably believe their software to have a very liberal, > free, and open-source license - but they have de facto no license at all. > > Jérémy. > > PS: because i see one module per day in this situation > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
