What's it like to not just allow community contributions to your documentation, but depend on them? What if literally anybody could edit the docs and see your work as you write? Mozilla doc team members share their experiences working with radically open documentation for developers. Presentation by Eric Shepherd and Janet Swisher at the Technical Communication Summit, May 2011
Text of Radically open documentation
Radically Open Documentation
Eric Shepherd (@sheppy)Janet Swisher (@jmswisher)
Mozilla Developer Network
Session hashtag: #radopen
Why Be Open?
Why Be Open?The goals of being open are:
•Participation: Rocket fuel for smarter collaboration.
•Agility: Speed. Flexibility. Getting stuff done.
•Momentum: Communities want to push boulders that are already rolling.
•Rapid prototyping: Iterating and refining as we go.
•Leverage: Getting greater bang from limited resources. Punching above our weight.