Closed nexdrew closed 8 years ago
Hmm... Interesting. :)
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). :sunglasses:
Closed with #8.
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!