[Ietf-and-github] Alexey Melnikov's No Objection on draft-ietf-git-github-wg-configuration-06: (with COMMENT)

Alexey Melnikov via Datatracker <noreply@ietf.org> Thu, 12 March 2020 10:56 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 4BD153A0B5F; Thu, 12 Mar 2020 03:56:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-git-github-wg-configuration@ietf.org, git-chairs@ietf.org, ietf-and-github@ietf.org, Christopher Wood <caw@heapingbits.net>, caw@heapingbits.net, francesca.palombini@ericsson.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <158401056823.18300.16488902811081953276@ietfa.amsl.com>
Date: Thu, 12 Mar 2020 03:56:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/uQMSCU5w8Z0yxx-a17l43JsgFR8>
Subject: [Ietf-and-github] Alexey Melnikov's No Objection on draft-ietf-git-github-wg-configuration-06: (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 10:56:09 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-git-github-wg-configuration-06: 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-github-wg-configuration/



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

**********************************************************************
* Note, that I am conducting an experiment when people aspiring to be*
* Area Directors get exposed to AD work ("AD shadowing experiment"). *
* As a part of this experiment they get to review documents on IESG  *
* telechats according to IESG Discuss criteria document and their    *
* comments get relayed pretty much verbatim to relevant editors/WGs. *
* As an AD I retain responsibility in defending their position when  *
* I agree with it.                                                   *
* Recipients of these reviews are encouraged to reply to me directly *
* about perceived successes or failures of this experiment.          *
**********************************************************************

The following comments were provided by Francesca Palombini
<francesca.palombini@ericsson.com>.

Francesca would have balloted *No Objections* on this document. She wrote:

Comment:

This draft is informational, but does put up requirements on IETF Secretariat
and tools team in order for readers to follow its possible use (develop certain
features, add certain tasks to IETF Secretariat). I see this draft as both a
wish list (valid at this point in time) and a guideline. If it would contain
only the possible guideline, I would understand that publishing it would have
value, but as it is I am not sure: what does publishing it add to having the
draft itself?