Draft: draft-ietf-git-github-wg-configuration

Commentary: And other changes to address AD comments about the value of the document .
Paragraph (version A):
The use of GitHub in IETF working group processes is increasing.
This document describes possible uses and conventions for working
groups which are considering starting to use GitHub.  It does not
mandate any processes, and does not require changes to the processes
used by current and future working groups not using GitHub.
Paragraph (version B):
The use of GitHub in IETF working group processes is increasing.
This document describes uses and conventions for working groups which
are considering starting to use GitHub.  It does not mandate any
processes, and does not require changes to the processes used by
current and future working groups not using GitHub.
Paragraph (version A):
This document proposes a set of administrative processes and
conventions for IETF working groups to use if they choose as a
working group to use GitHub to facilitate their work.  The proposals
in this document are not directed at working groups or individuals
that are already using GitHub to do IETF work.  Practices vary among
existing working groups and some of them are not consistent with the
conventions proposed here: that is fine.  The goal of the proposals
in this document is not to require uniformity in current practice,
but to help working groups get started using GitHub in a reviewed and
validated way if desired.
Paragraph (version A):
This section specifies a proposal for an administrative process and
conventions to support the creation and management of GitHub
organizations for working groups and single-document repositories in
a uniform way.  The steps could be done manually by the IETF
Secretariat or they could be automated.  See
<https://github.com/richsalz/ietf-gh-scripts> and
<https://github.com/martinthomson/i-d-template> for working examples
of automation that is in use in some working groups.
Paragraph (version A):
In this document the question of whether processes should be manual
or automated is deliberately left unspecified, since the first
question that should be asked is whether this is functionality the
community would want to have supported at all.
Paragraph (version A):
This document proposes that there be a facility in the IETF
Datatracker (<https://datatracker.ietf.org/>) interface to allow an
area director or working group chair to request the creation of a
GitHub organization for a particular working group.  Ideally, this
facility would appear both as part of the working group chartering UI
as well as the working group page UI.
Paragraph (version B):
This document specifies a set of administrative processes and
conventions for IETF working groups to use if they choose as a
working group to use GitHub to facilitate their work.  The
specifications in this document are not directed at working groups or
individuals that are already using GitHub to do IETF work.  Practices
vary among existing working groups and some of them are not
consistent with the conventions proposed here: that is fine.  The
goal of the specifications in this document is not to require
uniformity in current practice, but to help working groups get
started using GitHub in a reviewed and validated way if desired.
Paragraph (version B):
This section specifies an administrative process and conventions to
support the creation and management of GitHub organizations for
working groups and single-document repositories in a uniform way.
The steps may be done manually by the IETF Secretariat or they may be
automated.  See <https://github.com/richsalz/ietf-gh-scripts> and
<https://github.com/martinthomson/i-d-template> for working examples
of automation that is in use in some working groups.
Paragraph (version B):
In this document the question of whether processes should be manual
or automated is deliberately left unspecified, since these are
implementation details that the IETF Secretariat and Tools Team will
address.
Paragraph (version B):
This document specifies that there be a facility in the IETF
Datatracker (<https://datatracker.ietf.org/>) interface to allow an
area director or working group chair to request the creation of a
GitHub organization for a particular working group.  Ideally, this
facility would appear both as part of the working group chartering UI
as well as the working group page UI.
Paragraph (version A):
When there are personnel changes in the area or the working group,
those changes would be reflected in the GitHub organization.  There
should likely be an ability in the Datatracker to specify that there
were personnel changes.
Paragraph (version B):
When there are personnel changes in the area or the working group,
those changes would be reflected in the GitHub organization.  There
should be an ability in the Datatracker to specify that there were
personnel changes.
Paragraph (version A):
I-D.ietf-git-using-github contains discussion of the different
possible ways that a working group can use GitHub and the large
number of decisions associated with doing so.  This section proposes
a basic set of administrative policies for working groups to follow
and the administrative support needed to carry out those policies.
Paragraph (version B):
I-D.ietf-git-using-github contains discussion of the different
possible ways that a working group can use GitHub and the large
number of decisions associated with doing so.  This section specifies
a basic set of administrative policies for working groups to follow
and the administrative support needed to carry out those policies.
Paragraph (version A):
Working group GitHub content needs to also be backed up and publicly
archived.  This document proposes using the git protocol git-protocol
itself for both of these tasks.
Paragraph (version B):
Working group GitHub content needs to also be backed up and publicly
archived.  This document specifies using the git protocol git-
protocol itself for both of these tasks.