potiuk commented on code in PR #27262: URL: https://github.com/apache/airflow/pull/27262#discussion_r1008716321
########## ISSUE_TRIAGE_PROCESS.rst: ########## @@ -27,16 +24,116 @@ of resolving issues. An unusual element of the Apache Airflow project is that you can open a PR to fix an issue or make an enhancement, without needing to open an issue first. -This is intended to make it as easy as possible to contribute to -the project. +This is intended to make it as easy as possible to contribute to the project. + +Usually users are report `Issues <https://github.com/apache/airflow/issues>`_ where they describe +the issues they think are Airflow issues and should be solved. There are two kinds of issues: + +* Bugs - when the user thinks the reported issue is a bug in Airflow +* Features - when there are small features that the user would like to see in Airflow + +We have `templates <https://github.com/apache/airflow/tree/main/.github/ISSUE_TEMPLATE>`_ for both types +of issues defined in Airflow. + +However, important part of our issue reporting process are +`GitHub Discussions <https://github.com/apache/airflow/discussions>`_ . Issues should represent +clear, small feature requests or reproducible bugs which can/should be either implemented or fixed. +Users are encouraged to open discussions rather than issues if there are no clear, reproducible +steps, or when they have troubleshooting problems, and one of the important points of issue triaging is +to determine if the issue reported should be rather a discussion. Converting an issue to a discussion +while explaining the user why is an important part of triaging process. + +Responding to issues/discussions (relatively) quickly +''''''''''''''''''''''''''''''''''''''''''''''''''''' + +It is vital to provide rather quick feedback to issues and discussions opened by our users, so that they +feel listened to rather than ignored. Even if the response is "we are not going to work on it because ...", +or "converting this issue to discussion because ..." or "closing because it is a duplicate of #xxx", it is +far more welcoming than leaving issues and discussions unanswered. Sometimes issues and discussions are +answered by other users (and this is cool) but if an issue/discussion is not responded to for a few days or +weeks, this gives an impression that the user was ignored and that the Airflow project is unwelcoming. + +We strive to provide relatively quick responses to all such issues and discussions. Users should exercise +patience while waiting for those (knowing that people might be busy, on vacations etc.) however they should +not wait weeks until someone looks at their issues. + + +Issue Triage Team +'''''''''''''''''' + +While many of the issues can be responded to by other users and committers, the committer team is not +big enough to handle all such requests and sometimes they are busy with implementing important +and complex features that require focusing for extended periods of time on them. Therefore, some people +who are regularly contributing and helping other users and shown their deep interest +in the project to the triage team. The current list of triage team members can be found in +`the .asf.yaml <.asf.yaml>`_ file in the ``collaborators`` section. + +Committers can invite people to become members of the triage team if they see that the users are already +helping and responding to issues and when they see the users are involved regularly. But you can also ask +to become a member of the team (on devlist) if you can show that you have done that and when you want to have +more ways to help others. + +The triage team members do not have committer privileges but they can +assign, edit, and close issues and pull requests without having capabilities to merge the code. They can +also convert issues into discussions and back. The expectation for the issue triage team is that they +spend a bit of their time on those efforts. Triaging means not only assigning the labels but often responding +to the issues and answering user concerns or if additional input is needed - tagging the committers or other community members who might be able to help provide more complete answers. + +Being an active and helpful member of the "Issue Triage Team" is actually one of the paths towards +becoming a committer. By actively helping the users and triaging the issues and responding to them and +involving others (when needed) shows that you are not only willing to help our users and the community, +but are also ready to learn about parts of the projects you are not actively contributing to - all of that +are super valuable components of being eligible to `become a committer <COMMITTERS.md>`_. + +If you are a member of the triage team and not able to make any commitment, it's best to ask to have yourself +removed from the triage team. + +BTW. Every committer is pretty much automatically part of the "Issue Triage Team" - so if you are committer, +feel free to follow the process for every issue you stumble upon. + +Actions that can be taken by the issue triager +'''''''''''''''''''''''''''''''''''''''''''''' + +There are several actions an issue triager might take: + +* Closing and issue with "invalid" label explaining why it is closed in case the issue is invalid. This + should be accompanied by information that we cn always re-open an issue if our understanding was wrong + or if the user provides more information. + +* Converting an issue to a discussion, if it is not very likely it is an Airflow issue or when it is not + responsible, or when it is a bigger feature proposal requiring discussion or when it's really users + troubleshooting or when the issue description is not at all clear. This also involves inviting the user + to a discussion if more information might change it. + +* If the issue seems important enough that it should likely be looked at before the next release but there Review Comment: very good point :). Consistency above all :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
