Re: [Last-Call] Genart last call review of draft-ietf-git-using-github-04
Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 06 March 2020 16:32 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93ADB3A0A5E; Fri, 6 Mar 2020 08:32:03 -0800 (PST)
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 oJpue14bqFjL; Fri, 6 Mar 2020 08:32:02 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 BEC453A0A5D; Fri, 6 Mar 2020 08:32:01 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 026GVwJF008664; Fri, 6 Mar 2020 17:31:58 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6081120441A; Fri, 6 Mar 2020 17:31:58 +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 4F986204396; Fri, 6 Mar 2020 17:31:58 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 026GVwbs012940; Fri, 6 Mar 2020 17:31:58 +0100
To: last-call@ietf.org
Cc: ietf-and-github@ietf.org, draft-ietf-git-using-github.all@ietf.org
References: <158250611906.1067.14505081937854561120@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3450f158-be66-71d3-b29a-6751650d64af@gmail.com>
Date: Fri, 06 Mar 2020 17:31:58 +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: <158250611906.1067.14505081937854561120@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/last-call/eOjH2pRa4zh6Dy8YX7qzteRER04>
Subject: Re: [Last-Call] Genart last call review of draft-ietf-git-using-github-04
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 16:32:04 -0000
Hi, I take advantage of this Last Call about github use at IETF to give my comments about writing I-Ds on github. We are writing a draft with a few colleagues at IETF about a 6MAN topic. We initially thought we'd use the Word template but quickly we moved to xml2rfc and github storage. - the xml2rfc.ietf.org GUI generates a *.txt.pdf file, whereas it should generate a *.pdf file. That makes difficult to talk about a 'txt' file (is it the ASCII or the .txt.pdf?). I have been told I should report this to 'tools-discuss' email list, which I will do one day. - the github folder containing the xml source should be as small as possible, and have at least as possible additional clutter files. This is not like a project of C files where there are no numerous *.c and *.h and *.asm files. There is just one source: the xml. - I wrote a README about how to use that xml file. There are to distinct operations: compilation and submission. - despite my efforts of explaining, people still prefer to exchange the files by email. This feedback is from working with several groups on several xml drafts on several gihub repositories. - this the README that I wrote and put in the github repository of the xml file of the Internet Draft we currently write: ----------------------------------------------------------------------- 0. on Windows, use the free Github Desktop tool. Within it, use buttons like 'Commit to master' and others like 'Push origin' in order to upload the files that you modify. 1. How to 'compile' the .xml file: - go to https://xml2rfc.tools.ietf.org - press the button to select a file - choose the .xml file - leave the 'Output format' and 'Options' to their default - click 'Submit' That displays the .txt file in the browser, but can also create .txt and .pdf files, depending on how the Output format is Optioned. That does not submit the draft to the IETF. 2. In order to submit a draft, upload the .xml at the address https://datatracker.ietf.org/submit/ 3. do not commit the xml file to github before you are sure it compiles safely on xml2rfc.tools.ietf.org Alex Le 24/02/2020 à 02:01, Brian Carpenter via Datatracker a écrit : > Reviewer: Brian Carpenter > Review result: Ready with Issues > > Gen-ART Last Call review of draft-ietf-git-using-github-04 > > I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed > by the IESG for the IETF Chair. Please treat these comments just > like any other last call comments. > > For more information, please see the FAQ at > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. > > Document: draft-ietf-git-using-github-04.txt > Reviewer: Brian Carpenter > Review Date: 2020-02-24 > IETF LC End Date: 2020-03-03 > IESG Telechat date: > > Summary: Ready with issue > -------- > > Comment: > -------- > > I've tracked this document since the -00 version and I think it is clear > and represents WG consensus. > > Issues: > ------- > > Is this draft intended to become part of BCP25? I think it would be > useful for the IESG to clarify this rather than leave it to the RFC Editor. > > Nit: > ---- > >> 3.4. Document Formats >> >> In addition to the canonical XML format [RFC7991], document editors >> might choose to use a different input form for editing documents, >> such as Markdown. Markdown-based formats are more accessible for new >> contributors, though ultimately decisions about format is left to >> document editors. > > s/is/are/ > >
- [Last-Call] Genart last call review of draft-ietf… Brian Carpenter via Datatracker
- Re: [Last-Call] Genart last call review of draft-… Martin Thomson
- Re: [Last-Call] [Gen-art] Genart last call review… Alissa Cooper
- Re: [Last-Call] [Gen-art] Genart last call review… Brian E Carpenter
- Re: [Last-Call] Genart last call review of draft-… Alexandre Petrescu
- Re: [Last-Call] Genart last call review of draft-… Kjetil Torgrim Homme
- Re: [Last-Call] Genart last call review of draft-… Alexandre Petrescu
- Re: [Last-Call] Genart last call review of draft-… Kjetil Torgrim Homme
- Re: [Last-Call] Genart last call review of draft-… Alexandre Petrescu