[Feature Request] Display Active Maintainer Statistics to Identify Projects Needing More Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- analytics
Research direction
Start by reviewing the linked projects health dashboard and the repository dashboard described in the issue. Determine where maintainer activity data would come from and define a page or section that reports active-maintainer counts, recent commits or merged pull requests, and average response time; done means these statistics are displayed clearly for each project.
Written by the indexing model from the issue text.
Description
Issue Description
https://all.devstats.cncf.io/d/53/projects-health-table?orgId=1
Currently, the repository dashboard does not provide specific statistics on active maintainers. It would be beneficial to display information about each project's number and activity of maintainers. This will help users identify projects, like etcd, that may need additional maintainer support.
Proposed Solution
- Develop a feature that pulls and displays data on the active maintainers for each project.
- Present the information in a clear and easily accessible format, such as a dedicated section within the repository dashboard or a separate tab/page.
- Include relevant statistics, such as the number of active maintainers, their recent activity (e.g., commits, merged PRs), and average response time to issues/PRs.
Benefits
- Provides users with insights into the maintainer support for each project.
- Helps identify projects needing additional maintainers to ensure continued development and support.
- Enhances overall transparency and understanding of project health and sustainability.
- Dominant language
- Shell
- Stars
- 130
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cncf/devstats
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
-
blocked enhancement
-
blocked enhancement
-
bug question
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100