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

Jump to bottom

Rob's AD review comments #44

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Rob's AD review comments #44

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
480553f
Include secretariat in owners
martinthomson Mar 11, 2020
7b55110
un-SHOULD some sentences
martinthomson Mar 11, 2020
96ecc42
d
martinthomson Mar 11, 2020
7520f98
Merge branch 'master' into rob
martinthomson Mar 16, 2020
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
10 changes: 5 additions & 5 deletions draft-ietf-git-using-github.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,9 +171,9 @@ within an area. Large organizations create too much overhead for general
management tasks, particularly when there is a need to maintain membership.

Each organization requires owners. The owner team for a Working Group
repository MUST include responsible Area Directors. Area Directors MAY also
designate a delegate that becomes an owner and Working Group chairs MAY also be
owners.
repository MUST include responsible Area Directors and SHOULD include the IETF
Secretariat. Area Directors MAY also designate a delegate that becomes an owner
and Working Group chairs MAY also be owners.

A team with administrator access SHOULD be created for the Working Group Chairs
and any Working Group Secretary. Administrator access is preferable, since this
Expand Down Expand Up @@ -239,7 +239,7 @@ The set of GitHub features ({{features}}) that the Working Group relies upon
need to be clearly documented in policies. This document provides some guidance
on potential policies and how those might be applied.

Features that the Working Group does not rely upon SHOULD be made available to
Features that the Working Group does not rely upon can be made available to
document editors. Editors are then able to use these features for their own
purposes. For example, though the Working Group might not formally use issues
to track items that require further discussion in order to reach consensus,
Expand All @@ -248,7 +248,7 @@ keeping the issue tracker available to editors can be valuable.
Working Group policies need to be set with the goal of improving transparency,
participation, and ultimately the quality of the consensus behind documents. At
times, it might be appropriate to impose some limitations on what document
editors are able to do in order to serve these goals. Chairs SHOULD
editors are able to do in order to serve these goals. Chairs are encourage to
martinthomson marked this conversation as resolved.
Show resolved Hide resolved
periodically consult with document editors to ensure that policies are
effective.

Expand Down