Re: [kitten] Proposal for tracking document reviews and skipping WGLC

Nico Williams <nico@cryptonector.com> Thu, 07 July 2016 00:55 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA82612B02F for <kitten@ietfa.amsl.com>; Wed, 6 Jul 2016 17:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 fIYZPEbg7Ilh for <kitten@ietfa.amsl.com>; Wed, 6 Jul 2016 17:55:08 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E7EA12B00D for <kitten@ietf.org>; Wed, 6 Jul 2016 17:55:08 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTP id 3E5F4B8081; Wed, 6 Jul 2016 17:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=Zu0i05AP5tplmA /B+1Tw56QkyrY=; b=HGzg57UmvkBDAdkHIl2DGsrEcmLRHRKP0tOyQm/PPrGOxM EuNf8/1HcDpXpUxCwQtsSq2fgeloHzAc4CT/bCiT8TwBKqZI3hkksr1WA9uSCbC/ 8uqM8DKF9RJo38p7WL1jDmyHBmIK9dM9yXhZgy4uJ8/t1P9SeHZybaehfx0zc=
Received: from localhost (108-207-244-100.lightspeed.austtx.sbcglobal.net [108.207.244.100]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTPSA id 15105B806B; Wed, 6 Jul 2016 17:55:06 -0700 (PDT)
Date: Wed, 06 Jul 2016 19:54:55 -0500
From: Nico Williams <nico@cryptonector.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Message-ID: <20160707005452.GH4935@localhost>
References: <alpine.GSO.1.10.1606202328590.18480@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1606202328590.18480@multics.mit.edu>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/_72oEf2OEJIbzLclcEnjzfro6xQ>
Cc: kitten@ietf.org
Subject: Re: [kitten] Proposal for tracking document reviews and skipping WGLC
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 00:55:10 -0000

On Mon, Jun 20, 2016 at 11:58:08PM -0400, Benjamin Kaduk wrote:
> Does this proposal seem reasonable?

Yes.

> If this proposal moves forward, there is a question of where to host the
> wiki page: two choices that came up so far are a github wiki or an
> IETF-hosted trac wiki, but we are not tied to those two options.  My

I'm not a fan of the IETF trac.  I'm not a fan of the github issue
tracker either, but,

a) github is very convenient,
b) its wiki is nice,
c) this can all be blended (optionally) with using git[hub] for version
   control of each I-D,
d) we can have an organization for the WG to be the umbrella for [a
   subset of] the WG's documents that every participant who asks can be
   made a member of.

> understanding is that either one would require an account tied to that
> provider in order to edit (to avoid wiki spam), so there would be some
> barrier to entry in either case.  However, perhaps more people already
> have github accounts than IETF trac accounts, which lends some preference

It's also becoming common to use github for IETF work.  E.g., TLS 1.3.

I'd consider other VCS services built around git too.

> to github; indeed, other WGs are using github for document editing and
> issue tracking already.  Regardless of where the wiki is hosted, a wiki
> account would not be needed in order to participate in document review;
> comments can always be sent to the mailing list and the chairs are able to
> edit the wiki page on behalf of others.

Indeed, the mailing list must remain the ultimate consensus confirmation
medium for now and the forseeable future.

Nico
--