Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Top Issues GitHub Action #1488

Merged
merged 2 commits into from
Apr 14, 2024

Conversation

FrankRay78
Copy link
Contributor

@FrankRay78 FrankRay78 commented Mar 7, 2024

spectre.console contributions are largely made by a small set of dedicated contributors/maintainers, whom have less time than open issues (fairly common occurence in the OSS world). As such, we've been discussing how to stay motivated in the face of a growing backlog, fairly prioritise the outstanding issues, potentially introduce some kind of overall roadmap planning and guidance.

At one point, we even discussed and considered blanket closing inactive issues and PR's after a certain age, see the RFC for this idea here: #1422, "Mark PR's as stale after 300 days, close them after another 60 if no activity"

Proposal
github-readme-stats have addressed this exact issue through up/downvotes against issues/features/bugs/PRs, to give their contributor community a very clear steer what to focus their efforts on. Here's what you will find featured fairly prominently on their repository readme:

We're a small team, and to prioritize, we rely on upvotes 馃憤. We use the Top Issues dashboard for tracking community demand (see anuraghazra/github-readme-stats#1935). Do not hesitate to upvote the issues and pull requests you are interested in. We will work on the most upvoted first.

This seems like a great approach for spectre.console to adopt provisionally, and road test. This PR includes the GitHub Action workflow to generate the 'top issues dashboard', making use of this marketplace action: https://github.com/marketplace/actions/top-issues-action

Follow on work required, once this PR has been merged
Once the action has executed successfully for the first time and the 'top issues dashboard' been created (ie. the issue # for the dashboard will be known), then I will submit a second PR for:

  1. Instructions in spectre.console readme.md to upvote favourite issues
  2. Instructions in the new issue template, to search for existing issues before creating a new one, and upvote issues found as necessary
  3. Pin a discussion with instructions to upvote favourite issues

Testing
I've successfully implemented the Top Issues Dashboard on a public repo I own, experimenting with different settings, see: https://github.com/FrankRay78/PatienceOS/issues

@FrankRay78 FrankRay78 requested a review from a team March 7, 2024 22:24
@FrankRay78 FrankRay78 self-assigned this Mar 7, 2024
@FrankRay78 FrankRay78 added this to the 0.49 milestone Mar 7, 2024
@FrankRay78 FrankRay78 merged commit a893a96 into spectreconsole:main Apr 14, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: PR 馃摤
Development

Successfully merging this pull request may close these issues.

None yet

2 participants