Cool stuff. It looks like we have some nice incremental steps that we can start introducing.
Just a comment after the meeting - my current thinking about the triage process improvement. As I understand the approach you propose now is that rather than trying to define the whole triage process up-front, we just pin-point small, incremental changes in our process requiring just little adaptations from the people involved. If we do that while having the "Big Goal" we want to achieve in our vision - this might get us there (or somewhere close to it but better) eventually :). J. On Mon, Nov 9, 2020 at 6:27 AM Vikram Koka <[email protected]> wrote: > Hi all, > > I have updated our meeting notes document to summarize the discussion from > our call on Thursday. Thank you all who joined the call. > > To all those who attended, can you please double-check and add if I missed > anything? > To all those who didn't join, if you disagree to anything covered, please > voice your opinion. > Also, please let me know if you want to include anything in the call the > coming week. > Overall Summary > > Key discussions points raised: > > - > > Experienced committers such as Jarek and Kaxil who have a broad > knowledge of Airflow look at all the issues raised in the stream of > incoming issues and then process prioritization as well as what they choose > to work on. > - > > Committers focused on specific areas such as Kubernetes and User > Interface would generally like to look at the issue in their areas of > focus, so that they can quickly resolve those within their area of > expertise. > - > > Filtering of issues, by the triage team (Elad, Paola, Vikram, et al), > would be helpful here in optimising committer time. > - > > Elad commented how tagging issues with “GoodFirstIssue” has galvanized > contributions from new and inexperienced contributors, who are looking to > contribute. > - > > Use of priority and milestones should be the committers only, not by > the triage team. These would be extremely useful in the context of release > planning to ensure that “critical” issues assigned to a release, must be > fixed as part of that release. > - > > Automation of steps and transitions such as: > - > > Waiting on a user for more information. Automatically close the > issue if there is no response within a specified time. > - > > Re-assign or bring back to triage status if an assignee does not > respond within a specified time. > - > > Triage team to continue assigning labels and streamlining issue > streams, based on updated set of labels, including additional labels to be > added. > - > > Request committers to add sizing for issue as part of the triage > process, so that contributors can pick up small issues to tackle, similar > to “GoodFirstIssue”. > > > *Doc links*: > *Meeting notes*: > https://docs.google.com/document/d/1Fx46SoOnNLiqZKtrC-tOHj3zFlZfQwWuR2LRFXJnWqw/ > > > Next meeting: > *Date*: November 12th > *Time*: 8.30-9.30 AM Pacific / 4.30 PM GMT > *Zoom link*: > https://astronomer.zoom.us/j/92994970750?pwd=NVRPdmhQbWJNblRIcDRuTVZiYldqZz09 > <https://www.google.com/url?q=https://astronomer.zoom.us/j/92994970750?pwd%3DNVRPdmhQbWJNblRIcDRuTVZiYldqZz09&sa=D&source=calendar&ust=1605255722894000&usg=AOvVaw2EAMClSMtJ0lTQhT7B_38Q> > > Best regards, > > Vikram > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
