Strenghten a bit and clarify importance of triaging issues #27262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rossturk
approved these changes
Oct 25, 2022
potiuk
force-pushed
the
strengthen-triage-process-importance-in-committership-path
branch
from
968cb3d
to
ac00396
Compare
o-nikolas
approved these changes
Oct 26, 2022
|
Any more comments? |
shubham22
reviewed
Oct 28, 2022
potiuk
force-pushed
the
strengthen-triage-process-importance-in-committership-path
branch
2 times, most recently
from
da95f6c
to
64eda21
Compare
pierrejeambrun
approved these changes
Oct 29, 2022
Triaging issues is an important part of the work we do. It is crucial that we respond swiftly and accurately to issues and discussions created by our users so that they feel welcome and listened to. By participation in triaging process, contributors might show not only their willingness of helping other community members, but also show that they understand various parts of airflow (also that they are capable of learning it while helping others - which is one of the best ways to learn parts of Airflow you do not actively contribute to.
potiuk
force-pushed
the
strengthen-triage-process-importance-in-committership-path
branch
from
28053b9
to
6301d64
Compare
|
Applied all comments from @pierrejeambrun @shubham22 as well and rebased. Let's see if others will chime in after pinging in the devlist. |
|
I have a feeling that the title of the PR/Commit should be changed after all those comments :) |
|
Merging as is. We can always improve it later. |
potiuk
deleted the
strengthen-triage-process-importance-in-committership-path
branch
ephraimbuddy
added
the
type:misc/internal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Triaging issues is an important part of the work we do. It is crucial that we respond swiftly and accurately to issues and discussions created by our users so that they feel welcome and listened to.
By participation in triaging process, contributors might show not only their willingness of helping other community members, but also show that they understand various parts of airflow (also that they are capable of learning it while helping others - which is one of the best ways to learn parts of Airflow you do not actively contribute to.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.