[Ietf-and-github] Martin Vigoureux's No Objection on draft-ietf-git-using-github-05: (with COMMENT)

Martin Vigoureux via Datatracker <noreply@ietf.org> Thu, 12 March 2020 11:00 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ietf-and-github@ietf.org
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC2A3A0C5A; Thu, 12 Mar 2020 04:00:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Vigoureux via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-git-using-github@ietf.org, git-chairs@ietf.org, ietf-and-github@ietf.org, Christopher Wood <caw@heapingbits.net>, caw@heapingbits.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <158401082788.18076.104688218811852864@ietfa.amsl.com>
Date: Thu, 12 Mar 2020 04:00:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/fgW6HgcxlmT0Cm1j9EXekioXnJE>
Subject: [Ietf-and-github] Martin Vigoureux's No Objection on draft-ietf-git-using-github-05: (with COMMENT)
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Mar 2020 11:00:28 -0000

Martin Vigoureux has entered the following ballot position for
draft-ietf-git-using-github-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-git-using-github/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

I share most of the concerns raised by my co-ADs.

What I'd really like to see is some clarifications added such that it is clear
that these recommandations are not for all IETF WGs. There is a sentence which
aims at stating that:
   The requirements here apply to the case where Working Groups decide
   to use GitHub as a primary means of interaction.
But in fact before that one can also read:
   The intent is to allow each Working Group ...
and after that:
   Each Working Group SHOULD create ...
   Each Working Group MAY ...
plus many occurrences of "Working Groups" (plural).

To resolve the ambiguity may be you could do:
   The intent is to allow a Working Group considerable flexibility in how it
   uses GitHub. The Working Group SHOULD create its own new organisation. The
   Working Group MAY ...

And/or maybe reinforce the first sentence by clarifying that, in the rest of
the document, "Working Groups" refer to working groups which have decided to
use GitHub.

-m