Topic Notes Follow-up Structure Load structure into Gerrit Tool Chain Draft Comparison and Recommendation of Document Tool Chain
Require plain text content - IF it supported as input into Pandocs. Markdown, ReStructured Text, etc. Goal is "white label" content only Will still require transformation tools to enable appropriate HTML output Doc team may be required to produce native content
Meetings Move regular Tuesday meetings earlier (e.g. start at 8 or 9 ET)? Would be better for both Europe and Asian participants Next Steps Regroup current Wiki Topics into simpler structure based on Audiences / Roles (e.g. Developer, User, Operations, etc.) gg2147@att.com 29 Jun 2017 Schedule special meeting with project team members on June 29 from 7-8 pm ET to review 1) draft structure and 2) Tool chain options Kenny Paul 28 Jun 2017 gg2147@att.com 06 Jul 2017 Draft what it means to Validate content gg2147@att.com 06 Create initial draft of Documentation Guidelines - Process gg2147@att.com 11 Jul 2017 Create initial draft of Documentation Guidelines - Style Guide Andrea Anderson 11 Jul 2017 Create initial draft of Committer Checklist (e.g. Consistency, Style Guide, Grammar, etc.) Matthew Harffy , gg2147@att.com 11 Jul 2017 gg2147@att.com 06 Jul 2017 Rich Bennett 30 Jun 2017 Try combining two sets of disparate content and combining them into a real world piece of master document (hiearchy) - e.g. Release Notes Spencer Seidel 11 Jul 2017