potiuk opened a new pull request #22200: URL: https://github.com/apache/airflow/pull/22200
Maybe this is my non-native English, but I often feel a bit strange when reading the issues raised by our users whe they start the description with: * "I expected this and that" For me - this comes from the "What you expected to happen" heading we have and I have a feeling this might lead to bad wording of the issues which can lead to unnecessary tensions. "Expectation" is a bit too strong of a word for the Open-Source project because there might be many reasons why the "expectation" is not fulfilled and the user might not be aware, so they might "Expect" something in a sense of "demanding" it, when there are good reasons things are how they are. In most cases people do not read the description or hint we provided - they stop short by reading the header and base their answer on the header. I personally perceive that when you start "I expected this and this", it feels like "This is obvious it should be like this". I think changing the heading to "What you think should happen" might be much better and has much less of the "demand" in it. Eventually it might lead to people understanding better that what they raise here is more of a "wish" rather than "expectation" and that this presents their personal thinking rather than "general expectation". Making sure in the heading wording that the raised issue is a bit "softer" might also set the tone for the follow-up conversation. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
