veyepar: Entry points and guide posts: Helping new contributors find their way

Author(s):	Janet Swisher
Location	Crystal Ballroom
Date	may Tue 19	Days Raw Files
Start	10:10	First Raw Start	10:11
Duration	00:30:00	Offset	0:01:53
End	10:40	Last Raw End	10:37
Chapters	00:00
Total cuts_time	23 min.

http://lanyrd.com/2015/writethedocs/sdmwxh/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Entry_points_and_guide_posts_Helping_new_contributors_find_their_way.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

How did Mozilla Developer Network (MDN) achieve a 46% increase in active editors and a 90% increase in translation contributions in 2014? Many factors helped, but a major element was the support we added for new contributors.
“Scratch your own itch” is the proverbial invitation to contribute to open source projects. How well this works for contributing to code is open to debate, but it rarely makes sense for open source documentation, especially for well-established projects. Not only is it unhelpful for the project, which typically has plans (or at least wishlists) for improving the docs, but it provides very little guidance to the contributor as to what they might do, what they personally are able to do, and what would be most helpful to do.
In the 10 years that MDN has been a wiki (some of the content pre-dates the wiki), the community has always welcomed constructive contributions by anyone who bothers to create a user account. Over the years, we’ve created meta-documentation about contributing to the site, including wishlists of things we’d like to see documented. However, these didn’t necessarily help newcomers gain traction.
Only in the last year or so have we created documentation to help new contributors specifically. Our aim is to help newcomers find the right match among:
Topics and tasks the person is interested in (what they like)
Tasks the person has the skills and time to do (what they can do)
Tasks that help MDN meet the goals that Mozilla has set (what we need/want)
I’ll describe the features we’ve put in place to achieve this, as well as things we’re still working on. I’ll leave space for discussion so we can all share ideas and successes.

Comment:

production notes