Re: [Teas-ns-dt] Github?

I agree.  Who has write permission to that part of the repository?

If you would prefer, I can take the current sync’d version of the XML file and add it to the repository under “definitions” – most likely as a pull, which whoever is the “owner for that can then “merge” into the folder.

If I do that, I would also add a README.md file and a Makefile (which would be similar to the one under framework) which could be used to verify the results of any proposed pull against that part of the repository.

The README.md file would (as it does under the framework folder) mostly describe the process for using “make” (among other things).

The main thing – for using XML only – would be to get the local version of both “make” and “xml2rfc.”  That would almost certainly mean working with a UNIX/Lynux-like environment (which can be done on a MS Windows platform, using Cygwin).

But there would remain the option to resolve changes using E-Mail…

--
Eric

--
Eric

From: Shunsuke Homma <s.homma0718@gmail.com>
Sent: Friday, May 1, 2020 9:16 PM
To: Kiran Makhijani <kiranm@futurewei.com>
Cc: Eric Gray <eric.gray@ericsson.com>om>; teas-ns-dt@ietf.org
Subject: Re: [Teas-ns-dt] Github?

Hi Eric,

The authors were managing the XML for the definition draft on my personal github repository, because it was an individual work.

Now, the draft is published as NS-DT's contribution, and it may be a good timing for moving XML into the nsdt github repository.

Regards,

Shunsuke

2020年5月2日(土) 0:22 Kiran Makhijani <kiranm@futurewei.com<mailto:kiranm@futurewei.com>>:
Here’s the xml - would you like to pull from here?

https://github.com/s-homma/draft-nsdt-teas-transport-slice-definition?<https://protect2.fireeye.com/v1/url?k=600a3aad-3eaa80c3-600a7a36-869a14f4b08c-dd98bd8b43c3e9e2&q=1&e=43eb935f-6beb-4d72-82e7-77c23db3dd7b&u=https%3A%2F%2Fgithub.com%2Fs-homma%2Fdraft-nsdt-teas-transport-slice-definition%3F>

Any other way I can make it easier for you?
Regards
Kiran

________________________________
From: Eric Gray <eric.gray@ericsson.com<mailto:eric.gray@ericsson.com>>
Sent: Friday, May 1, 2020 8:18:11 AM
To: Kiran Makhijani <kiranm@futurewei.com<mailto:kiranm@futurewei.com>>
Cc: teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org> <teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>>
Subject: Github?

I was going to start looking into the XML version for the definitions draft via github, and discovered that – if you are using an XML version to generate your text version – it is not in our github repository.

Trying to put in a “pull” against the Text version is very much unnecessarily complicated (mostly because of the editing changes associated with getting the right pagination, footer and header information placement, etc. – which would, among other things, make merging multiple changes very messy and is the main advantage in using either the Markdown and/or XML formats).

So I guess I will just focus on compiling a set of specific editing suggestions for the definitions draft.  Note that this too will be messy, making the realistic assumption that not all of the suggested changes will be accepted as proposed, because it will be necessary to produce a summary of the changes that are acceptable to everyone, after allowing for discussion and responses.

Hopefully, I will complete those editing suggestions today.

--

Eric
--
Teas-ns-dt mailing list
Teas-ns-dt@ietf.org<mailto:Teas-ns-dt@ietf.org>
https://www.ietf.org/mailman/listinfo/teas-ns-dt