Author(s):	Rory Aronson
Location	blank
Date	jan Tue 22	Days Raw Files
Start	09:10	First Raw Start	error-in-template
Duration	0:50:0	Offset	None
End	10:00	Last Raw End
Chapters
Total cuts_time	None min.

https://2019.linux.conf.au/schedule/presentation/283/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Keynote_Beyond_READMEmd_C1_3.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:	We all understand the importance of the README.md file in open-source software. But what happens when you go beyond software and begin to document your hardware and your business model too? What could happen if you transformed your documentation from a file, to a product? In this talk, Rory Aronson tells the story of how FarmBot Inc is raising the bar of what it means to have great documentation, and why it is vital to his mission and vision. markdown
Comment:	production notes