8 ms·
Conspicuously missing scenario: Sandra owns the comic drawing package "stickman" and publishes 0.1.0, 0.9.9 and 1.0.0. A few months/years later, Stick Manufactu
by sangnoir 11y ago
Conspicuously missing scenario: Sandra owns the comic drawing package "stickman" and publishes 0.1.0, 0.9.9 and 1.0.0. A few months/years later, Stick Manufacturing Corp [StickMan(tm)] shows up with their Internet of Sticks support package library to go with their registered trademark and want to publish it as "stickman". What happens next? Do they just hand over the package so Stick Corp can publish a new version? Does NPM inc rename Sandra's "stickman" to something else? what happens to Julie's "comic" package that depends on "stickman^0.9.9" when the package is handed over?
- laughinghan 11y agoTheir previous post does specifically address this, in its own bolded bullet-point: ○ The dispute resolution policy minimizes disruption. Transferring ownership of a package’s name doesn’t remove current versions of the package. Dependents can still retrieve and install it. Nothing breaks. Had Azer taken no action, Kik would have published a new version of kik and everyone depending upon Azer’s package could have continued to find it. It was abrupt unpublishing, not our resolution policy, that led to yesterday’s disruptions. http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
- catnaroek 11y agoDo old versions of the package remain under ownership of the original author? Let's assume I publish a package “foo”, and the name is later transferred to someone else. Will npm make it perfectly clear that the versions I published are my intellectual property, rather than that someone else's? My English reading comprehension isn't precisely the best, but I'm pretty sure this concern isn't addressed in the text you cited.
- laughinghan 11y agoThis concern is indeed not addressed in the text I cited. However, though my English reading comprehension isn't precisely the best either, I'm pretty sure this concern wasn't brought up in your comment that I was replying to when citing that text. I don't see this concern addressed in their Package Name Disputes document at all: https://www.npmjs.com/policies/disputes https://www.npmjs.com/policies/disputes Perhaps they'd be delighted if you brought it up in the public forum they linked to at the end of the blogpost? https://github.com/npm/policies/issues/44 https://github.com/npm/policies/issues/44
- catnaroek 11y ago> Perhaps they'd be delighted if you brought it up Or perhaps they would not. After all, my question is a very natural question to ask, and they don't seem to have given it any thought, as if they were ignoring a particularly big elephant in a small and cramped room. It seems deliberate to me. And, even under the unlikely assumption that it isn't deliberate, it says a lot about npm Inc's lack of empathy for their own users. In any case, not being a JavaScript programmer myself, let alone an npm user, I can't bring myself to care enough to comment on their GitHub issue.
- laughinghan 11y agoHonestly I don't think it's as natural a question as you think it is (I haven't noticed anyone else bring it up on HN or in that GitHub Issue), and I don't think it's hard to answer, either. To make clear a package you published is your intellectual property, you're expected to use the "author" field in package.json; it's also common to mention your name in the README. The versions you published would continue to name you in the "authors" field and in the README, rather than someone else. Perhaps NPM thinks that suffices. (You might do neither of those things, and the someone else might use your name to publish later versions of the package, or a random person might use your name to publish a completely different package. But these problems not affected by the policies being discussed, nor really have anything to do with NPM seeing as the same thing could happen on GitHub (someone else can publish a repo and attribute you as the author; also, will GitHub make perfectly clear that a repo you publish is your intellectual property, rather than someone else's?).)
- catnaroek 11y ago> will GitHub make perfectly clear that a repo you publish is your intellectual property, rather than someone else's? My question doesn't apply to GitHub, because GitHub doesn't transfer your repositories to other people unless you tell it to.
- laughinghan 11y ago
- steveklabnik 11y agoI 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.
- btilly 11y agoHowever 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.
- revicon 11y agoThis is why setting version numbers in your dependencies is important.
- steveklabnik 11y agoYeah, if I was King of npm, I would have made shrinkwrap mandatory from day 1.
- mmanfrin 11y agoThis is literally the situation that began all these events.
- steveklabnik 11y agoSure. 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.
- denom 11y agoThis 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!
- jowiar 11y agoIANAL, but StickMan(tm) probably won't be able to claim a trademark on StickMan in the context of software. Trademarks generally require being the first to use a name within a specific market. See the assorted Apple Computer vs. Apple Records suits that happened once Apple Computer entered the music business. It was perfectly kosher for there to be "Apple Records" and "Apple Computer", but once "Apple Computer" started selling music, they were violating Apple Records' trademark. The reason kik was an issue isn't just that "Kik" is a trademark. It's that "Kik" is a trademark referring to a piece of software.
- orik 11y agoreplace stickman with Kik and the problem still exists.
- jsprogrammer 11y ago"Kik" is not just a trademark referring to a piece of software. It refers to a very specific type of software. KIK Interactive, Inc. has described it in many words, but they are all somewhat similar to: >Computer software for use with mobile devices, namely, computers, personal digital assistants (PDAs) and mobile phones for downloading, displaying, transmitting, receiving, editing, extracting, encoding, decoding, playing, storing and organizing text, sound, images, audio files and video files The `kik` package was software that was used with other devices for other purposes. KIK Interactive hasn't even been able to produce a specific Trademark that the `kik` package would have infringed upon.
- awjr 11y agoThe real problem is the namespace issue that seriously needs sorting out. com.sandra.stickman would be different to com.stickmanufacturingcorp.stickman npm is growing hugely. It needs to sort out the domain space issue quickly.
- paulhodge 11y agoDots are allowed in the package name, so there's nothing stopping someone from having a package named "com.sandra.stickman", if they are really inclined to do that.
- TheDong 11y agoYou're missing the point. Being intentionally obtuse adds nothing.
- woah 11y agoThat's why it's best not to force people to namespace with backwards website addresses.
- paulhodge 11y agoIf I was being obtuse then it was unintentional. It was a real suggestion. If people really want reverse TLD names then they should do it, and if the community likes it, it will catch on. FYI there are already some package names out there with ".com" on the end.
- steveklabnik 11y agonpm literally supports namespaces already https://docs.npmjs.com/misc/scope https://docs.npmjs.com/misc/scope And, it's not actually clear that a namespace would have been enough had a lawsuit actually been filed.
- awjr 11y agoscopes are ways of grouping functionally related packages. Not sure that is the same thing. You may be right about the lawsuit.
- monochromatic 11y ago"We've made lots of changes to make things better going forward. What's that? No, of course the changes don't address what actually caused all the issues everybody is talking about."
- laughinghan 11y agoIt was abrupt unpublishing, not our resolution policy, that led to yesterday’s disruptions. http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
- monochromatic 11y agoProximate cause, maybe.
- gcb0 11y agothat's still the one sided argument the commenter above you highlighted. just saying it twice from the same month doesn't make it less one sided.
- laughinghan 11y agoMaybe I don't know what you mean by "above you", but, what? The arguments above me I've seen are "missing scenario: ..." and "they didn't address what actually caused all the issues". Which is a one-sided argument is identical to mine?
- NTripleOne 11y agoWhat happens next is Sandra throws her toys out of the pram and gives the middle finger to 'the (stick)man'.
- diskcat 11y agowe should have a first come first serve policy unless stated otherwise. it would be very rude to take the name 'stickman' from an author just because some big important webscale global internet of things unicorn multi-national 1000billion users app company has an app with the same name. why can't they just call it stickman_app and not steal other people's land? although we should also implement LVT to fix the landgrabbing issue