News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @05:48PM (#11385183)
I don't personally think that npm can tell you what would happen, because this form of situation really relies on the exact details of what's going on. Especially since trademark is about confusion, the specifics really count. Your "stickman" case might be a "no", but a "microsoft" package might be a "yes". Or not. It depends.
Re:Changes to Npm's unpublish policy by btilly on Tuesday March 29, 2016 @05:58PM (#11385261)
However this case matters because it closely resembles what got a developer pissed off enough at npm to unpublish hundreds of modules.

And the current changes don't help with the pissed off developer scenario much. Because a pissed off developer can simply publish broken versions of packages instead of unpublishing them, and still break the world.

Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @06:15PM (#11385373)
Yeah, if I was King of npm, I would have made shrinkwrap mandatory from day 1.
Re:Changes to Npm's unpublish policy by revicon on Tuesday March 29, 2016 @11:02PM (#11386674)
This is why setting version numbers in your dependencies is important.
Re:Changes to Npm's unpublish policy by mmanfrin on Tuesday March 29, 2016 @06:27PM (#11385447)
This is literally the situation that began all these events.
Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @06:32PM (#11385485)
Sure. But the parent seems to be asking for a general example of what would happen in such a dispute; unlike the rules for unpublish, they require human judgment, and so you can't actually give a single answer here.
Re:Changes to Npm's unpublish policy by sangnoir on Tuesday March 29, 2016 @07:06PM (#11385689)
> But the parent seems to be asking for a general example of what would happen in such a dispute

Actually my question (I'm parent) is also on the technical level, since I'm pessimistically assuming the lawyers will win everytime.

If Sandra renames her package (voluntarily or not) - will the old versions with contested name resolve correctly stickman v0.99? Or will they be gone forever? Will Stick Corp inherit management of the old versions? Is it a good idea? Who will manage point-release vulnerability upgrade - Sandra or Stick Corp? etc. There are a lot of questions relating to the original quagmire that NPM Inc is not answering.

Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @07:14PM (#11385735)
Yeah, sounds like you should ask in that linked thread. Assuming the lawyers win, it's not clear to me either.
Re:Changes to Npm's unpublish policy by denom on Tuesday March 29, 2016 @08:16PM (#11386051)
This is exactly what politically empowered people and lawyers are good at figuring out. Let the law and motivated individuals sort it out in institutions that society has designated. What we are seeing now are the consequences of conflicting unilateral actions.

The goal of Npm should be to insure that any software built using their tools enjoys uninterrupted historical continuity and progress. The technical challenge is as serious as the political complexity--exactly as it should be! Rash and sudden movements (yanking version, letting squatters snap up names) are undesirable because they do not honor the spirit of necessity:

Move only when necessary, and then move decisively, and always fight to ensure the historical continuity of the software. If people are confused, illustrate the precept in your actions and instruct the people!