You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on conversation here and similar idea here, I created all-stars which contains pre-fetched author data for the maintainers of the top depended packages on npm. Credits could leverage this to achieve the following, without hitting the network or sacrificing speed:
Remove duplicate listings of some popular authors
So that, e.g., the following can be identified as the same person and grouped/listed once:
jonschlinkert github@sellside.com (12 packages)
Jon Schlinkert (12 packages)
...
Isaac Z. Schlueter i@izs.me (19 packages)
isaacs isaacs@npmjs.com (7 packages)
...
juliangruber julian@juliangruber.com (4 packages)
Julian Gruber mail@juliangruber.com (4 packages)
...
jonathanong jonathanrichardong@gmail.com (3 packages)
Jonathan Ong me@jongleberry.com (2 packages)
Provide more info, like GitHub username, for several authors
E.g. something like this (or credits-cli could just use a different style for GitHub usernames):
Isaac Z. Schlueter isaacs@npmjs.com [GitHub: isaacs] (26 packages)
Jon Schlinkert github@sellside.com [GitHub: jonschlinkert] (24 packages)
Julian Gruber julian@juliangruber.com [GitHub: juliangruber] (8 packages)
Jonathan Ong jonathanrichardong@gmail.com [GitHub: jonathanong] (5 packages)
The initial release of all-stars includes data for 251 authors of the top 150 depended packages.
Please take a look and let me know what you think. Thanks!
The text was updated successfully, but these errors were encountered:
What should happen to the people that are not included in all-stars?
I will check you project in detail soon, I've got a lot to do on the weekend. ;) Please feel free to ping me again, when you haven't heard something after a few days. :)
For maintainers that are not found in all-stars, I would just stick with the current functionality - no gain or loss there.
Over time, PRs could be created against all-stars to add missing folks - no changes to credits would be required at that point (besides maybe bumping the dependency). 😎
Based on conversation here and similar idea here, I created all-stars which contains pre-fetched author data for the maintainers of the top depended packages on npm. Credits could leverage this to achieve the following, without hitting the network or sacrificing speed:
Remove duplicate listings of some popular authors
So that, e.g., the following can be identified as the same person and grouped/listed once:
Provide more info, like GitHub username, for several authors
E.g. something like this (or credits-cli could just use a different style for GitHub usernames):
The initial release of all-stars includes data for 251 authors of the top 150 depended packages.
Please take a look and let me know what you think. Thanks!
The text was updated successfully, but these errors were encountered: