Thanks Jarek for the extra context and additions to the Traiging rst!
An update from my end as a new Triage member: For the past few weeks I have looked at every single notification from Airflow Github and it has been a very informative learning experience. 1. Beyond tagging and updating Issues you gain exposure to far more user concerns, questions and PRs than you otherwise would. This has been massively helpful to be more aware of all the work going on in Airflow and where gaps are for our users. It rounds you out as a community member in Airflow. 2. You are also given the opportunity to shepherd in more contributors to the project. It feels particularly good to help someone who filed an issue to get involved in the community by submitting a PR to solve their issue, and then following through with reviewing it, and so on. Seeing that process through from beginning to end is very rewarding! 3. I am also getting a true sense of just how overwhelming the influx of Issues, PRs and Discussions is. I have come across several folks who submitted PRs and never got feedback and then left the community. Losing these folks is a bad experience for them but also for us because we lost perhaps a great future contributor/committer/triager. We certainly need all the help we can get on this front, for reviewing, providing feedback and ultimately merging folks' contributions. I truly appreciate all the time the committers and other community members put into this side of Airflow; it's tedious and time consuming work, and is often under appreciated! Cheers, Niko ________________________________ From: Jarek Potiuk <ja...@potiuk.com> Sent: Tuesday, October 25, 2022 6:50 AM To: dev@airflow.apache.org Subject: [EXTERNAL] [PROPOSAL] Clarifications of triage team role including strenghtening importance of active triaging Hey everyone, I think with the recent addition of Denis and Niko to the triage team we already see some good signs that we should likely make the triage team stronger and also incentivised to help :). I think this is instrumental to be more welcoming for our community to respond quicker to issues and discussions (even if that response is "no we won't do it because" or "converting to discussion because") and I think having a committed (pun intended) triage team that helps committers in this task is crucial. We already mentioned "issue triaging" in the in our criteria to become commiter, but I think it was not too clear https://github.com/apache/airflow/blob/main/COMMITTERS.rst#community-involvement. You could interpret it differently I think (building issue triaging process? Making sure it works? Doing triaging yourself? What are the expectations when you are part of the triage team?). I attempted to describe it a bit better and explain what are the expectations from the triage team and why actively helping to triage issues (and discussions!) is actually a good way to become a committer. Clarifying it might also help some other people to step up and ask to be added (or even us - maintainers - to invite some of the contributors to the triage team) - because they will realise this is really good way on their road to committership I based it quite a bit on my own actions and experiences - I think actively helping our users by responding to their issues (which I think should also become more explicit part of expectations for the triage team) is one of the fastest and best ways for me to learn the parts of code I am not actively contributing to (on top of actually helping our users) I prepared a draft, proposal PR that attempts to explains our approach, expectations and strengthens a bit the importance of active triaging in the road to committership: https://github.com/apache/airflow/pull/27262 I'd love comments on that one - either here or in the PR. Would love to hear what others think. J.
