[glue-wg] REMINDER: GLUE WG teleconference, Tuesday, November 12, 2019

[Navarro, JP]

I think we should start creating the entire OGF-GLUE githug directory structure, identify all the documents we will need to convert, and even put placeholders in GitHub. I’m willing to help out and work on it in parallel to GLUE 2.1 as long as we don’t make the conversion a pre-requisite to releasing 2.1.

JP



On Nov 12, 2019, at 11:17 AM, Sill, Alan <alan.sill at ttu.edu<mailto:alan.sill at ttu.edu>> wrote:

This would be fine also, but can I suggest that a document be started to begin the conversion process so that we can start any future revisions from Markdown?

Alan

On Nov 12, 2019, at 11:14 AM, Navarro, JP <navarro at mcs.anl.gov<mailto:navarro at mcs.anl.gov>> wrote:

I vote to keep it simple and focus on getting 2.1 out the door. Converting to Markdown, git, or other editing and writing tools can be done as a separate future activity and is broader in scope that the 2.1 document. It applies to all the rendering documents and everything else we currently have hosted on ogf.org<http://ogf.org/>.

Given the two online editing choices I think Google docs may be the easiest.

JP


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20191112/51dd23e1/attachment-0001.html>