Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to ASF lazy consensus doc in CONTRIBUTING.rst #33973

Merged
merged 2 commits into from
Sep 3, 2023
Merged

Link to ASF lazy consensus doc in CONTRIBUTING.rst #33973

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d611e23
Link to ASF lazy consensus doc in CONTRIBUTING.rst
RNHTTR Aug 31, 2023
ba12f19
Update CONTRIBUTING.rst
RNHTTR Sep 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ There are certain expectations from the members of the security team:
* They are supposed to be active in assessing, discussing, fixing and releasing the
security issues in Airflow. While it is perfectly understood that as volunteers, we might have
periods of lower activity, prolonged lack of activity and participation will result in removal
from the team, pending PMC decision (the decision on removal can be taken by LAZY CONSENSUS among
from the team, pending PMC decision (the decision on removal can be taken by `LAZY CONSENSUS <https://community.apache.org/committers/lazyConsensus.html>`_ among
all the PMC members on private@airflow.apache.org mailing list).

* They are not supposed to reveal the information about pending and unfixed security issues to anyone
Expand Down