Hi
user
Admin Login:
Username:
Password:
Name:
The technical challenges of serving docs at Google’s scale
--client
eric
--show
write_the_docs_2013
--room room_1 2289 --force
Next: 6 Helping the help pages
show more...
Marks
Author(s):
Ashleigh Rentz
Location
Room 1
Date
apr Tue 09
Days Raw Files
Start
14:30
First Raw Start
14:28
Duration
00:40:00
Offset
0:01:47
End
15:10
Last Raw End
15:10
Chapters
00:00
0:38:19
Total cuts_time
38 min.
http://lanyrd.com/2013/writethedocs/scfpdz/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
archive
public
mp4
svg
png
assets
release.pdf
The_technical_challenges_of_serving_docs_at_Googles_scale.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
Google Code launched in 2005, hosting documentation for Google’s public APIs and Open Source software. Five years later, massive growth in the company’s developer offerings had pushed the site’s infrastructure to the max. What sorts of problems can sneak up when you go from 11 APIs to over a hundred? Or when many of those docs rapidly expand from hundreds to thousands of pages? And how can you build a serving infrastructure that won’t leave a room of execs holding their collective breath when new products launch at your annual showpiece conference? Join Google Developer Programs’ Ashleigh Rentz for a behind-the-scenes retrospective: learn what it took to migrate a massive documentation library to a new home at Google Developers (developers.google.com) without freezing the existing site and how the new backend leverages both Open Source and Google technology to provide a CMS that truly scales.
Comment:
production notes
2013-04-09/14_28_13.dv
Apply:
14:28:13 - 14:30:16 ( 00:02:03 )
S:
14:28:13 -
E:
14:30:16
D:
00:02:03
show more...
vlc ~/Videos/veyepar/eric/write_the_docs_2013/dv/room_1/2013-04-09/14_28_13.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:28:13
seconds: 0.0
Wall: 14:28:13
Duration
00:02:03
14:30:16
seconds: 0.0
Wall: 14:28:13
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2013-04-09/14_30_16.dv
Apply:
14:30:16 - 15:08:35 ( 00:38:19 )
S:
14:30:16 -
E:
15:08:35
D:
00:38:19
show more...
vlc ~/Videos/veyepar/eric/write_the_docs_2013/dv/room_1/2013-04-09/14_30_16.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:30:16
seconds: 0.0
Wall: 14:30:16
Duration
00:38:19
15:08:35
seconds: 0.0
Wall: 14:30:16
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2013-04-09/15_08_36.dv
Apply:
15:08:36 - 15:09:09 ( 00:00:33 )
S:
15:08:36 -
E:
15:09:09
D:
00:00:33
show more...
vlc ~/Videos/veyepar/eric/write_the_docs_2013/dv/room_1/2013-04-09/15_08_36.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
15:08:36
seconds: 0.0
Wall: 15:08:36
Duration
00:00:33
15:09:09
seconds: 0.0
Wall: 15:08:36
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2013-04-09/15_09_09.dv
Apply:
15:09:09 - 15:10:42 ( 00:01:33 )
S:
15:09:09 -
E:
15:10:42
D:
00:01:33
show more...
vlc ~/Videos/veyepar/eric/write_the_docs_2013/dv/room_1/2013-04-09/15_09_09.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
15:09:09
seconds: 0.0
Wall: 15:09:09
Duration
00:01:33
15:10:42
seconds: 0.0
Wall: 15:09:09
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2013-04-09/14_28_13.dv
2013-04-09/14_30_16.dv
2013-04-09/15_08_36.dv
2013-04-09/15_09_09.dv
Veyepar
Video Eyeball Processor and Review
