Hi
user
Admin Login:
Username:
Password:
Name:
The Joys of Being A Maintainer
--client
dot_net_fringe
--show
dot_net_fringe_2015
--room mezzanine 9654 --force
Next: 1 Relax and let the HTTP Machine do the Work
show more...
Marks
Author(s):
Brendan Forster
Location
Mezzanine
Date
apr Tue 14
Days Raw Files
Start
11:15
First Raw Start
error-in-template
Duration
00:30:00
Offset
None
End
11:45
Last Raw End
Chapters
Total cuts_time
None min.
http://lanyrd.com/2015/dotnetfringe/sdkwdz/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
The_Joys_of_Being_A_Maintainer.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:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
"If you've never open sourced your code, you're probably missing out on the joys of collaborating with other developers. From answering support questions to reviewing code and even submitting patches for bugfixes or new features, there's many ways for others to help improve and enhance the work you've started. So what actually happens after you've published some code you're really proud of? What can you do to make it easier for others to collaborate on your code? And what traps should you watch for as you start down this path? In this talk, Brendan, Justin and Keith will discuss some of the common situations that come up after opening up a project to contributions, and talk about lessons learned along the way.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review