Author(s):	Maciej Fijałkowski
Location	Congo Room
Date	oct Fri 07	Days Raw Files
Start	16:45	First Raw Start	error-in-template
Duration	01:00:00	Offset	None
End	17:45	Last Raw End
Chapters
Total cuts_time	None min.

https://za.pycon.org/talks/28/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	There has been a lot said about how to ensure correct quality control using tests, continuous integration, peer review etc. In this talk I would like to focus exclusively on my experience as an open source contributor with various projects. I've contributed extensively to projects I don't manage (like twisted, mercurial, cpython) and I've overseen contributions by others to projects like vmprof or PyPy. I would like to share my experience on how various methods (tests, reviews etc.) make me feel as a contributor and how easy it is to integrate changes based on that. I think the human factor of contributions is often too omitted from the process. markdown
Comment:	production notes