IETF Logo Mail Archive

Re: [Ietf-and-github] [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt

Kent Watsen <kent+ietf@watsen.net> Fri, 08 March 2019 20:39 UTC

Return-Path: <010001695f07d926-00d6192b-ac68-42a2-b35d-4d855208b542-000000@amazonses.watsen.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 8E001127962 for <ietf-and-github@ietfa.amsl.com>; Fri, 8 Mar 2019 12:39:06 -0800 (PST)
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 (1024-bit key) header.d=amazonses.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 exZhiyQLfzDP for <ietf-and-github@ietfa.amsl.com>; Fri, 8 Mar 2019 12:39:05 -0800 (PST)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEA441277E7 for <ietf-and-github@ietf.org>; Fri, 8 Mar 2019 12:39:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1552077543; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=SrD+kbpcRgi0d8c8sgeLI4VDIQubUwrEhpCH3IeWXqM=; b=KWZL621L3RpoG3iJu8OTedf/rh+Wb4w8sneH+U6EWpQMx6A6TchFQ/jmh46stuPC zj0JpmQnJQTfEF58pM2rGp77HC8CeE2zqQAVLWdE2G79bfg3gmV9tgceF/5ABPiSnwt 7epWbvwvNdYWt176o9qH7d6eWMDBp6EzoTn+DRgE=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 08 Mar 2019 20:39:03 +0000
References: <155112114000.10633.2593235416875795961.idtracker@ietfa.amsl.com> <01000169261421c7-978ecbf5-dcc4-4738-ba58-f409ce6adaf1-000000@email.amazonses.com> <2e4a853c-6622-81e8-adf5-02deb3e1d6e3@gmx.de> <010001692a9f8f0f-a4ba1870-6959-4518-8503-6e30424b1ac9-000000@email.amazonses.com> <ea32731b-55cf-aa67-a87a-184dfbad6d49@gmx.de> <010001692ab8ef80-96b79bab-c831-4917-b5a2-edc3a37ab952-000000@email.amazonses.com> <c0ecb9bc-793e-fa36-c916-1027ec12ddea@joelhalpern.com> <ef58bede-02b8-dcb8-1ffd-eef921e9a715@levkowetz.com> <3849BD6A-DD18-4624-8ED6-87B968211B5B@stewe.org> <20aaf8c4-2b85-ac28-f780-37c37d62843b@levkowetz.com>
To: RFC Interest <rfc-interest@rfc-editor.org>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
In-Reply-To: <20aaf8c4-2b85-ac28-f780-37c37d62843b@levkowetz.com>
Message-ID: <010001695f07d926-00d6192b-ac68-42a2-b35d-4d855208b542-000000@email.amazonses.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.03.08-54.240.8.96
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/HvFDinK5xSBJrpsXaqEzf07SPl4>
Subject: Re: [Ietf-and-github] [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
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: Fri, 08 Mar 2019 20:39:07 -0000

Hi All,

I hope that this work seems interesting to you.   I don't actually know, as there have been no comments to the effect yet.   Maybe folks are reserving comments for a presentation in Prague, but unfortunately I won't be able to make Thursday's WG session.

Assuming this work is interesting, is this the right forum for it?   I think this work is covered by the "git" charter (tooling, automation, best practices, etc.), and it has high-potential for affecting the xml2rfc format, but maybe there's a better home?

Lastly, what steps need to be taken to have a solution everyone is happy with?   I'm assuming standard RFC publication process, but are there any special considerations that need to be observed given that it's a tool for the community?

Regards,
Kent

v2.23.0 | Report a Bug | By Email