Hi
user
Admin Login:
Username:
Password:
Name:
Fun with .buildinfo
--client
debian
--show
debconf17
--room buzz 12450 --force
Next: 1 in-toto -- Securing supply chains as a whole
show more...
Marks
Author(s):
Steven Chamberlain
Location
Buzz
Date
aug Thu 10
Days Raw Files
Start
10:00
First Raw Start
error-in-template
Duration
00:20:00
Offset
None
End
10:20
Last Raw End
Chapters
Total cuts_time
None min.
https://debconf17.debconf.org/talks/91/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Fun_with_buildinfo.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
Beyond the obvious use-case of .buildinfo files for reproducible builds, I will present some other ideas of how to use them. There will be new opportunities for automated QA, for tracing software origin, and securing package distribution.
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