If you, the recipient, believe the terms are ambiguous, then contact the author and receive the full license (as I described), but that doesn't change the fact the package is still licensed for your use.
On Wednesday, March 27, 2013 10:00:55 AM UTC-7, Dick Hardt wrote: > > Actually, that is not true. There are several MIT licenses, so unless the > actual license text is included, it is ambiguous what the license is: > > http://en.wikipedia.org/wiki/MIT_License#Various_versions > > Having a LICENSE file in the package makes it clear what the license is, > or alternatively stating the full license in the README.md > > -- Dick > > On Mar 27, 2013, at 9:55 AM, Austin William Wright < > diamon...@users.sourceforge.net <javascript:>> wrote: > > 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 nod...@googlegroups.com <javascript:> > To unsubscribe from this group, send email to > nodejs+un...@googlegroups.com <javascript:> > 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 nodejs+un...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
