2017-06-29 Doc Project Meeting

Topics, Notes, and Follow-Up Tasks

Topic	Notes	Follow-up

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 Jun 29, 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 PaulJun 28, 2017 Clarify what documentation needs to be formally captured and managed vs. use of the Wiki @gg2147@att.com Jul 6, 2017 Create initial draft of Documentation Guidelines - Process @gg2147@att.com Jul 11, 2017 Create initial draft of Documentation Guidelines - Style Guide @Andrea Anderson Jul 11, 2017 Create initial draft of Committer Checklist (e.g. Consistency, Style Guide, Grammar, etc.) @Matthew Harffy, @gg2147@att.com Jul 11, 2017 Identify a formal Documentation contact for each Project @gg2147@att.com Jul 6, 2017 Create initial draft for M1 Deliverables @Rich Bennett Jun 30, 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 Jul 11, 2017