The document discusses the OpenStack Content Team goals of leveraging community resources to produce more content, engaging subject matter experts, and incorporating user feedback. It provides an agenda for the meeting which includes recapping goals, how attendees can help now, completed and future goals. Completed goals included content for the Icehouse release in April 2014. Future goals include updating marketing portals, producing monthly webinars, videos, collateral, and finalizing personas. The document outlines the content team's scope of work, types of content, and process for developing and submitting new content.

1. OpenStack
Content Team Working Meeting
Margie Callard
margie@openstack.org
May 2014

2. 2
Agenda
‣ Recap of goals/structure for team
‣ How you can help now
‣ What’s done/what we can work on
‣ Feedback

3. 3
OpenStack Content Team Goals
1. Leverage community resources to produce more content
2. Engage community subject matter expertise
3. Incorporate direct feedback from customers and users

4. 4
1) Tactics:
• Sign up to be a contributor
• 10 people, 5 hours/month
• Dedicate to complete by Paris
• Tell me what times are best to meet – doodle
• Meet monthly
• Work through mailing list and google docs
2) Strategy
• Review what we’ve looked at so far
• Start thinking what else you want to add
• Vote on it early June
• Let’s start working
• Content sprint or thought sprint?
How you can help now

5. 5
Completed Foundation Content Goals
1. Icehouse discussions – End of March
2. Icehouse strategy deck for team – early April
3. Icehouse briefings press/analysts – early April
4. Icehouse release: demo, updated landing page, software
pages updated, webinar: April 17

6. 6
Future Goals/Ideas
• Marketing portal updates: General look/feel, how else to
organize?
• Monthly webinars
• Videos: OpenStack 101 – Kathy
• Potential collateral
• How to get involved with OpenStack
• User stories/updating format to fit with videos
appropriately
• Finalizing personas
• Brand guide

7. 7
Addendum
Background on content team

8. 8
• Current
• Gap analysis: identifying content that’s missing and setting
priorities around those gaps for completion
• Future
• Protect positioning: developing content that’s consistent
with positioning and branding
• Keep current: update content as it changes in a timely
manner
Content team: scope of work

9. 9
• Output: Educational, non-commercial
• Mediums: print collateral, videos, website, webinars, etc. Gap
analysis: identifying content that’s missing and setting priorities
around those gaps for completion
• Distribution
• Via marketing portal to ecosystem companies, directly to
users at events and webinars
• Creative commons licensing to allow others to use
Content team: type of content

10. 10
1. Team prioritization of content approved for development
2. Team member volunteers resources for content and potentially
forms a sub-group, sets deadline for completion.
3. Keep in touch with Foundation for questions and submit drafts
back to Content Team for group review
4. Once draft received, group has a formal period of time to review
through Google docs and submit comments before Foundation
works with assigned resource to finalize
Content team: Process to develop/submit content