Simple email application for Android. Original source code: https://framagit.org/dystopia-project/simple-email
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

130 lines
6.0 KiB

  1. npm-disputes(7) -- Handling Module Name Disputes
  2. ================================================
  3. This document describes the steps that you should take to resolve module name
  4. disputes with other npm publishers. It also describes special steps you should
  5. take about names you think infringe your trademarks.
  6. This document is a clarification of the acceptable behavior outlined in the
  7. [npm Code of Conduct](https://www.npmjs.com/policies/conduct), and nothing in
  8. this document should be interpreted to contradict any aspect of the npm Code of
  9. Conduct.
  10. ## TL;DR
  11. 1. Get the author email with `npm owner ls <pkgname>`
  12. 2. Email the author, CC <support@npmjs.com>
  13. 3. After a few weeks, if there's no resolution, we'll sort it out.
  14. Don't squat on package names. Publish code or move out of the way.
  15. ## DESCRIPTION
  16. There sometimes arise cases where a user publishes a module, and then later,
  17. some other user wants to use that name. Here are some common ways that happens
  18. (each of these is based on actual events.)
  19. 1. Alice writes a JavaScript module `foo`, which is not node-specific. Alice
  20. doesn't use node at all. Yusuf wants to use `foo` in node, so he wraps it in
  21. an npm module. Some time later, Alice starts using node, and wants to take
  22. over management of her program.
  23. 2. Yusuf writes an npm module `foo`, and publishes it. Perhaps much later, Alice
  24. finds a bug in `foo`, and fixes it. She sends a pull request to Yusuf, but
  25. Yusuf doesn't have the time to deal with it, because he has a new job and a
  26. new baby and is focused on his new Erlang project, and kind of not involved
  27. with node any more. Alice would like to publish a new `foo`, but can't,
  28. because the name is taken.
  29. 3. Yusuf writes a 10-line flow-control library, and calls it `foo`, and
  30. publishes it to the npm registry. Being a simple little thing, it never
  31. really has to be updated. Alice works for Foo Inc, the makers of the
  32. critically acclaimed and widely-marketed `foo` JavaScript toolkit framework.
  33. They publish it to npm as `foojs`, but people are routinely confused when
  34. `npm install foo` is some different thing.
  35. 4. Yusuf writes a parser for the widely-known `foo` file format, because he
  36. needs it for work. Then, he gets a new job, and never updates the prototype.
  37. Later on, Alice writes a much more complete `foo` parser, but can't publish,
  38. because Yusuf's `foo` is in the way.
  39. 1. `npm owner ls foo`. This will tell Alice the email address of the owner
  40. (Yusuf).
  41. 2. Alice emails Yusuf, explaining the situation **as respectfully as possible**,
  42. and what she would like to do with the module name. She adds the npm support
  43. staff <support@npmjs.com> to the CC list of the email. Mention in the email
  44. that Yusuf can run npm owner `add alice foo` to add Alice as an owner of the
  45. foo package.
  46. 3. After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
  47. and Alice can't come to any sort of resolution, email support
  48. <support@npmjs.com> and we'll sort it out. ("Reasonable" is usually at least
  49. 4 weeks.)
  50. ## REASONING
  51. In almost every case so far, the parties involved have been able to reach an
  52. amicable resolution without any major intervention. Most people really do want
  53. to be reasonable, and are probably not even aware that they're in your way.
  54. Module ecosystems are most vibrant and powerful when they are as self-directed
  55. as possible. If an admin one day deletes something you had worked on, then that
  56. is going to make most people quite upset, regardless of the justification. When
  57. humans solve their problems by talking to other humans with respect, everyone
  58. has the chance to end up feeling good about the interaction.
  59. ## EXCEPTIONS
  60. Some things are not allowed, and will be removed without discussion if they are
  61. brought to the attention of the npm registry admins, including but not limited
  62. to:
  63. 1. Malware (that is, a package designed to exploit or harm the machine on which
  64. it is installed).
  65. 2. Violations of copyright or licenses (for example, cloning an MIT-licensed
  66. program, and then removing or changing the copyright and license statement).
  67. 3. Illegal content.
  68. 4. "Squatting" on a package name that you plan to use, but aren't actually
  69. using. Sorry, I don't care how great the name is, or how perfect a fit it is
  70. for the thing that someday might happen. If someone wants to use it today,
  71. and you're just taking up space with an empty tarball, you're going to be
  72. evicted.
  73. 5. Putting empty packages in the registry. Packages must have SOME
  74. functionality. It can be silly, but it can't be nothing. (See also:
  75. squatting.)
  76. 6. Doing weird things with the registry, like using it as your own personal
  77. application database or otherwise putting non-packagey things into it.
  78. 7. Other things forbidden by the npm
  79. [Code of Conduct](https://www.npmjs.com/policies/conduct) such as hateful
  80. language, pornographic content, or harassment.
  81. If you see bad behavior like this, please report it to <abuse@npmjs.com> right
  82. away. **You are never expected to resolve abusive behavior on your own. We are
  83. here to help.**
  84. ## TRADEMARKS
  85. If you think another npm publisher is infringing your trademark, such as by
  86. using a confusingly similar package name, email <abuse@npmjs.com> with a link to
  87. the package or user account on [https://www.npmjs.com/](https://www.npmjs.com/).
  88. Attach a copy of your trademark registration certificate.
  89. If we see that the package's publisher is intentionally misleading others by
  90. misusing your registered mark without permission, we will transfer the package
  91. name to you. Otherwise, we will contact the package publisher and ask them to
  92. clear up any confusion with changes to their package's `README` file or
  93. metadata.
  94. ## CHANGES
  95. This is a living document and may be updated from time to time. Please refer to
  96. the [git history for this document](https://github.com/npm/cli/commits/latest/doc/misc/npm-disputes.md)
  97. to view the changes.
  98. ## LICENSE
  99. Copyright (C) npm, Inc., All rights reserved
  100. This document may be reused under a Creative Commons Attribution-ShareAlike
  101. License.
  102. ## SEE ALSO
  103. * npm-registry(7)
  104. * npm-owner(1)