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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 12 March 2020 12:28 UTC

Return-Path: <alexandre.petrescu@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 E2DC13A0F9A for <ietf-and-github@ietfa.amsl.com>; Thu, 12 Mar 2020 05:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Level:
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 lCjkVHgfw0jR for <ietf-and-github@ietfa.amsl.com>; Thu, 12 Mar 2020 05:28:21 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE6023A0F86 for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 05:28:19 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 02CCSHrT026218 for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 13:28:17 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D77BF2059FB for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 13:28:17 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id CD11C2057AE for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 13:28:17 +0100 (CET)
Received: from [10.11.240.10] ([10.11.240.10]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 02CCSEaB027459 for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 13:28:16 +0100
To: ietf-and-github@ietf.org
References: <158401082788.18076.104688218811852864@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <8cddb995-d3b2-bc6c-1706-30f9ff4933df@gmail.com>
Date: Thu, 12 Mar 2020 13:28:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <158401082788.18076.104688218811852864@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/e5ctpCdr2uNhVHmJIUf9cnCrcGY>
Subject: Re: [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
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: Thu, 12 Mar 2020 12:28:23 -0000


Le 12/03/2020 à 12:00, Martin Vigoureux via Datatracker a écrit :
> 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.

I do not understand this.

It is people who decide to use or not use github for their work in that 
WG.  SOme people in the same WG use it, others dont.

Because of that, maybe clarify that the recommendations written in this 
I-D are for Contributors to I-D in a a WG, not for WG chairs. (?)

Other people dont work in WGs (independent track) and, among them, still 
some use github and others no.

WG chairs can accept or not accept that the Contributors in a document 
use github or not.

I do not know what can be recommended to WG Chairs about using or not 
using github.  Maybe the Chairs use github to maintain the Charter text, 
if they so want.  Maybe the Chairs use github to store the presentaiton 
material at a WG meeting.  Maybe the Chairs request contributors to 
store the presentation material on github.

Some people might be prohibited by employer's policy from creating an 
account on github.  It is an assumptionn that I did see: the creator of 
a sharepoint repository assumed that people would prefer to use their 
company email address and not their other private address, which is 
typiccally used on github.

Alex

> 
> -m
> 
> 
> 
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>