Thanks – I noticed that and think it is useful. Even better IMO is a world where no special local software must be installed on my computer to take what is basically a text document and generate an XML file that can in turn be used to generate an I-D. Either a copy/paste into a form or one button to publish would be cool (and probably make it easier for new contributors).
Jason
From: Martin Thomson <martin.thomson@xxxxxxxxx>
Date: Monday, July 16, 2018 at 4:56 PM
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com >
Cc: Aaron Falk <aaron.falk@xxxxxxxxx>, Lars Eggert <lars@xxxxxxxxxx>, IETF discussion list <ietf@xxxxxxxx>
Subject: [EXTERNAL] Re: Note Well & GitHub
On Mon, Jul 16, 2018 at 4:44 PM Livingood, Jason <Jason_Livingood@xxxxxxxxxxx> wrote:
[JL] It’d be awesome if perhaps the tools team or someone created a sample starting GitHub project with the Note Well and anything else useful and then a WG could just clone that repository when they started up. I looked around quite a bit to see what other WGs were doing on GitHub before I created the IASA2 one and probably got a bunch of stuff wrong. For example, the WG does not expect to have many I-Ds but if we did I might create a drafts folder to contain them all, as I did with the Meetings folder. On the other hand there’s enough variation in WGs that we probably don’t want to over-specify things.
You might be interested in https://github.com/
martinthomson/i-d-template
[JL] BTW, don’t get me started on taking something from GitHub to upload a draft on the IETF site. 😉 IMO that’s an area of friction for document authors that should/could be made much easier.
The above includes a means of automating that process.
Jason,
+1 to that, starting with Kramdown as the original source.
Cheers,
Andy
On Wed, Jul 18, 2018 at 2:53 PM, Livingood, Jason <Jason_Livingood@xxxxxxxxxxx> wrote:
