From de364ec80e3f23e35d24ac8b0ef1351994c6e9b0 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Thu, 19 May 2022 16:19:14 +0200 Subject: [PATCH 1/4] Add "no-issue-needed" rule directly in CONTRIBUTING.rst The rule was not really explained directly where you'd expect it, it was hidden deeply in "triage" process where many contributors would not even get to. This PR adds appropriate explanation and also explains that discussions is the preferred way to discuss things in Airflow rather than issues. --- CONTRIBUTING.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index f862d33b1963a..f66f2698c684e 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -66,6 +66,18 @@ implement it. Issue reporting and resolution process -------------------------------------- +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. + +If you however feel the need to open an issue (usually a bug or feature request) +consider first to start `GitHub Discussion `_. +In vast majority of cases, discussions are better than issues - you should only open +issues if you are sure you found a bug and have reproducible case to make the +maintainers aware of it, or when you want to raise a feature request which you think +does not require a lot of discussion. In case you have a very important topic +to discuss - start a discussion on the `Devlist `_. + The Apache Airflow project uses a set of labels for tracking and triaging issues, as well as a set of priorities and milestones to track how and when the enhancements and bug fixes make it into an Airflow release. This is documented as part of From cc7fdf2d156aab7490be9e6cd475e19587046d47 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sat, 21 May 2022 18:37:47 +0200 Subject: [PATCH 2/4] Update CONTRIBUTING.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- CONTRIBUTING.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index f66f2698c684e..7123348bfc5c1 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -71,7 +71,7 @@ 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 however feel the need to open an issue (usually a bug or feature request) -consider first to start `GitHub Discussion `_. +consider starting with a `GitHub Discussion `_ instead. In vast majority of cases, discussions are better than issues - you should only open issues if you are sure you found a bug and have reproducible case to make the maintainers aware of it, or when you want to raise a feature request which you think From 07d9bf8725b773f99c82e4a5664765483064bc32 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sat, 21 May 2022 18:37:52 +0200 Subject: [PATCH 3/4] Update CONTRIBUTING.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- CONTRIBUTING.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 7123348bfc5c1..e799606cea18e 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -72,7 +72,7 @@ This is intended to make it as easy as possible to contribute to the project. If you however feel the need to open an issue (usually a bug or feature request) consider starting with a `GitHub Discussion `_ instead. -In vast majority of cases, discussions are better than issues - you should only open +In the vast majority of cases discussions are better than issues - you should only open issues if you are sure you found a bug and have reproducible case to make the maintainers aware of it, or when you want to raise a feature request which you think does not require a lot of discussion. In case you have a very important topic From d426d664d18281fe6cdbb31b6a8e90e1b5cc6e4d Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sat, 21 May 2022 18:37:58 +0200 Subject: [PATCH 4/4] Update CONTRIBUTING.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- CONTRIBUTING.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index e799606cea18e..e8a2650b031a0 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -73,10 +73,10 @@ This is intended to make it as easy as possible to contribute to the project. If you however feel the need to open an issue (usually a bug or feature request) consider starting with a `GitHub Discussion `_ instead. In the vast majority of cases discussions are better than issues - you should only open -issues if you are sure you found a bug and have reproducible case to make the -maintainers aware of it, or when you want to raise a feature request which you think -does not require a lot of discussion. In case you have a very important topic -to discuss - start a discussion on the `Devlist `_. +issues if you are sure you found a bug and have a reproducible case, +or when you want to raise a feature request that will not require a lot of discussion. +If you have a very important topic to discuss, start a discussion on the +`Devlist `_ instead. The Apache Airflow project uses a set of labels for tracking and triaging issues, as well as a set of priorities and milestones to track how and when the enhancements and bug