veyepar: Strategies to Fight Documentation Inertia

Author(s):	Britta Gustafson
Location	Crystal Ballroom
Date	may Tue 06	Days Raw Files
Start	12:00	First Raw Start	11:46
Duration	00:20:00	Offset	0:13:38
End	12:20	Last Raw End	12:33
Chapters	00:00
Total cuts_time	21 min.

http://conf.writethedocs.org/49
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Strategies_to_fight_documentation_inertia.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:	I'm a non-developer working with a community including a bunch of mostly-volunteer developers, and for years our developer documentation wiki was quiet and mostly static. I didn't touch it, since I don't know enough to work on developer resources, right? Wait, no! I realized that even if I can't update it all myself, I can help the developers with it, including a bit of persuading them. I'll explain some of my strategies for making working on documentation more appealing and rewarding for developers, including by lending it some aspects of the quick feedback that people get when writing code. This includes things like: Ways to make the wiki feel active and alive, since nobody likes to hang out in a ghost town. Good questions to ask that encourage people to write things down. How to make first edits easy with bite-sized tasks and prominent "todos" that entice people to click that edit button. Finding people who prefer to ask permission first before making changes, and being there to give them permission! And the best "trick": advice for effective ways to thank people a lot, publicly and specifically. markdown
Comment:	production notes