An emphatic +1 from me! The issues could gain a huge boost from the added human curation, whether it's adding sensible labels, running Project kanban boards, linking issues to PRs (and other relevant issues), and more. It could not only bring some order to the chaos, but help those in the community reporting issues feel like they’re being heard.
Evan Rusackas ( he | him ) Frontend Lead Preset | preset.io On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <maximebeauche...@gmail.com>, wrote: > Hi all, > > It just came to my attention that GitHub added a new "triage" access level > at the repo level. > https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/ > > In the past, we've identified that it was impossible for non-committers > (especially our PMs and contributors-that-are-not-yet-committers) to help > us triage issues, apply labels, assign reviews, close and reopen issues as > needed. It's really clear to me that we really need all the help we can get > in this area, and that not being able to involve more people into this > process hurts us, and is a clear operational downside of using the ASF > infra. > > I'd like to build a case for this to become allowed by ASF infra. But > first, I'd love to see some +1s, and a list of GitHub handles for people in > our community who could make use of this feature. > > More technically, I think the way to make that easy and painless would be > to add a new entry to the `.asf.yaml` file that would enable maintainers to > assign the "triage" role to whoever they see fit. For reference, here's > more context on that piece of automation I'd like to latch this onto here: > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features > > FYI, xposting this to general@incubator for their attention. > > Max
