Hi
user
Admin Login:
Username:
Password:
Name:
Quantitative community management
--client
lca
--show
lca2013
--room MCC5 1671 --force
Next: 1 Scratching your own itch - subsurface diving log
show more...
Marks
Author(s):
Asheesh Laroia
Location
MCC5
Date
feb Fri 01
Days Raw Files
Start
13:20
First Raw Start
error-in-template
Duration
0:45:00
Offset
None
End
14:05
Last Raw End
Chapters
Total cuts_time
None min.
http://lca2013.linux.org.au/schedule/30306/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Quantitative_community_management.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
In recent years, communities as wide-ranging as Wikihow to Thunderbird have been surveying participants and using this information to improve the experiences of participants. A variety of open source projects are now tracking contributors to identify where people fall away, and to nudge them forward. In this talk, you will learn the state of the art in community measurement, common mistakes made in surveying, and how to actively use data to improve activity within a project. This talk will cover the following issues in detail: * How Wikipedia used A/B testing to improve contribution rejection messages * Based on entrance/exit surveys from OpenHatch's Open Source Comes to Campus program, what do new contributors know? * The impact of treating gender as a plain-text field, rather than a drop-down, on the answer rate * How Ubuntu's Developer Advisory Team tracks, contacts, and nudges new contributors * How motivations for Thunderbird contributors differ substantially from the FLOSSpols survey * How to misread your survey data (and tips on avoiding that) Upon leaving this talk, you will have a solid background in the current state of data collection within open source communities and how to apply those tools to your own project.
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