draft-ietf-git-github-wg-configuration-00.txt   draft-ietf-git-github-wg-configuration-01.txt 
wugh A. Cooper wugh A. Cooper
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational P. Hoffman Intended status: Informational P. Hoffman
Expires: August 17, 2019 ICANN Expires: September 9, 2019 ICANN
February 13, 2019 March 08, 2019
GitHub Configuration for IETF Working Groups GitHub Configuration for IETF Working Groups
draft-ietf-git-github-wg-configuration-00 draft-ietf-git-github-wg-configuration-01
Abstract Abstract
The use of GitHub in IETF working group processes is increasing. The use of GitHub in IETF working group processes is increasing.
This document describes possible uses and conventions for working This document describes possible uses and conventions for working
groups which are considering starting to use GitHub. It does not groups which are considering starting to use GitHub. It does not
mandate any processes, and does not intend to change the processes mandate any processes, and does not require changes to the processes
used by current working groups. used by current and future working groups not using GitHub.
Discussion of this document takes place on the ietf-and-github Discussion of this document takes place on the ietf-and-github
mailing list (ietf-and-github@ietf.org), which is archived at mailing list (ietf-and-github@ietf.org), which is archived at
<https://mailarchive.ietf.org/arch/search?email_list=ietf-and- <https://mailarchive.ietf.org/arch/search?email_list=ietf-and-
github>. github>.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 17, 2019. This Internet-Draft will expire on September 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
2.4. Working Group Closing . . . . . . . . . . . . . . . . . . 4 2.4. Working Group Closing . . . . . . . . . . . . . . . . . . 4
2.5. Creation of Document Repository . . . . . . . . . . . . . 4 2.5. Creation of Document Repository . . . . . . . . . . . . . 4
3. Working Group Process . . . . . . . . . . . . . . . . . . . . 5 3. Working Group Process . . . . . . . . . . . . . . . . . . . . 5
3.1. Contributions . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Contributions . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Backing Up and Archiving GitHub Content . . . . . . . . . 5 3.2. Backing Up and Archiving GitHub Content . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Many IETF working groups and participants make use of GitHub in Many IETF working groups and participants make use of GitHub in
different ways as part of their work on IETF documents. Some others different ways as part of their work on IETF documents. Some others
are interested in having their working groups use GitHub to are interested in having their working groups use GitHub to
facilitate the development of working group documents, but they are facilitate the development of working group documents, but they are
unfamiliar with how to get started or they are unclear about which unfamiliar with how to get started or they are unclear about which
conventions to follow. conventions to follow. Some other working groups use or plan to use
other other code repository services such at GitLab and Bitbucket,
which have different properties than GitHub.
This document proposes a set of administrative processes and This document proposes a set of administrative processes and
conventions for IETF working groups to use if they chose as a working conventions for IETF working groups to use if they chose as a working
group to use GitHub to facilitate their work. The proposals in this group to use GitHub to facilitate their work. The proposals in this
document are not directed at working groups or individuals that are document are not directed at working groups or individuals that are
already using GitHub to do IETF work. Practices vary among existing already using GitHub to do IETF work. Practices vary among existing
working groups and some of them are not consistent with the working groups and some of them are not consistent with the
conventions proposed here: that is fine. The goal of the proposals conventions proposed here: that is fine. The goal of the proposals
in this document is not to require uniformity in current practice, in this document is not to require uniformity in current practice,
but to help working groups to get started using GitHub in a uniform but to help working groups to get started using GitHub in a uniform
skipping to change at page 4, line 30 skipping to change at page 4, line 34
going through the steps in Section 2.1. That is, it would be good to going through the steps in Section 2.1. That is, it would be good to
be able to run steps 3 and 4 from Section 2.1 so that the rest of the be able to run steps 3 and 4 from Section 2.1 so that the rest of the
activities in this section such as personnel work the same for the activities in this section such as personnel work the same for the
organizations that were created on their own. organizations that were created on their own.
2.3. Personnel Changes 2.3. Personnel Changes
When there are personnel changes in the area or the working group, When there are personnel changes in the area or the working group,
those changes would be reflected in the GitHub organization. There those changes would be reflected in the GitHub organization. There
should likely be an API to specify that there were personnel changes. should likely be an API to specify that there were personnel changes.
[[ Need to do a bit of research on how to do this through the API, if
possible. ]]
2.4. Working Group Closing 2.4. Working Group Closing
When a working group is closed, the team with administrative access When a working group is closed, the team with administrative access
would be removed and the owner list would be returned to its initial would be removed and the owner list would be returned to its initial
composition. The organization summary and the repositories within composition. The organization summary and the repositories within
the organization would be updated to indicate that they are no longer the organization would be updated to indicate that they are no longer
under development. under development.
2.5. Creation of Document Repository 2.5. Creation of Document Repository
 End of changes. 7 change blocks. 
10 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/