Engaging developers in Mozilla docs
-
Upload
janet-swisher -
Category
Technology
-
view
2.553 -
download
2
description
Transcript of Engaging developers in Mozilla docs
![Page 1: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/1.jpg)
Engaging Developers in Mozilla’s Documentation
Janet Swisher (@jmswisher)
Mozilla Developer Network
![Page 2: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/2.jpg)
Why are we here?
![Page 3: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/3.jpg)
What is MDN?https://developer.mozilla.org
![Page 4: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/4.jpg)
What Is MDN?Content
•Web development: reference, tutorials, and guides
•Mozilla APIs
•Mozilla project (building, testing, debugging, process)
• Firefox add-on development
Audience
• Web developers
• Developers using Mozilla code/libraries
• Developers working on the Mozilla project
• Add-on developers
![Page 5: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/5.jpg)
Where content comes from
•Some historical content (e.g., inherited from Netscape)
•New material
•Some paid for by Mozilla
•Some contributed by Mozilla community
•Some from other communities
![Page 6: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/6.jpg)
Documentation process• Using Bugzilla as a documentation planning tool
• Documentation-specific bugs
• Tags on engineering bugs
• Prioritization and delegation
• Tagging for review
![Page 7: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/7.jpg)
Communication channels
• IRC (#devmo on irc.mozilla.org)
• Mailing list/news group/Google group ([email protected])
• Blog posts (http://hacks.mozilla.org)
• Talk pages (under-used)
![Page 8: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/8.jpg)
MDN community meetings
• Every other Wednesday, 10 am PT
• Agenda in Mozilla project wiki
• Discussion in IRC
![Page 9: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/9.jpg)
Wiki Wednesdays
• Target Audience: Mozilla developers
• Blog post, with chunks to topic-specific mailing lists
• Credit given to last week’s contributors
• Special email alias
![Page 10: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/10.jpg)
Doc sprints• First one in-person in Paris, Oct.
2010
• Virtual, late January 2011
• Virtual, early April 2011
• Following this conference
![Page 11: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/11.jpg)
Why people don’t contribute
•They don’t realize it's a wiki
•They don’t want to bother setting up an account
•They’re intimidated by changing “the” documentation
![Page 12: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/12.jpg)
Webdev community
![Page 13: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/13.jpg)
Cooperation with other groups
![Page 14: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/14.jpg)
What could we do better?• “Welcome Wagon”
• 5-minute tasks
• More/better recognition (badges?)
• New contributor map
![Page 15: Engaging developers in Mozilla docs](https://reader036.fdocuments.net/reader036/viewer/2022062405/55515026b4c905bd1c8b5681/html5/thumbnails/15.jpg)
Take Away
•View your mission as bigger than software.
•Ask for help and reviews in small chunks.
•Talk to developers and contributors through their preferred channels.
• Look for alliances based on your (broad) mission.