From 480553fe27b5b7e13d0bc07ec1f5225a296cc7dd Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 11 Mar 2020 17:03:36 +1100 Subject: [PATCH 1/3] Include secretariat in owners --- draft-ietf-git-using-github.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-git-using-github.md b/draft-ietf-git-using-github.md index f947d10..06954db 100644 --- a/draft-ietf-git-using-github.md +++ b/draft-ietf-git-using-github.md @@ -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 From 7b55110cd348cc3d07c4793ffd61c43090476e4f Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 11 Mar 2020 17:10:30 +1100 Subject: [PATCH 2/3] un-SHOULD some sentences --- draft-ietf-git-using-github.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-git-using-github.md b/draft-ietf-git-using-github.md index 06954db..de77b03 100644 --- a/draft-ietf-git-using-github.md +++ b/draft-ietf-git-using-github.md @@ -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, @@ -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 periodically consult with document editors to ensure that policies are effective. From 96ecc422c74e4cd9bb4eddf1d06fe01e7d4051fb Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 12 Mar 2020 07:22:13 +1000 Subject: [PATCH 3/3] d Co-Authored-By: Christopher Wood --- draft-ietf-git-using-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-git-using-github.md b/draft-ietf-git-using-github.md index de77b03..638aa48 100644 --- a/draft-ietf-git-using-github.md +++ b/draft-ietf-git-using-github.md @@ -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 are encourage to +editors are able to do in order to serve these goals. Chairs are encouraged to periodically consult with document editors to ensure that policies are effective.