Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TopicNotesFollow-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



MeetingsMove regular Meeting ScheduleMove 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.) Gregory Glover 
  •  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 
  •  Clarify what documentation needs to be formally captured and managed vs. use of the Wiki Gregory Glover   Draft what it means to Validate content Gregory Glover
  •  Create initial draft of Documentation Guidelines - Process Gregory Glover 
  •  Create initial draft of Documentation Guidelines - Style Guide Andrea Anderson  
  •  Create initial draft of Committer Checklist (e.g. Consistency, Style Guide, Grammar, etc.) Matthew Harffy, Gregory Glover  
  •  Identify a formal Documentation contact for each Project Gregory Glover 
  •  Create initial draft for M1 Deliverables Rich Bennett 
  •  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