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

Melinda Shore <melinda.shore@nomountain.net> Sun, 19 March 2017 18:32 UTC

Return-Path: <melinda.shore@nomountain.net>
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 955E2129513 for <ietf-and-github@ietfa.amsl.com>; Sun, 19 Mar 2017 11:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.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 URG6Y3ZxLEKI for <ietf-and-github@ietfa.amsl.com>; Sun, 19 Mar 2017 11:32:37 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 E32CE129511 for <ietf-and-github@ietf.org>; Sun, 19 Mar 2017 11:32:36 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id p189so33358664pfp.1 for <ietf-and-github@ietf.org>; Sun, 19 Mar 2017 11:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=9eRrNVLxW7XViY1ofZHl9F98Y9hO4NT5QfbEzwTNHFI=; b=EFlFP7xJnlK/9INk63wZxgxRc/HIrzws0sveKJJf8LqkXVLyoGaiziCR4bRVo1uL41 4tcm5igy49NPopkDHOMp9UBAsxGB1uW/YBLrW3fG6pIawY5aQZp81zngfVjHkZ26XuCG GmDvZlwj1t8U9/2gQIcIZ/xLnArAiQkTWX2BuNT3lzmolHhI/0janfuM5hYc9mpXHz1B M9gntFGE5owNDkeaIe11KcDyWMJshAolqWCdrC5KiU0WWH18YlzaocxQCpDYpJXVxVdi BJyjivcTSOa/uFyh3zhx3+2kEy8uuWqvHO0PPmf6XA0DG9epXSO8kJ5a58FO9z0kisqU q1Og==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=9eRrNVLxW7XViY1ofZHl9F98Y9hO4NT5QfbEzwTNHFI=; b=owWgCGDGZ1uObAZC+3lG6ZQkd+b+N6hyn0kxKofZC53oaa0ymCjwaDFNxiqj/z2DyB dppv3GMt1EmkfOYudhgOC1+vV2DwH/SKlmYEES3z28ejZkrG1ieZbOk/JXZK3E8BfzF6 raPcdgBio2LQ/Ke1P3U+fDaIXhZU0XbGbdaVW+eb3OLsASqGvyqYCpJQ/0iBM1iuubau MKYBzwOMuj1wRsDQIWcNl7iuJKALhDJ0FKEnOjuWi0OBx3xSho15LmAKH0a9qgrMo2bi nprDpaYMzkrj2Us/Muu/55quyErxTdLuG47FyFFZcti0DLR2ZqOC377VIfTPvTwj48Ll pkDQ==
X-Gm-Message-State: AFeK/H2IpA7TAjEGs61y2NjsdVnkxYZtwd6aHMI/iW4l5sW0uWUChW/stJ9RX0X6KGCzjA==
X-Received: by 10.99.125.27 with SMTP id y27mr2938874pgc.79.1489948356066; Sun, 19 Mar 2017 11:32:36 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-51-192-radius.dynamic.acsalaska.net. [216.67.51.192]) by smtp.gmail.com with ESMTPSA id w29sm28367989pfi.131.2017.03.19.11.32.34 for <ietf-and-github@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Mar 2017 11:32:35 -0700 (PDT)
To: ietf-and-github@ietf.org
References: <B1A0A921-3034-45B7-BE70-6490BA95A6D7@vpnc.org> <CABkgnnX6Qqhe6D63npbwxUVXa5sOY9AdZ9Ew5Jnb39rY-npjdg@mail.gmail.com>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <e8e1d155-e8e2-d86c-e11e-07d4ee2669c4@nomountain.net>
Date: Sun, 19 Mar 2017 10:32:32 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CABkgnnX6Qqhe6D63npbwxUVXa5sOY9AdZ9Ew5Jnb39rY-npjdg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="Cqe1vpu7FTQPKRti0DcM4lf2qb84fpR9l"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/ZpUiRSy44caNoDtn5Jq-tRlfO2Y>
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: Sun, 19 Mar 2017 18:32:38 -0000

On 3/15/17 9:25 PM, Martin Thomson wrote:
> TRANS - appear to have a draft on github and issues in trac (shudder)

To clarify, authors have a draft in github - we're good with
authors/editors using whatever tools they find most effective
and aren't going to mandate draft tool use one way or another.

The issues are in trac because it was important, given a
highly factionalized working group participant base, to have
the issue tracker on a neutral, IETF-owned and managed platform.
I think that regardless of whatever else is used, there's a
lot of process value in having good IETF-managed tools available,
and I'd love it if we could get a git service (including ticketing
and their wiki) up on IETF resources.  But trac is what we've got
so trac is what we use.

I think the goal here is to give people the tools to be effective
rather than having them be controlled by their tools.

Melinda