WG Action: Formed GitHub Integration and Tooling (git)

The IESG <iesg-secretary@ietf.org> Fri, 08 February 2019 22:07 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 41752131022; Fri, 8 Feb 2019 14:07:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: WG Action: Formed GitHub Integration and Tooling (git)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, git-chairs@ietf.org, ietf-and-github@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <154966364726.31128.15268659046534805678.idtracker@ietfa.amsl.com>
Date: Fri, 08 Feb 2019 14:07:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/C_F5PoO01g0tOfnHiw-Z-znJOWQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2019 22:07:27 -0000

A new IETF WG has been formed in the General Area. For additional
information, please contact the Area Directors or the WG Chairs.

GitHub Integration and Tooling (git)
-----------------------------------------------------------------------
Current status: Proposed WG

Chairs:
  Christopher Wood <christopherwood07@gmail.com>;
  Paul Hoffman <paul.hoffman@icann.org>;

Assigned Area Director:
  Alissa Cooper <alissa@cooperw.in>;

General Area Directors:
  Alissa Cooper <alissa@cooperw.in>;

Mailing list:
  Address: ietf-and-github@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/ietf-and-github
  Archive: https://mailarchive.ietf.org/arch/browse/ietf-and-github/

Group page: https://datatracker.ietf.org/group/git/

Charter: https://datatracker.ietf.org/doc/charter-ietf-git/

Many IETF working groups use external code repository services, primarily
GitHub, in managing their work. Individual working groups, while continuing
to operate within IETF guidelines for working group activity, have developed
their own policies and practices for how they use these services. These
policies and practices cover aspects such as: managing discussion between
working group mailing lists and GitHub issues and pull requests; how text
contributions are expected to be made; labeling and naming conventions;
maintaining readable draft snapshots; using tooling and automation; informing
participants about IETF policies; and others.

The GitHub Integration and Tooling (GIT) working group will select a set of
such practices and document policies that support those practices. The
policies will each detail how work is conducted by working groups that opt to
follow the work practice. The goal is to provide both process and tooling
support for working groups that choose to adopt the practices.

The documents produced by this group may apply to services similar to GitHub.
However, documenting generalized policies that are designed to apply to
multiple services or policies specific to services besides GitHub are out of
scope for this working group. Pursuing such work requires a re-charter.

The documents produced by this group will not alter the Internet Standards
Process (BCP 9). They will describe how to work within it. Whether working
groups choose to use GitHub or the documented policies to support their work
will remain entirely at their discretion.

The working group may also discuss tooling requirements in support of GitHub
use. Decisions about implementing specific tooling needs will be undertaken
by the IETF Tools Team in consultation with working group participants and
other interested contributors.

Milestones:

  Aug 2019 - Work practice description and policy document(s) sent to IESG
  for publication as BCP