Summit Content Team

Summary

(Full summary statement to be published 17 July 2013.)

Roles

• Content Anchors - Mozilla executives and key stake holders responsible for generating and grounding Summit purpose. Work with Track Leads to advise on alignment of Summit purpose and track goals.
• Content Team - team responsible for generating content, vetting program agenda, populating and mobilizing the Summit program. This is the primary role of all Delegates.
• Content Team Lead - drives Summit Content Team by framing communication flow and activities for all content generation from team. Lead liaison between Content and Program teams.
• Delegates - though encompasses all members at Summit Assembly, used here specifically to mean delegates working with Track Leads to align Summit purpose to track goals, co-create, refine, populate and help lead program agenda.
• Track Lead - Delegate leads that oversee track groups. Work closely with Content Anchors to align purpose of Summit and track goals.

• Program Team - team responsible for creating the schedule based on the work of the Content Team (e.g., keynotes, sessions, demos, branding, hosting, open spaces, etc.). When final Summit Program is published, some Delegates from Content Team will become members of the Program Team.

Summit Tracks

• Purpose and Strategy
  • Content Anchors: Mitchell Baker, Mark Surman
  • Track Leads: Lukas Blakk, Michelle Thorne
  • Link to Purpose and Strategy etherpad.
• Product, Technology and Innovation
  • Content Anchors: Jay Sullivan, Brendan, Chris Lee, & Harvey Anderson
  • Track Leads: David Ascher, David Herman
  • Link to Product, Technology and Innovation etherpad.
• People and Process
  • Content Anchors: Debbie, Jim Cook
  • Track Leads: Michael Coates, Gandalf Braniecki
  • Link to People and Process etherpad.

Work Timeline

• Phase I: Co-creating a Summit program
  • Part 1: Aligning Summit purpose and content to generate v.1 of Summit program (16 July – 1 August)
    • Deliverable: Brief proposal of aligned purpose and content for Program Team
    • Due Date: 1 August 2013
    • Timeline of activities:
      • 16 - 22 July: Track Leads meet with Delegates to communicate summit purpose, clarify and align track goals to purpose, and articulate any necessary recommendations for Program Team. Delegates populate top level Summit Program roles for v.1.
      • 22 – 26 July: Content Anchors meet with Track Leads to refine goals and recommendations.
      • 29 – 31 July: Track Leads, Delegates, and Content Team Lead clarify roles of Summit Program aligned to Summit purpose and track goals.
      • 1 August: Content Anchors, Track Leads and Content Team Lead deliver proposal to Program Team.
  • Part 2: Vetting and Refining v. 1 of Summit Program
    • Deliverable: Feedback for revisions on Summit Program for v. 1
    • Due Date: 6 August 2013
    • Timeline of activities:
      • 1 August: Summit Program v. 1 shared with all Delegates for feedback.
      • 1 – 5 August: Content Anchors, Track Leads, Delegates vet and refine v.1
      • 6 August: Refined v.1 sent back to Program Team
  • Part 3: Vetting and Refining v. 2 of Summit Program
    • Deliverable: Feedback for revisions on Summit Program for v. 2
    • Due Date: 13 August 2013
    • Timeline of Activity:
      • 8 August: Summit Program v. 1 shared with all Delegates for feedback.
      • 8 – 12 August: Content Anchors, Track Leads, Delegates vet and refine v.1
      • 13 August: Refined v.2 sent back to Program Team
  • Part 4:
    • Deliverable: Final Summit Agenda
    • Due Date: August 24
    • Timeline of Activity:
      • 22 August: Summit Program v.3 shared with Content Anchors
      • 24 August: Content Anchors give final feedback to Program Team
      • 27 August: Agenda Published to Project

• Phase II: Populating Summit Program (27 August – 27 September)

• Phase III: Delivering Summit Program (30 September – Summit and beyond)