[Cfrg] Ways of Working

Nick Sullivan <nick@cloudflare.com> Thu, 23 May 2019 21:34 UTC

Return-Path: <nick@cloudflare.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E8FE120105 for <cfrg@ietfa.amsl.com>; Thu, 23 May 2019 14:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahJMEF7QLHtR for <cfrg@ietfa.amsl.com>; Thu, 23 May 2019 14:34:26 -0700 (PDT)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54D6C1200BA for <cfrg@irtf.org>; Thu, 23 May 2019 14:34:26 -0700 (PDT)
Received: by mail-vs1-xe2d.google.com with SMTP id y6so4509383vsb.0 for <cfrg@irtf.org>; Thu, 23 May 2019 14:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=rcCZ0X7qkCS+QqX8wJ7VQUqD69tcj+7mtXNw0fZoW8I=; b=GMiMRThZr+I3VKNyFSAz6DiAbHqvqf/HJMnAGquYc9pzRdf1gETRZrX10h/0srYeX8 06ZGe05CZ1aec9+7rHVktFepWWb15WE0FtaKBxH33+gzxIiappDVySWHkmRAkeaiakwY vmkfkMP6rmNQ28P/ArOLlVsF4WHuM48VVm4b4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rcCZ0X7qkCS+QqX8wJ7VQUqD69tcj+7mtXNw0fZoW8I=; b=UNe9eF9Rkb8BMc37ucUaNb7Z8wgy1oUKUQOmAXpMsGoEv1Qx+8sZASkILmtNiLEm+r pXy6m6XLd+eqMrB3vTA3gSPSGJtZCFB6VzthOzm5sDPRI+FdfH1op60NL1I/2DYxEYEI YL1NgO0H+lZX1TwEgnNwxx7v+HfqcreqIKen5E5cixQ9oWpigxukuFIwnmJSIgoAzSc+ QbBoSNdD+VOK17pctG2wfoNYh1xcdiWTP0GOWCFxRMWapCMhECqnhLovnnuew8LOilQ6 ulKz8JLRJhPofdw28IdAEy6SneuvqJNSw8qInYniGumKsr80RgeheiuxnLrk/q2qTlJ0 JbbA==
X-Gm-Message-State: APjAAAWLLTwwlmwZivrfDJfcqvxzl/z/VOBSDG7FYxlo2FIlvXgngf2b uG+r/4tE3JT0JXPhI5sF7eyprYeim1L2SvLUIrhQwnOJCRLcfw==
X-Google-Smtp-Source: APXvYqyFUjcMQtoU4XBlxHZiuS9VrdVh8LKNCGaAwQGnNP0EzH61LUSwSdtOjqUNo/epDZUyMV1qit4Yd/xCQ0OS8J4=
X-Received: by 2002:a67:de99:: with SMTP id r25mr16560919vsk.215.1558647264934; Thu, 23 May 2019 14:34:24 -0700 (PDT)
MIME-Version: 1.0
From: Nick Sullivan <nick@cloudflare.com>
Date: Thu, 23 May 2019 14:34:13 -0700
Message-ID: <CAFDDyk_G92x8BjuuLnwr5tD7Rkg0fo-1gbqP2ceUtwUAa_rQ+A@mail.gmail.com>
To: cfrg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000008eaf24058994d88b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/QUYsCYBh3jMLmbHwNoKOQZ5nX5A>
Subject: [Cfrg] Ways of Working
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2019 21:34:28 -0000

Dear CFRG,

In an effort to improve the transparency and velocity of the CFRG process,
the chairs would like to introduce a supplementary tool for developing and
tracking the development of adopted drafts: GitHub.

This tool has been adopted successfully in several IETF Working Groups with
positive results. GitHub has subjectively improved the quality and velocity
of the development of drafts by enabling tools such as the idnits tool
<https://tools.ietf.org/tools/idnits/> to be run automatically, by allowing
WG members to provide specific editorial suggestions in the form of Pull
Requests, and by enabling editors to organize issues reported by the WG.

Once a draft has been adopted as an RG Document, the draft will be given a
dedicated repository on the CFRG Github organization (github.com/cfrg) and
draft editors will be given administrative rights to this repository. The
materials in the GitHub repository do not constitute IRTF documents and
drafts must still be formally submitted to the Datatracker. Links to GitHub
issues or Pull Requests may be referenced on-list for convenience.

Any substantive decisions made during discussions on GitHub should be
summarized on the list to solicit input from the broader community before
being incorporated into a draft. The research group chairs will consult the
working group mailing list on any issue that is potentially contentious.

This process roughly follows the suggestions put forth in Martin Thomson's
BCP draft on using Github in the IETF:
https://tools.ietf.org/html/draft-ietf-git-using-github-00

The use of GitHub is not mandatory. For now, using GitHub will be optional
for currently adopted drafts and recommended for future drafts.

- Nick, Kenny, Alexey