What if all the top 100 npm maintainers changed everything in npm to gpl? Would it still be poison then?
Its their work, they dedicated to it. You are using it, for free. Yes, some modules are interchangeable but not all, And normally they were a lot of work to write. Finishing your program would be near impossible without all these modules. And you are worried cause lawyers tell you crap? Tell them don't like gpl contact the license holder to acquire a comercial license. The email of the author is almost always in the license file. Just don't come and talk about poison and how to avoid it. You and your decisions are (your) problem, not the person that made something for free and offered you for a license that does not require any counterpart unless repackage and sell the source (if gpl, others dont even require this which is amazing and what most people do in the node community) I think the real issue is how much some developers feel entitled to things. Put yourself in check and ask yourself questions: have i ever contributed back? Have i ever supported an open source project? if not have i ever offered help (or monetary compensation) to the owner of an open source project? If the answer is no, at least dont say things are poison. Entitled? Be graceful instead Nuno Ps. Another topic of discussion would be how the only way to make money in open source is support. What does that tell us about ourselves as programmers and most of all humans? On Dec 15, 2012, at 7:41 AM, Austin William Wright <[email protected]> wrote: > On Saturday, December 15, 2012 12:36:16 AM UTC-7, Jonathan Dickinson wrote: >> On Saturday, 15 December 2012 06:38:14 UTC+2, Raynos wrote: >>> I have zero dependencies on GPL modules for that reason and won't use any >>> npm modules that are under the GPL licence. >> >> This brings up a good point: we should maybe be able to blacklist licenses >> in the NPM client. If you want to write copyleft-free code you should be >> able to configure NPM to reject copyleft modules so that you don't poison >> your own codebase. > As I mentioned, you can't "poison" your code base merely by listing code as a > dependency, submodule, or anything else. You must, at a very minimum, > actually be distributing the code in question. > -- > 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 -- 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
