veyepar: Listening to the Needs of Your Global Open Source Community

Author(s):	Elizabeth K. Joseph
Location	Tasman Hall A
Date	jan Tue 17	Days Raw Files
Start	17:40	First Raw Start	17:18
Duration	0:45:0	Offset	0:21:26
End	18:25	Last Raw End	18:48
Chapters	00:00 0:08:37
Total cuts_time	35 min.

http://linux.conf.au/schedule/presentation/103/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Listening_to_the_Needs_of_Your_Global_Open_Source_Community.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:	When open source projects are small it's easy to work directly with your contributors to make sure that you're serving their needs, but what happens when the project gets larger? It's really easy to assume nothing is wrong when contributors aren't communicating with the project leadership or infrastructure team about what they’re struggling with, but it's rarely the case that contributing is a smooth process. Drawing from experience in the Ubuntu and OpenStack communities, this talk will explore some of the ways large projects have worked to identify pain points for their contributors and then address them. Case studies include: * Institution of regular check-ins with core teams in the Ubuntu project. * Discussions with the OpenStack QA team about workarounds they were doing to scour job logs, and the subsequent implementation of the ELK (Elasticsearch, Logstash and Kabana) stack. * Work with the i18n team in OpenStack to provide a new translations platform. From these case studies and more we'll explore how to get into contact with contributors, reading between the lines in mailing list posts to learn where people are struggling and working to make your project a comfortable place where contributors know they can ask for assistance. markdown
Comment:	production notes