The backlog is actually in good shape. Most of the open issues just need attention from a knowledgeable contributor in the specific area to add some pointers if the issue is valid or not.
The protocol for triage can be found in: https://github.com/apache/airflow/blob/main/ISSUE_TRIAGE_PROCESS.rst We also have #issue-triage slack channel where we raise concerns/questions/focus areas. Contributors can get triage access if we add them to https://github.com/orgs/apache/teams/airflow-triage team (It gives Github Triage role access https://infra.apache.org/github-roles.html ) I'd be happy to work with 2-3 contributors on this. If others are interested please let us know. Once we have the list and if there are no objections from PMCs I'll open a Jira to Infra to update grant access for triage role. Noting - regardless of triage privileges I encourage everyone to assist us by simply commenting in issues. The act of close/set labels is not time consuming, the real problem is actually handling the issues. On Wed, Oct 5, 2022 at 6:15 PM Oliveira, Niko <oniko...@amazon.com.invalid> wrote: > Hello folks, > > Yesterday I attended a session at ApacheCon about best practices for > managing bug/issue backlogs for a project and it got me reflecting on the > Airflow issue backlog. I'd like to get more involved in initial (and > continuous) triage of Airflow issues on Github. > > I chatted with Jarek after the session (yay, in-person events are back!) > and he mentioned that there is a mechanism available to give non-committers > the ability to modify/update Issue tags, assignees, etc on Gihub while > triaging (though not the ability to merge, of course). > > If something like this exists, is anyone willing to add me to it? If it > doesn't exist, is anyone willing to collaborate with me to setup something > like this up? :) > > Cheers, > Niko >
