Hi
user
Admin Login:
Username:
Password:
Name:
Keeping up with the pace of a fast growing community without dying
--client
pyconza
--show
pyconza2016
--room congo_room 11459 --force
Next: 1 Running Django Applications on GAE - Flexible Environment(Previously Managed VMs)
show more...
Marks
Author(s):
Flavio Percoco
Location
Congo Room
Date
oct Thu 06
Days Raw Files
Start
09:30
First Raw Start
error-in-template
Duration
01:00:00
Offset
None
End
10:30
Last Raw End
Chapters
Total cuts_time
None min.
https://za.pycon.org/talks/34/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Keeping_up_with_the_pace_of_a_fast_growing_community_without_dying.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
New open source communities are born everyday. Some of them are meant to last long and some others aren't. There's a moment in every community where it needs to outgrow itself, expand its limits and aim way higher than ever. This is no necesarily related to its goals but the ecosystem it needs to stay alive. Once a community has gone beyond its limits, the community members, consumers and leaders will have to keep up with its pace. How do we help it to remain sane? How do we keep our goals on track while allowing for further growth? How do we allow it to keep expanding without further damaging the community? These are all questions we ask ourselves everyday in the OpenStack community and that we've managed to work on without killing ourselves on 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