OpenStack Content Team Working Meeting

Margie Callardmargie@openstack.orgMay 2014

2

Agenda

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

3

OpenStack Content Team Goals

1. Leverage community resources to produce more content

2. Engage community subject matter expertise3. Incorporate direct feedback from customers and

users

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

Completed Foundation Content Goals

1. Icehouse discussions – End of March2. Icehouse strategy deck for team – early April3. Icehouse briefings press/analysts – early April4. Icehouse release: demo, updated landing page,

software pages updated, webinar: April 17

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

AddendumBackground on content team

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

• 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

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