potiuk commented on code in PR #62417: URL: https://github.com/apache/airflow/pull/62417#discussion_r2851638634
########## contributing-docs/04_how_to_contribute.rst: ########## @@ -36,53 +36,111 @@ Report security issues If you want to report a security finding, please follow the `Security policy <https://github.com/apache/airflow/security/policy>`_ +Issue reporting and resolution process +====================================== + +.. note:: + **TL;DR: Quick Summary** + + * **No Issue Needed:** You can open a PR directly without opening an issue first. + * **Discussion First:** If you aren't sure about a bug or feature, start a + `GitHub Discussion <https://github.com/apache/airflow/discussions>`_ instead. + * **No Assignments:** we do **not** assign issues to non-maintainers. Please do not ask to + be assigned; simply comment "working on it" and submit your PR. + * **Parallel Work is fine:** Multiple people can work on the same issue and it's fine while not necessarily + default. When it happens - we will merge the best implementation, and encourage learning and + community feedback. + +An unusual element of the Apache Airflow project (compared, for example, to commercial +development) 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. + +If you feel the need to open an issue (usually a bug or feature request), consider starting +with a `GitHub Discussion <https://github.com/apache/airflow/discussions>`_ instead. + +In the vast majority of cases, discussions are better than issues. You should only open an +issue if you are certain you have found a bug with a reproducible case, or when you want to +raise a feature request that will not require extensive discussion. If you have a significant Review Comment: updated. -- 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]
