GitHub metrics for Optimism's Retro Funding 5

[ccerv1]

Q&A for the Retro Funding 5 impact metrics. You can view the source code here.

The following fields are included in the GitHub-based metrics analysis for Retro Funding 5:

1. artifact_url: Repository URL associated with the project based on the application. A project may have multiple repos in its application.
2. project_name: Name of the project.
3. project_category_id: Category ID of the project (1, 2, 3).
4. num_contributors: Total number of contributors before August 1, 2024. A contributor is defined as any non-bot user that has contributed to the repository (since 2015) by committing code directly to a repository, opening an issue, or opening/reviewing a pull request.
5. num_trusted_contributors: Number of trusted contributors before August 1, 2024. A subset of the contributors defined above, this is the number of contributors that are also in the top 420 of the OpenRank developer trust score.
6. num_contributors_last_6_months: Number of contributors over the period Feburary 1, 2024 - August 1, 2024.
7. num_stars: Total number of stars as of September 23, 2024.
8. num_trusted_stars: Number of stars from trusted users before August 1, 2024. A subset of the stars defined above, this is the number of stars from users that are also in the top 420 of the OpenRank developer trust score.
9. trust_weighted_stars: This metric is a percentage score between 0% and 100%, representing the sum of the reputation share of the developers who starred the repo. If all developers in OpenRank developer ranking have starred a particular repo, the metric's value is going to be 100% for this particular repo. The more and the higher ranked developer who starred the repo, the higher the percentage value, the higher impact and quality of this repo. We calculate this metric by first calculating every developer's reputation share (%) based on their OpenRank score, then sum them up if they starred the target repo.
10. num_forks: Total number of forks as of September 23, 2024.
11. num_trusted_forks: Number of forks from trusted users before August 1, 2024. A subset of the forks defined above, this is the number of forks from users that are also in the top 420 of the OpenRank developer trust score.
12. trust_weighted_forks: This metric is a percentage score between 0% and 100%, representing the sum of the reputation share of the developers who forked the repo. If all developers in OpenRank developer ranking have forked a particular repo, the metric's value is going to be 100% for this particular repo. The more and the higher ranked developer who forked the target repo, the higher the percentage value, the higher impact and quality of this repo. We calculate this metric by first calculating every developer's reputation share (%) based on their OpenRank score, then sum them up if they forked the target repo.
13. trust_rank_for_repo_in_category: Ranking of the repository's OpenRank trust score within its category. A score of 1 indicates the highest ranking repo in its category.
14. age_of_project_years: Age of the project in years, measured from the project's first public commit to August 1, 2024.
15. license(s): License(s) used by the project.
16. application_id: Application ID in the sign-up and voting UIs.