-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull authors from commit history? #12
Comments
@noffle It's not just looking up the last npm publisher. It's looking up everyone who had npm publish permission at the time of the last release. As a concrete example, take a look at the response from http://registry.npmjs.com/standard/latest at the "maintainers" key. That's what we're using. I wonder what the tradeoffs of using git history vs. npm publisher history are. Seems like you'd pull in more casual contributors which could be good. But I wonder if folks would game this by just getting in trivial things like copyright year updates into popular projects so they can show up as a suggestion in |
Hey I do this but I'm not trying to game the system... It's just that a lot of projects have typos in their docs 😃 Forked repos in DecemberThat being said, I probably should not receive donations for adding a couple lines to the docs. |
This is going into bigger scope, but this project feels like it's on the same spectrum as @kemitchell's License Zero and sustain. I think |
There's something really powerful and magical about saying "give $10 to my dependencies" and have that money actually trickle down to those authors & contributors all the way down. (In theory!)
|
what about defining a custom edit: sorry i didn't see #2 😅 |
This is more involved, but it'd be cool if all contributors to a project got pulled in as well as the last npm publisher!
The text was updated successfully, but these errors were encountered: