Ideas for new visualizations

[JustinGOSSES]

No description provided.

[JustinGOSSES]

• Cord diagram of what user or orgs commit to code owned by what other user/orgs.
  • This will show members of the community who work on stuff other than their own.
• Visualization to show in grid form what code is used by others. In other words, tool X is used by tools Y,W,Z and tool A is used by tools G, T, D, Z.
  • This would presumably show what projects are component tools that can be used as building blocks as opposed to to end-user tools.
• What code projects in the list share the most number or % of dependencies with either a selected tool in the metadata or a list of dependencies provided via CSV, requirements.txt or other method?

[JustinGOSSES]

Create repo personas and categorize each repo as a type. Something like below but need to do more work to establish the boundaries are easy to calculate as a metric without gaps between.

• More than 10 contributors last 12 months, more than 100 stars and 90% of issues and pull requests stay open less than 2 months and 95% get a first response within 3 days and 70% within 1 day and merges are done by at least 3 different person with no person having more than 75% = attracted community and response excellent and shared maintainer workload

• More than 10 contributors last 12 months, more than 100 stars and 90% of issues and pull requests stay open less than 2 months and 95% get a first response within 3 days and 70% within 1 day but response is one person 75% of the time = attracted community and response excellent but potentially at risk for burnout

---

• More than 10 contributors last 12 months, more than 100 stars but 90% of issues and pull requests stay open less than 2 months and 95% get a first response within 3 days and 70% within 1 day = attracted community and response excellent

• More than 10 contributors last 12 months, more than 100 stars and more than 20 PRs overall but PR response time is = attracted community but response time lags

---

• More than 10 contributors last 12 months, more than 100 stars but more than 11 PRs open and more than 20 PRs overall = _attracted community but PR left open _

• More than 10 contributors last 12 months, more than 100 stars = attracted community

---

• Between 2 and 6 contributors after first 90 days less than 4 issues or PRs in the last 12 months = smaller project now slowed
• More than 1 contributor but less than 6 contributors within past 18 months and more than 20 issues or PRs in the last 18 months = smaller project

---

• zero contributions in last 12 month but had a contribution after first 3 months. grounded definitely
• zero contributions in last 6 month but had a contribution after first 3 months. grounded probably
• zero contributions after 3 months on GitHub = never grew community

---

• single contributor, more than 4 activities in past 12 months and has been more than 3 months on GitHub = solo project

---

• new to GitHub within 3 months = too little information to judge

[JustinGOSSES]

Things to use as metrics.... some of these are already captured, are captured but need calculated, or still need collected from the GitHub API.

• time:
  • date of data fetch is before or after 90 days repo started on GitHub (true/false)
  • calculate other metrics within the past 365 days
  • calculate other metrics within the first 90 days
• Contributors
  • number of contributors within first 20 days (assuming these are team members)
  • number of contributors within first 90 days (any additional to first 20 days may be new members)
  • number of contributors all time (additional contributors may be new team members or external contributors attracted to the project.
• Pull Requests
  • number within first 20 days
  • number within first 90 days
  • number overall
  • number within last 365 days if more than 1 year old.
• Issues
  • number within first 20 days
  • number within first 90 days
  • number overall
  • number within last 365 days if more than 1 year old.
• Stars
  • number within first 20 days
  • number within first 90 days
  • number overall
  • number within last 365 days if more than 1 year old.
• Total activity (Stars, Issues, Pull Requests)
• Ratios:
  • issues/pull requests
  • open/closed issues
  • open/closed pull requests
  • pull requests open after X unit of time
  • issue open after X unit of time.