Re: [Ietf-and-github] Roll call for WGs using GitHub

Carsten Bormann <cabo@tzi.org> Wed, 15 March 2017 19:12 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1CE1317CC for <ietf-and-github@ietfa.amsl.com>; Wed, 15 Mar 2017 12:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0iS9ohB3H60U for <ietf-and-github@ietfa.amsl.com>; Wed, 15 Mar 2017 12:12:35 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 045E31317CE for <Ietf-and-github@ietf.org>; Wed, 15 Mar 2017 12:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2FJCVfh024998; Wed, 15 Mar 2017 20:12:31 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vk1Sv56W6zDJ0C; Wed, 15 Mar 2017 20:12:31 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B1A0A921-3034-45B7-BE70-6490BA95A6D7@vpnc.org>
Date: Wed, 15 Mar 2017 20:12:31 +0100
Cc: Ietf-and-github@ietf.org
X-Mao-Original-Outgoing-Id: 511297950.901438-8673956c8ba78ce79daf61d320e88cc5
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C5ACB85-56E4-46C0-8586-A0360A59529C@tzi.org>
References: <B1A0A921-3034-45B7-BE70-6490BA95A6D7@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/qsu87zG-3UjN-HdElYA5vtld5t4>
Subject: Re: [Ietf-and-github] Roll call for WGs using GitHub
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 19:12:37 -0000

Most of the WGs in the constrained node/network (“IoT”) cluster are somewhere between

> - GitHub is used for a few docs, based on author preferences

and

> - GitHub is used for most or all docs

To wit:

https://github.com/lwig-wg
https://github.com/6lo
https://github.com/core-wg
https://github.com/cbor-wg *)?
https://github.com/cose-wg *)
https://github.com/lp-wan *)

But in most of these WGs the styles are different from document to document; only the ones marked with a star are more consistent (some of these WGs are very new).
(We also used to have some documents that lived in the personal repos of authors.)

Most documents still are:

> - issue tracking only, pull requests are rare

but some are

> - issue tracking and pull requests are common

(e.g., in CoRE, coap-tcp-tls and oscoap), and these pretty much qualify for:

> - all significant doc changes happen by pull request

by now.

But apart from those most religiously handled drafts, we still have a bit of a mishmash between

> - issues from the mailing list are turned into GitHub issues

and

> - some issues are tracked on the mailing list, others on GitHub

Grüße, Carsten