Lessons in Community from Open Source projects

30
Lessons in Community from Open-source Projects Janet Swisher, Mozilla Technical Writer/Community Steward STC Toronto Management Day, Feb 29, 2012

description

What does it mean to collaborate in creating user assistance? What are some ways that community members (customers, partners, or others in your company) can contribute to user assistance? How can professional technical communicators safeguard accuracy, and certify authority in an open, collaborative environment? In this session, I provide my perspective on these issues, based on my experiences in both theopen source and traditional software worlds.

Transcript of Lessons in Community from Open Source projects

Page 1: Lessons in Community from Open Source projects

Lessons in Community from Open-source Projects

Janet Swisher, MozillaTechnical Writer/Community Steward

STC Toronto Management Day, Feb 29, 2012

Page 2: Lessons in Community from Open Source projects

Discussion is encouraged

Photo by HoboElvis

Page 3: Lessons in Community from Open Source projects

What I’m planning to talk about

• What is community?

• What is community-generated content?

• How does community work?

• Contributing to an open source community

• Managing community-generated content for business

Page 4: Lessons in Community from Open Source projects

Tell me about yourself

Page 5: Lessons in Community from Open Source projects

DEFINITIONS

Page 6: Lessons in Community from Open Source projects

What is community?

“It is not merely the group that generates community, but the interactions within it.”―Jono Bacon, The Art of Community

Page 7: Lessons in Community from Open Source projects

What is community-generated content?

• Wiki-based docs• Wiki-based

knowledge article• Open source docs

(parallel to code)

• Comments on web-based docs

• Comments on blogs

• Support forums

Page 8: Lessons in Community from Open Source projects

What CGC is NOT

Page 9: Lessons in Community from Open Source projects

“Crowds aren’t smart. Communities of peers are.” ― Matt Thompson, Mozilla

Photo by blmurch

What CGC is NOT

Page 10: Lessons in Community from Open Source projects

Which comes first?

“The Apache Software Foundation … believes that its first order of business is creating healthy software content development communities focused on solving common problems; good software content is simply an emergent result.”―Brian Behlendorf, former president of the Apache Software Foundation

Page 11: Lessons in Community from Open Source projects

Listen

ConnectShare

CGCCommunity

Solutions

Page 12: Lessons in Community from Open Source projects

CONTRIBUTING

Page 13: Lessons in Community from Open Source projects

Start modestly

• Introduce yourself• Listen• Get to know the

community• Contribute in small

ways• Build support for

bigger changes

Photo by sean dreilinger

Page 14: Lessons in Community from Open Source projects

Meritocracy

• Balance getting stuff done vs. talking about it

• Your expertise may be respected, or not

• Others will edit your content

Photo by sarahbest

Page 15: Lessons in Community from Open Source projects

Communication Channels

• Embedded in the system • Mailing lists• Newsgroups — whut?• IRC — whut?

Page 16: Lessons in Community from Open Source projects

A few words about style guides

Page 17: Lessons in Community from Open Source projects

MANAGING CGC

Page 18: Lessons in Community from Open Source projects

Who is your community?

Tech PubsSales

Engineering

Consulting

Support

Partners

Customers

General Public

Page 19: Lessons in Community from Open Source projects

Realistic expectations

Photo by JoshBerglund19

Page 20: Lessons in Community from Open Source projects

Who will contribute?

90%: “lurk” but never contribute

9%: do a little 1%: do a lot

Jakob Nielsen, Participation Inequality: Encouraging More Users to Contribute

Image by verbeeldingskr8

Page 21: Lessons in Community from Open Source projects

Why do people contribute?

“Why do people contribute free documentation? Results of a survey,” Andy Oram

Page 22: Lessons in Community from Open Source projects

Challenges

• Access–Who can see, contribute, approve?

• Accuracy–How do you make sure it’s correct?

• Authority–How can readers trust it?

Page 23: Lessons in Community from Open Source projects

Review Process

Patch Model• Submit > Review >

Publish• Content is not public

until it is reviewed.

Wiki Model• Submit > Publish >

Review• Content is public

immediately.• May want to visually

differentiate unreviewed content.

Page 24: Lessons in Community from Open Source projects

Pitfalls

Image by @joefoodie

Page 25: Lessons in Community from Open Source projects

Villains

Photo by istolethetv

Page 26: Lessons in Community from Open Source projects

Avoiding pitfalls and villains

• Vigilant content review

• Good, easy-to-find guidelines and templates

• Patience

• Constant community engagement

Page 27: Lessons in Community from Open Source projects

Paths to success

• Welcome Wagon• Tasks for newbies• Multiple communication channels• Recognition and reputation• Mentor and empower• Gratitude

Page 28: Lessons in Community from Open Source projects

Take-aways

Photo by renaissancechambara

Page 29: Lessons in Community from Open Source projects

Resources

• The Art of Community: Building the New Age of Participation, Jono Bacon

• Conversation and Community: The Social Web for Documentation, Anne Gentle

• “Participation Inequality: Encouraging More Users to Contribute,” Jakob Nielsenhttp://www.useit.com/alertbox/participation_inequality.html

• “Why do people write free documentation? Results of a survey,” Andy Oramhttp://onlamp.com/onlamp/2007/06/14/why-do-people-write-free-documentation-results-of-a-survey.html

Page 30: Lessons in Community from Open Source projects

Thanks!

Twitter: @jmswisherEmail: [email protected]