I forked someone's repo and added functionality. The amount I contributed is just under half of all the functionality it now has.
In the fork in package.json
, his name is still in the author field.
Should I change the author field to myself and add him as a contributor to the contributors
field? Or should I leave the author field AS-IS and add me as a contributor?
author
key is not flexible enough. It should accept also an array of authors. In other cases, theauthor
is merely the «creator» of the package, but not the author of most of the code. Not even 1%. The code will be totally transformed and won't be distributed in NPM. Example: project starters/generators... Starting a site with Gatsby, it generates a base project with the official boilerplate, but there is already anauthor
in package.json. Then what? – Tentationcontributors
key (which is not even mentioned in official npm page about package.json) is like: «Hey, this people also did some work here»... but I'm still the main author. It's a difficult matter, I guess. Sorry for this not being an answer, but even more questions, @christiaan-westerbeek. Anyways, in that case, more or less 50% of code, you both should be oncontributors
(but there is the thing thatcontributors
is not even parsed by NPM... As example,eslint
package. List 3 persons (notauthors
key, notcontributors
not github.com/eslint/eslint/graphs/contributors). – Tentationmaintainers
key is mentioned. Maybe that key would be more appropiate for this (seems like it should have the same shape thancontributors
key). – Tentation