Content Stackers          Anne Gentle    anne@openstack.orgOpenStack Design Summit         November 2010
My Story           2
Documentation is Hard,Let’s Go Programming!                Source: Mattel                                 3
Content ‘Splosions•   Wiki                I find it incredibly hard to make sure that the                        users get...
Community Documentation• You’ve seen documentation.• You’ve participated on the social web.• You’re about to see the futur...
Stacker ApproachWe want:                   We will: to deliver content in a   1. Listen and Monitor way that involves our ...
1. Listen and Monitor•   Increase signal to noise ratio•   Control the fire hose flow•   Take feedback from the community•...
2. Audit and Curate• When you see something great, ask  permission to use it• Ensure content licensing works for you• Recy...
3. Involve and Engage• Come to doc sprints• License your content – Apache or Creative  Commons• Talk to us, blog with us, ...
Become a Content StackerWe want all sorts of contributors.• Join the Documentation  Mailing List• Create a wiki account at...
Any Questions?@annegentle                           Anne Gentlewww.facebook.com/          anne@openstack.orgconversationan...
Upcoming SlideShare
Loading in …5
×

OpenStack Content Stackers

1,788 views

Published on

  • Be the first to comment

  • Be the first to like this

OpenStack Content Stackers

  1. 1. Content Stackers Anne Gentle anne@openstack.orgOpenStack Design Summit November 2010
  2. 2. My Story 2
  3. 3. Documentation is Hard,Let’s Go Programming! Source: Mattel 3
  4. 4. Content ‘Splosions• Wiki I find it incredibly hard to make sure that the users get the right information from the docs.• Mailing Lists On the one hand, it seems that there is already too much information as people miss things• Launchpad Answers that are already in there. On the other hand, there is always information that people• IRC are looking for, and that is not in the docs.• Code - Gaël Varoquaux, developer, Mayavi2 project• Blogs• API 4
  5. 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. 5
  6. 6. Stacker ApproachWe want: We will: to deliver content in a 1. Listen and Monitor way that involves our 2. Audit and Curate community and opens 3. Involve and Engage collaboration. 6
  7. 7. 1. Listen and Monitor• Increase signal to noise ratio• Control the fire hose flow• Take feedback from the community• Repeat 7
  8. 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) 8
  9. 9. 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
  10. 10. Become a Content StackerWe 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
  11. 11. Any Questions?@annegentle Anne Gentlewww.facebook.com/ anne@openstack.orgconversationandcommunitywww.linkedin.com/in/annegentle

×