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

"Henry B (Hank) Hotz, CISSP" <hbhotz@oxy.edu> Thu, 07 July 2016 01:16 UTC

Return-Path: <hbhotz@oxy.edu>
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 5DB5512D15E for <kitten@ietfa.amsl.com>; Wed, 6 Jul 2016 18:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 BO9aimRIYzC7 for <kitten@ietfa.amsl.com>; Wed, 6 Jul 2016 18:16:05 -0700 (PDT)
Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.201.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9A5A12D0E1 for <kitten@ietf.org>; Wed, 6 Jul 2016 18:16:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id ED8D1E263; Wed, 6 Jul 2016 21:16:04 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca
Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lp3c64Bmcifj; Wed, 6 Jul 2016 21:16:04 -0400 (EDT)
Received: from [192.168.3.129] (24-205-82-163.dhcp.psdn.ca.charter.com [24.205.82.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 36DB4E25C; Wed, 6 Jul 2016 21:16:04 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: "Henry B (Hank) Hotz, CISSP" <hbhotz@oxy.edu>
In-Reply-To: <20160707005452.GH4935@localhost>
Date: Wed, 06 Jul 2016 18:16:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4A6292D-F85A-4ACA-8AF7-E3DC6854BC01@oxy.edu>
References: <alpine.GSO.1.10.1606202328590.18480@multics.mit.edu> <20160707005452.GH4935@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/54YP9F3FyKMyEB4Qmn1Ha8h2N-k>
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 01:16:07 -0000

Given the necessary multitude of different username/password combinations I need to avoid duplicating passwords already, I don’t consider the need for yet another for an IETF wiki to be a serious impediment.

Agreed that *some* mailing list traffic is still necessary so the otherwise-uninvolved have a chance to weigh in.

> On Jul 6, 2016, at 5:54 PM, Nico Williams <nico@cryptonector.com> wrote:
> 
> 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
> -- 
> 
> _______________________________________________
> Kitten mailing list
> Kitten@ietf.org
> https://www.ietf.org/mailman/listinfo/kitten


Personal: hbhotz@oxy.edu
https://www.linkedin.com/in/hbhotz/