Sprints and Stacks

Editor's Notes

• #7: I am a content stacker at Rackspace, here’s where I think we’re going
• #9: there are challenges to using these tools – social media amplifies errors and heightens drama in communities while also enabling more voices and sites.AmplificationDramaToo many channelsToo much datamap represents the number of unique authors in each Usenet newsgroup who appeared in the current year, 2003.
• #10: Making it work anyway.Use sprints, strategic stacks with analytics, licensing that enables tinkering, and purposeful collaboration to tune your open docs strategy. I’m going to walk through three areas: Community, Sprints, and Stacks of Data.
• #12: We have a schism – DocBook and RST. I have so far divided by audience since DocBook deliverables are more advanced, PDF output and comments enabled.
• #13: Translation has not yet been activated. I have only seen a Korean wiki pop up. I don’t know if tooling is the problem or if people just write in English to get the attention of the wide audience.
• #14: One hard tack and four softies.Despite writing the process up in detail, so far devs write RST, no one really writes DocBook yet.
• #15: First call was to Belinda Lopez, her advice was – work out challenges with licensing. But they had already decided on Apache. I challenged the use of Apache for content, it’s just hard to interpret, CC is much easier to explain. Still working with lawyers for wording.
• #16: I challenged the use of Apache for content, it’s just hard to interpret, CC is much easier to explain. Still working with lawyers for wording.Now moving towards licensing for training materials – slide decks, check. But what about lab setup, video, workshops, and exams? Learning how to license those.
• #17: By combining CC and Apache I can now welcome blogger’s material
• #18: Publishers want OpenStack content. I feel like I’m in a fight to be an acquisitions editor some days. Everyone wants an OpenStack book, or blog entries about OpenStack to publishion their site. I was surprised at this.
• #20: Originally had doc sprint during design summit, moved it to earlier dateExpectation – to hold these regularly, reality, releases dictated when to hold themTiming has changed again to six month releases with milestone releases in between. Doc sprints need a rethink.
• #21: Eric Holscher – read the docs - said at Pycon, Devs need to write for other devs – strongly believe what ReadTheDocs.org guy preaches now. This is a 180 degree turn for me.
• #22: Barrier to entry is quite high with BZR and Launchpad. Yes I can walk through Windows contributors but they give up early. We are moving to git for code storage – how will that affect doc contributions? Doc contributors need access to people they can interview incessantly. Plus they need access to hardware, big time. Neither are easy to offer now.
• #23: We have people who desperately want to be involved with OpenStack – get led to docs, but have no idea how to write or make images or…When you want something done, ask a busy person. Unless the busy person just answers email all day.
• #25: Comments are going great, now users answer each other. I did a content audit, does a community audit also make sense? We are seeing some dilution though with too many sites such as a new forums site and Launchpad Answers also vying for attention.
• #26: Also thinking about a tweet chat – gets out of the IRC mold which might work well for a good portion of our users
• #28: Curated search engine plus search analyticsWorking on loyalty, bounce rateProof of the PDF popularity
• #31: We came out of the gate with way too many topics out there. We quickly learned that with too many topics and not enough interaction to start, it made the community seem empty. It’s what I call ‘empty restaurant syndrome’ — if you look in a window and no one is in there, you likely won’t go in.– Mike HardyStrategic communications program managerPitney-Bowes
• #33: Next – Launch and Learn
• #34: I plan to keep iterating, keep prioritizing, keep having fun, and keep learning. Join me!