Skip to content

Rob's AD review comments #44

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

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

Rob's AD review comments #44

Changes from all 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: 6 additions & 4 deletions draft-ietf-git-using-github.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,8 @@ within an area. Large organizations create too much overhead for general
management tasks.

GitHub requires that each organization have at least one owner. The owners for
a Working Group repository MUST include responsible Area Directors. Area
a Working Group repository MUST include responsible Area Directors and SHOULD
include Area Directors from the area and the IETF Secretariat. Area
Directors MAY also designate a delegate that becomes an owner. Working Group
chairs MAY also be owners.

Expand Down Expand Up @@ -255,7 +256,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 @@ -264,8 +265,9 @@ 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 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 periodically consult with document
editors and the Working Group to ensure that policies are effective.
in order to serve these goals. Chairs are encouraged to periodically consult
with document editors and the Working Group to ensure that policies are
effective.

A document editor can still use GitHub independently for documents that they
edit, even if the Working Group does not expressly choose to use GitHub. Any
Expand Down