-
Notifications
You must be signed in to change notification settings - Fork 88
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
[NOTICE] For any repo requests refined community OpenRank. #1387
Comments
This issue has not been replied for 24 hours, please pay attention to this issue: @gymgym1212 @xiaoya-yaya @xgdyp |
It may not be fair to the repo which is not installing the open-digger-bot. The reaction data would be more important to the repo in my mind. |
Actually the reactions data will only be used in community OpenRank calculation which is used for calculating contribution of each developer in a single community. So whether a repo installed open-digger-bot or not, it will not effect the global OpenRank of the repo at all. |
NOTE: After the Community OpenRanks of 650k repos are released, we may also create a demo and update the docs: https://github.com/X-lab2017/open-digger#for-repos So exciting :) |
Description
OpenDigger right now provides community OpenRank results for several repos like X-lab projects, Sealos and 20 projects under Alibaba contribution leaderboard.
In the future, any repo could request the refined community OpenRank, where refined means reactions data which is not in the GitHub log data will also be collected to correct the result.
The only way to get refined community OpenRank is installing open-digger-bot to the repo. After the installation, backend data service will collect all the issues/pulls' reactions for the repo and store into the graph database for further calculation.
Additionally, repos not installing open-digger-bot will also be included in community OpenRank calculation without reactions correction which means we can get all the community OpenRank results for all the repos on GitHub.
The text was updated successfully, but these errors were encountered: