Content Stackers

Anne Gentleanne@openstack.org

OpenStack Design SummitNovember 2010

2

My Story

3

Documentation is Hard, Let’s Go Programming!

Source: Mattel

Content ‘Splosions

• Wiki• Mailing Lists• Launchpad Answers• IRC• Code• Blogs• API

I find it incredibly hard to make sure that the users get the right information from the docs. On the one hand, it seems that there is already too much information as people miss things that are already in there. On the other hand, there is always information that people are looking for, and that is not in the docs.

- Gaël Varoquaux, developer, Mayavi2 project

4

5

Community Documentation

• You’ve seen documentation. • You’ve participated on the social web. • You’re about to see the future of open source

documentation at OpenStack.

Stacker Approach

We want:to deliver content in a way that involves our community and opens collaboration.

We will:1. Listen and Monitor2. Audit and Curate3. Involve and Engage

6

1. Listen and Monitor

• Increase signal to noise ratio • Control the fire hose flow• Take feedback from the community• Repeat

7

8

2. Audit and Curate

• When you see something great, ask permission to use it

• Ensure content licensing works for you • Recycle and reuse (single source if possible)

3. Involve and Engage

• Come to doc sprints• License your content – Apache or Creative

Commons• Talk to us, blog with us, listen with us• Read the content

9

Become a Content Stacker

We want all sorts of contributors.

• Join the Documentation Mailing List

• Create a wiki account at wiki.openstack.org

• Create a Launchpad account• Have a doc sprint at a meetup• Invite one or two people to

collaborate on Etherpad• Make OpenStack

documentation best-in-class

10

Any Questions?

Anne Gentleanne@openstack.org

@annegentle

www.facebook.com/conversationandcommunity

www.linkedin.com/in/annegentle