Sure we will add you to the list On Mon, 17 Oct 2022 at 23:00, Ferruzzi, Dennis <ferru...@amazon.com.invalid> wrote:
> I'd actually like to jump in on this as well, if possible. I tried to > help with triage little in the past but without being able to add the tags > myself, it felt silly just tagging someone else to add the tags. > > > ------------------------------ > *From:* Elad Kalif <elad...@apache.org> > *Sent:* Tuesday, October 11, 2022 11:50 PM > *To:* dev@airflow.apache.org > *Subject:* RE: [EXTERNAL]Github Issue Triaging > > > *CAUTION*: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > It seems that we don't need Infra: > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub > > Raised PR to add Niko: > https://github.com/apache/airflow/pull/27003 > <https://github.com/apache/airflow/pull/27003> > Add o-nikolas to triage team by eladkal · Pull Request #27003 · > apache/airflow · GitHub <https://github.com/apache/airflow/pull/27003> > github.com > https://lists.apache.org/thread/hoxfrooplhj08ss8ckf2ftbg5805bzqx We can > set (non-committer) collaborators the triage role with .asf.yaml > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub > ^ Add meaningful description above Read the Pull Request Guidelines for > more information. In case of fundamental code changes, an Airflow > Improvement Proposal (AIP) is needed. In case of a new dependency, check > compliance with the ASF 3rd Party License Policy. In case of backwards > incompatible changes please leave a note in a newsfragment file, named > {pr_number}.significant.rst or {issue_number}.significant.rst, in > newsfragments. > > > On Thu, Oct 6, 2022 at 12:39 AM Oliveira, Niko <oniko...@amazon.com.invalid> > wrote: > >> > @Niko - You can start helping even before you get added to that, by >> just tagging Elad, myself or other Triage team members (until you get into >> triage team) on the issues you feel are not-active so that we can close it. >> >> >> Yupp, sounds good, will do! I appreciate the support Kaxil. >> >> Cheers, >> Niko >> >> >> ------------------------------ >> *From:* Kaxil Naik <kaxiln...@gmail.com> >> *Sent:* Wednesday, October 5, 2022 10:16 AM >> *To:* dev@airflow.apache.org >> *Subject:* RE: [EXTERNAL]Github Issue Triaging >> >> >> *CAUTION*: This email originated from outside of the organization. Do >> not click links or open attachments unless you can confirm the sender and >> know the content is safe. >> >> 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. >> >> No objections from me, the more the merrier. >> >> @Niko - You can start helping even before you get added to that, by just >> tagging Elad, myself or other Triage team members (until you get into >> triage team) on the issues you feel are not-active so that we can close it. >> >> Other things are: >> >> - Reminding assignees if they are still working on the issues >> - Or add "pending response" where the issue creator hasn't replied >> >> Regards, >> Kaxil >> >> On Wed, 5 Oct 2022 at 17:32, Oliveira, Niko <oniko...@amazon.com.invalid> >> wrote: >> >>> Hey Elad! >>> >>> Yupp, I read through that rst and I'm going to help triage incoming >>> issues more frequently. Though I do think reviewing the backlog of issues >>> every quarter or so can be a useful exercise as well. >>> >>> Consider this my request to be added to the airflow-triage Team! >>> >>> Cheers, >>> Niko >>> ------------------------------ >>> *From:* Elad Kalif <elad...@apache.org> >>> *Sent:* Wednesday, October 5, 2022 9:01:22 AM >>> *To:* dev@airflow.apache.org >>> *Subject:* RE: [EXTERNAL]Github Issue Triaging >>> >>> >>> *CAUTION*: This email originated from outside of the organization. Do >>> not click links or open attachments unless you can confirm the sender and >>> know the content is safe. >>> >>> 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 >>>> >>>
