veyepar: Herding Cats: Getting an open source community to work on the same thing

Author(s):	John Dickinson
Location	OGGB3
Date	jan Thu 15	Days Raw Files
Start	14:15	First Raw Start	14:04
Duration	0:45:00	Offset	0:10:23
End	15:00	Last Raw End	15:09
Chapters	00:00 0:47:17
Total cuts_time	50 min.

http://lca2015.linux.org.au/schedule/30167/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Herding_Cats_Getting_an_open_source_community_to_work_on_the_same_thing.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

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

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Have you ever wondered how to get a big new feature completed in an open-source project? Getting people in the same company to work together can be a daunting task. Getting people to work together for a common goal when their employers actually compete with one another is quite a bit harder. Despite the challenges, the OpenStack Swift community came together to create the biggest new feature the project has ever seen.

Between June of 2013 and June of 2014, the OpenStack Swift community designed, built, and delivered storage policies, a major new feature that enables a ton of new use cases for users. This talk will briefly cover the feature implemented, but we'll mostly talk about how contributors from different companies came together and the lessons learned from that experience.

If you contribute an open source project, you'll want to hear what we did right, what we did wrong, tools we invented, tools we threw out, and how you can take these lessons we learned to your own project. We'll cover development work, review work, how we did communication, how we tracked tasks, and what we learned through it all.

Comment:

production notes