Hi Erik, Do you have a good understanding of *why* there are more issues being opened than being closed? If so, that might hint at some possible solutions.
For example, if you just don't have enough people to write code, then the PMC could focus on inviting new committers to try to grow the community, or mentoring new developers. If, on the other hand, the quality of the issues is poor, such that they aren't very actionable, you could ask for more information from the reporter, and add a label that shows its status, such as "waiting on reporter". If no response is given in a reasonable time, you can close old issues. You can also try to address issue quality using GitHub issue templates: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository You could also set up something to auto-close very old issues that haven't been updated in a long time, under the premise that they are probably not relevant anymore. If they are, they can always be re-opened. You can also use GitHub "projects" (which I see you're already using: https://github.com/apache/superset/projects) to help organize related tasks, so they can be closed when the overall project is done. If the problem is that your committers aren't paying attention to open issues, you can try to ping your community's dev@ list to remind people of how many issues are outstanding, as a way of encouraging people to help triage, close, and bring down the number. You could try to find other ways to "gamify" the count, too. But, ultimately, it comes down to volunteer effort. If the problem is that your committers are having trouble tracking the activity on GitHub, you can double check your mailing list configuration to ensure activity gets copied to a notifications@ or issues@ list that your committers can track (you can also configure them to go to dev@, but that tends to get spammy and redundant, especially for your committers who are happy seeing the notification dots and/or emails directly from GitHub). Ultimately, you'll need to figure out why the situation is the way it is, and address it accordingly. You won't be able to force volunteer community members to participate to bring the number down, but perhaps there's ways to encourage them, depending on why it's happening in the first place. On Thu, Jul 8, 2021 at 5:04 PM Erik Ritter <erik.t.rit...@gmail.com> wrote: > > Hi all, > > I'm a PMC member for Apache Superset, and we've recently been struggling > with the number of issues reported in our Github repo. We're currently at > > 800 open issues, and are having trouble keeping up with responding and > addressing all the user issues and feedback. We were curious if any other > Apache projects had a way of managing Github issues that works for them. We > were considering setting up a bot that assigns new issues to a random > committer/PMC member, but are open to other ideas too. Thanks for your help > and advice! > > Best, > Erik Ritter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
