Is there a license that says most people can do whatever you want with my stuff but if Microsoft (example) uses it to make 100 million dollars, I want to negotiate for a piece of it? That's really the question everyone is asking, although they're too shy to say it, because wanting to make money off of your stuff is considered bad form in certain quarters.
Personally, even if a huge company with a lot of money was using one of my projects as an integral part of a moneymaker, I'd be happy with a very, very fair (for them) royalty that they would probably not even consider significant. But if you use the MIT, the question of negotiating anything doesn't even come up. To be clear, I want a license that is not infectious at all. That lets people use, modify, redistribute, all that good stuff. But just leaves open the door that if someone gets really rich using my project, I can benefit from coming up with the idea and doing the work. Is there a license that represents this? On Friday, December 14, 2012 10:38:05 PM UTC-5, Forrest L Norvell wrote: > > On Fri, Dec 14, 2012 at 7:29 PM, David Herron > <da...@davidherron.com<javascript:> > > wrote: > >> I'm curious about the preferred license for modules that are distributed >> through the npmjs.org repository > > > We discussed this a bit at NodeConf summer camp this year, and the > consensus was pretty strongly in favor of BSD or MIT licenses, or at least > pretty liberal, commercial-use friendly licenses (including the Perl and > Apache licenses). > > In particular is there any legal barrier to using GPL in such modules? >> >> As far as I understand it, the legal barrier would be whether a module >> which uses a GPL'd module is derivative of that module. I don't think that >> it would be, but then the LGPL license does exist for a reason. >> > > Isaac can speak to this more authoritatively than I can, but npm itself > prescribes / proscribes no particular licenses. You could attach GPL3 > licenses to your modules if you wanted, but uptake would probably be > hampered, especially if there were some kind of associated Canonical-style > contributor's agreement. Node is still pretty much the wild west, and it's > tough to say if today's random hack project might not become tomorrow's > startup idea, and I think most devs want to keep their options open. > > F > -- -- 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.
