TOSW Done wrong presentation
by Werner Gold
on the latest EMEA Red Hat Partner Summit, I delivered a presentation
jointly with Joel Berman about:
"TOSW Done Wrong".
On our server for the partner summit, the Sozi enhanced SVG file and the
audio track are available.
SVG is available to everybody after registration and MP3 to partners and
A public FLV and OGV is here:
If you want that presentation, I can share all files elsewhere as well.
Last year I did another presentation about "Communities Beyond Open Source".
A public flash version is here:
This year I delivered an updated version of this presentation to the
sales and marketing leadership team at ABB. It was very well received
and kicked of some fundamental thought processes within the management
of this industrial company.
More content like this has been delivered by Matthias Stürmer from E&Y.
On this year's EMEA partner summit he talked about:
"Doing the Impossible: Managing Open Source Communities"
ODP, PDF and MP3 are at:
I can ask him or E&Y to give us permission for screencast creation and
Werner Gold wgold(a)redhat.com
Partner Enablement / EMEA phone: 49.9331.803 855
Steinbachweg 23 fax: +49.9331.4407
97252 Frickenhausen/Main, Germany cell: +49.172.764 4633
Key fingerprint = FF91B07C 6F3D340E A71791AC 5E3A6CB4 D44CBC37
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei Muenchen
Handelsregister: Amtsgericht Muenchen HRB 153243
Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham,
11 years, 7 months
Quick words of advice for smaller projects
by Mel Chua
While our community team was doing our annual retreat this year, we
spent 40 minutes looking at a variety of open source projects to see
what sort of patterns we could find; here are a few things we noticed
and some recommendations we made based on those very shallow looks. Not
sure where best to place them in the book, but Karsten said to send them
to this list. :)
* Small projects need to stick with one, canonical conversation
location when they start, and grow in response to capacity instead of in
anticipation of it (think of speccing out office space & departments
for a startup of 5 people).
** Don't increase mailing lists by rote.
** Splitting in to many different tools (Redmine, Fedora Hosted, github,
etc.) means the conversation and community is split. "Engineering word
of mouth about how to start up a project."
** Use one location (mailing list)
* These details do matter, even if you think they don't. :) Think about
how businesses must grow and change with size and age through various
distinct phases -- not all open source projects can run the same way.
* TTM pressure on the developers?
** May make conversations go quiet.
* Picking the best tool for each task instead of reinventing
11 years, 8 months