Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] New xml2rfc release: v3.0.0

Henrik Levkowetz <henrik@levkowetz.com> Thu, 03 September 2020 10:55 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 535AB3A0E7B; Thu, 3 Sep 2020 03:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level:
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 OG6O9SOCb6Oe; Thu, 3 Sep 2020 03:55:45 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01D383A0E6A; Thu, 3 Sep 2020 03:55:45 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:50155 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1kDmu8-0003oY-5U; Thu, 03 Sep 2020 03:55:44 -0700
To: Jay Daley <jay@ietf.org>, Carsten Bormann <cabo@tzi.org>
References: <E1kDR4G-0008G7-M9@durif.tools.ietf.org> <207F74B8-412D-4D74-AC1F-67C252FCFE56@tzi.org> <3e7ed8f3-fd40-be1c-5efa-5460e68827b9@levkowetz.com> <5E44402C-6821-4768-91FF-EBF4E5672EE4@ietf.org>
Cc: rfc-markdown@ietf.org, XML2RFC Interest Group <xml2rfc@ietf.org>, XML Developer List <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <879aab5a-1a1a-94c7-5eeb-27d6908d995b@levkowetz.com>
Date: Thu, 3 Sep 2020 12:55:35 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5E44402C-6821-4768-91FF-EBF4E5672EE4@ietf.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XJWMuacB4KPdop2GbuuMKP1inLRoiUVXm"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, cabo@tzi.org, jay@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/XAONuFZgsrhYrxPxdWDqpqlj6T0>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] New xml2rfc release: v3.0.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2020 10:55:46 -0000

Hi Jay,

On 2020-09-02 22:36, Jay Daley wrote:
>> 
>>> You mention a “schema change board”, can you tell us more about the
>>> coordinates of that?
>> 
>> It's currently John Levine, Peter Saint-Andre, Robert Sparks and myself.
>> It was set up in order to have some way of moving forward (or decide to
>> not move forward) with various changes, whether registered as tickets,
>> requested by the RPC or through the RPC by document authors, or otherwise
>> brought up.
> 
> Just to provide some more context. When we had an RSE they were
> responsible for helping the RPC and the developer (Henrik) triage
> incoming change requests and decide how those were addressed, which
> included: saying ’no’; changing the XML; changing the schema; and
> changing xml2rfc.
> 
> John’s role as Temporary RFC Series Project Manager (TRFCSPM) doesn’t
> include this responsibility, which left a gap that Henrik has being
> trying to fill while doing everything else. Consequently, a small
> group has been formed to fill this gap as a temporary measure while
> the IAB process to determine the future role of an RSE progresses.
> That group is made up of Henrik as the developer, John as the
> TRFCSPM, Robert as the Tools Team PM and Peter as an RSOC rep.
> 
> ’Schema Change Board’ is a label I’ve not heard before for this small
> group and sounds more established and authoritative than this group
> is meant to be.

I'm happy to use any label that's put on the group, but would like to have
_some_ label to use when referring to it.


Regards,

	Henrik