Topic Notes Follow-up 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 will be required to produce native content for selectedf selected Doc types (see Contributor & Committer roles review below) Structure Review draft of latest structure Contributor & Committer roles Review role definitions Review assignments View filename ONAP Doc Flow 7-07-2017.pptx height 250
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 Clarify what documentation needs to be formally captured and managed vs. use of the Wiki gg2147@att.com 18 Jul 2017 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 Matthew Harffy , gg2147@att.com 11 Jul 2017 Identify a formal Documentation contact for each Project gg2147@att.com 18 Jul 2017 Create initial draft for M1 Deliverables 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 Liu Yang 11 Jul 2017 Clarify role of Contributor and Committers by Doc type gg2147@att.com 18 Jul 2017