Draft: draft-thomson-github-bcp

Commentary: Add WG experiences from the ( now dead ) Some contributions by
Paragraph (version A):
When an Area Director changes, the outgoing Area Director MUST be
removed from the organization's ownership team.  This can be done by
the continuing AD, the outgoing AD or the WG Chairs.  The incoming
Area Director and/or delegate MUST be added to the organization's
ownership team.  When a WG Chair changes, the responsible Area
Director or a delegate MUST remove the previous WG Chair from the
organization's ownersip or administrative team and SHOULD add the new
WG Chair to that team.
Paragraph (version B):
When an Area Director changes, the outgoing Area Director MUST be
removed from the organization's ownership team.  This can be done by
the continuing AD, the outgoing AD or the WG Chairs.  The incoming
Area Director and/or delegate MUST be added to the organization's
ownership team.  When a WG Chair changes, the responsible Area
Director or a delegate MUST remove the previous WG Chair from the
organization's ownership or administrative team and SHOULD add the
new WG Chair to that team.
Paragraph (version A):
The wording and details of how to do so are specified at
https://trustee.ietf.org/license-for-open-source-repositories.html.
The details are copied below, but the IETF web-site is authorative.
Paragraph (version B):
The wording and details of how to do so are specified at
https://trustee.ietf.org/license-for-open-source-repositories.html.
The details are copied below, but the IETF web-site is authoritative.
Paragraph (version A):
While 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 such public respository MUST
follow the guidelines in note-well.  This recognizes that editors
have traditionally chosen their own methods for managing the
documents they edit but preserves the need for transparent
contributions with awareness of IPR considerations.
Paragraph (version B):
While 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 such public repository MUST
follow the guidelines in note-well.  This recognizes that editors
have traditionally chosen their own methods for managing the
documents they edit but preserves the need for transparent
contributions with awareness of IPR considerations.
Paragraph (version A):
A system of labelling issues can be effective in managing issues.
For instance, marking substantive issues separately from editorial
can be helpful at guiding discussion.  Using labels can also be
helpful in identifying issues for which consensus has been achieved,
but that require editors to integrate the changes into a document.
Paragraph (version B):
A system of labeling issues can be effective in managing issues.  For
instance, marking substantive issues separately from editorial can be
helpful at guiding discussion.  Using labels can also be helpful in
identifying issues for which consensus has been achieved, but that
require editors to integrate the changes into a document.
Paragraph (version A):
Editors SHOULD make pull requests for all substantial changes rather
than commiting directly to the "master" branch of the repository.
Paragraph (version B):
Editors SHOULD make pull requests for all substantial changes rather
than committing directly to the "master" branch of the repository.
Paragraph (version A):
Editors SHOULD endeavour to create a new Internet-Draft submission
two weeks prior to every session (see Section 7.1 of RFC2418).
Participants in a session can't be expected to monitor changes to
documents in real-time; an Internet-Draft ensures that there is a
common, stable state that is known to all participants.
Paragraph (version B):
Editors SHOULD endeavor to create a new Internet-Draft submission two
weeks prior to every session (see Section 7.1 of RFC2418).
Participants in a session can't be expected to monitor changes to
documents in real-time; an Internet-Draft ensures that there is a
common, stable state that is known to all participants.