Author(s):	Asheesh Laroia
Location	Heidelberg
Date	aug Thu 20	Days Raw Files
Start	14:00	First Raw Start	error-in-template
Duration	00:20:00	Offset	None
End	14:20	Last Raw End
Chapters
Total cuts_time	None min.

https://summit.debconf.org/debconf15/meeting/311/sandstormio-a-web-native-package-manager-with-many-lessons-from-debian/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

assets release.pdf Sandstormio_A_webnative_package_manager_with_many_lessons_from_Debian.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:	This talk introduces Sandstorm, a free software package manager for web applications with a focus on usability and security. The talk dives deep into how Sandstorm works and why. You'll see how Sandstorm is similar to and different from Debian, and you'll learn: * Why Sandstorm exists, and why I think it fits the web better than packaging the same apps in Debian directly * How people turn open source web apps into Sandstorm packages * How (and why) every Sandstorm app package is a Debian derivative * Why Debian should use this for Debian Developer-oriented infrastructure * Examples of web apps that Sandstorm is, and isn't, good for * How our community structure is different from Debian's -- with many lessons I've personally learned through my work on Debian * How Sandstorm adds security and access control to any web app You'll leave with a sense of the purpose of Sandstorm, an understanding of why we made it, and a desire to run it yourself. markdown
Comment:	production notes