Re: [Ietf-and-github] New draft, and proposal for BoF at IETF 103

Martin Thomson <martin.thomson@gmail.com> Sat, 22 September 2018 17:05 UTC

Return-Path: <martin.thomson@gmail.com>
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 2ACB0130E37 for <ietf-and-github@ietfa.amsl.com>; Sat, 22 Sep 2018 10:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 tByVgyYIBa5O for <ietf-and-github@ietfa.amsl.com>; Sat, 22 Sep 2018 10:05:58 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 0605A130E2B for <ietf-and-github@ietf.org>; Sat, 22 Sep 2018 10:05:58 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id k16-v6so1187204oik.6 for <ietf-and-github@ietf.org>; Sat, 22 Sep 2018 10:05:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O1ubIh+gF4O2n2j0TTvk57bIrTo1uC9h/Zt8vno9zwo=; b=LR0HPJhVFqFi86YLBRotPSQ8KcBC3UzewzZo/GliD3415FmIVhcZDxApce9qFnHFB/ pZlx2cW+bPo0usiSB5kCQnLJ8DVpi4+FhN9BCq2aDsnO5VJFLLgBLq+kph0uWYmXbHae bApIJxh+7qn0CBcLmFUfb92hZh5DwdKHLogz3dudC7aHnyb7Lb07WA+0iMOA7pWxWDrZ KQdf4aWWzMhwkP8+1ty7L5tHV2sA0FjVs6SgldN05nTEdUL/M5GyvmyicHciv058nPdS cuzACJg3tTHTciANzh2f5+B4g6UJ8gDWRL2NsTBAaYkdVcK7n/S/MTO5i/ZCj5j2twtT 5TVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O1ubIh+gF4O2n2j0TTvk57bIrTo1uC9h/Zt8vno9zwo=; b=GKnsrehwsGbR5pqriJzFAH1JAU1y/+p9c0FQwp9KNowmWjRn8vqxrM9yglQiQE7RMr 5e1H5GpRwBZcUxzvW7Vi5GQcasjekmbzUbJ4OLtmW6R3zva0ydPlpxFbEMLhO4f1oij3 mgLujrJ/ockmqg9cEJ8uWwsPzOzYAZl94/M4vx366Iijw6xApbleJPnmWKeKFEkBtBg2 y1WaAnUE6/JdQ6BqB8Uiwnlt4E5DtrThIFjuAMw2N/FP/wab4/rpYlKxAhdFQecvHTaf aK98cFPx2w7xb2ZJhhYSu+TeX3keYyXGM44pOLX3rXZ9WklbpkSUc6FAIFb9lr+W+4Yn V+/Q==
X-Gm-Message-State: APzg51AlYhCfLjZEso/NsOUz0u0q+EZRZvtr98CQfl/LSZr+Q46cDLyu SpwCRurJlvG9Tc0dLWh347xhJKXQpKiVa1oEKtw=
X-Google-Smtp-Source: ANB0VdYbetqkzNMCRbzu//WoBtdVa7eGzkizo7DsccBd4/F5I8CqPU8bVRCqhzO/Q55nD4A+N5/daX2TB5NdQB6qUK0=
X-Received: by 2002:aca:4dca:: with SMTP id a193-v6mr1571666oib.343.1537635957180; Sat, 22 Sep 2018 10:05:57 -0700 (PDT)
MIME-Version: 1.0
References: <5FED3790-8276-431F-85F1-6E42C57BA2F0@icann.org> <15767A94-7E61-4A91-8DB3-719BB55C0ABC@cooperw.in> <1B6523C5-5A56-4592-9545-F847C4C5F509@eggert.org> <A10B00CC-161A-49FD-B549-359B14DA3DF9@cooperw.in>
In-Reply-To: <A10B00CC-161A-49FD-B549-359B14DA3DF9@cooperw.in>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sat, 22 Sep 2018 10:05:47 -0700
Message-ID: <CABkgnnU27jdQFqKpcMat7tAv=23M_LokgFLzFdeCFCPWR9SKkA@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Lars Eggert <lars@eggert.org>, Paul Hoffman <paul.hoffman@icann.org>, ietf-and-github@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/nfiDv-rnYNRb8LkEgcijxXPtJGc>
Subject: Re: [Ietf-and-github] New draft, and proposal for BoF at IETF 103
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Sep 2018 17:05:59 -0000

On Thu, Sep 20, 2018 at 11:12 AM Alissa Cooper <alissa@cooperw.in> wrote:
> > no offense, but there isn't really anything non-obvious in draft-cooper-wugh-github-wg-configuration. IMO draft-thomson-github-bcp-00 is quite a bit more practically useful. Is that also in scope for discussion?
>
> I think it certainly could be, especially if people think the outcome would be different from the last BoF discussion of it.

FWIW, I'm happy to work with Alissa and Paul (or anyone else) to get
that doc in better shape if people believe that to be the right
answer.  I have a -01 that includes a bunch of feedback already, but I
didn't get around to pushing it.

When I talked to Alissa about this draft, I got the impression that
the idea was to go for something less comprehensive, which would be
more incremental in nature.  In terms of steps, these are good steps,
but I take Lars' point here: as a community, we're already well past
those baby steps and we might want to codify some more of the process.

I'm happy to join a discussion in Bangkok about this.  I think that
we've only really talked about the benefits/processes a few times in
the past.  If the intent here is to make the processes more concrete
and to gain some amount of official support for those processes, that
is worth discussing.

(BTW, I'm having similar discussions about congealing work practices
in my day job.  Supporting diverse work practices can be expensive,
and there is always some tension between wanting to find more
efficiency through supporting fewer options and supporting the highly
efficient and specialized practices that individuals or groups might
have developed over time.  It's a fun discussion.)