Agenda Roadmap Process

1
Agenda - Roadmap Process

• How living a document?
• Continuously updatable Web based document.
• Add a reminder to WG chairs to do it just
  before/after GGF. On the room booking from.
• Publish snapshots as an Informational Documents
• Twice a year as PDF.
• Needs a good naming scheme.
• Roadmap Working Group?
• Discuss - Ask for a BoF at GGF16.
• Needs an open discussion forum in any case.
• Exploit the WG process to create the WG.
• Mostly ADs
• Need a carefully written charter
• Relationship to interop fests?
• Discuss
• Possibly adding interop events to the road map
• No need, since the experience document should be
  there.
• Action ????

2
Agenda - Document Structure

• Do we include Informational Documents into
  Diagram?
• No.
• Do we include Published Documents in the Roadmap?
• Discuss.
• Yes, for history purposes.
• Selective.
• Action ADs - recommendations from history.
• Action Joel add pages for published documents.
• Include subsections for Groups with group
  description.
• Action To be provided by WG-Chairs
• Action ADs to review.
• Action Joel/Jem to provide an example and
  guidelines, eg no.
• Include introduction for each Area
• Action To be provided by ADs.
• Guide line less than one page, achievements,
  gaps, directions, Area view of the roadmap, cross
  refs to other areas.
• Structure Area, all groups, all document.
• Action Jem to assign AD homework
• Highlight reasons for roads taken or not taken.
• How do we include this? - No

3
Agenda - Document Structure Continued

• Do we include a Dependencies Chart?
• Discuss - Postpone for later, problems with
  referencing (published) docs
• Make static field lists pull downs where
  possible.
• Action Joel
• Change Grid Roles to Key Words.
• Initial list based on current roles.
• Action Joel and WG Chairs
• Add more complete document descriptions.
• Action WG-Chairs
• Action Joel/Jem to provide template example.
• Are the milestones right?
• What does the Public Comment field mean?
• Do we need more mile stones between First draft
  and PC.
• Malcolm

4
Agenda - Document Structure Continued

• Gap analysis sections by area.
• Action ADs
• Delete the sub section for schedule.
• But not the table
• Do we need to define
• No
• Interoperability?
• Interoperation?
• Code mobility?

5

• David Martin
• Ramin
• Andrew
• Franco
• Hiro
• Dave S
• Stephen P
• Ollo
• Mark
• Greg
• Mathew
• Malcolm

6
Documents

• Documents
• AG Concern about the process of taking things
  into Public Review. Two perspectives on the
  process. Either simply straight in to PC or have
  a significant quality check at initial GFSG
  review.
• GN GFSG can send it back to the authors before
  PC.
• DS Particularly for recommendations track
  documents.