Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Own it: working with a changing open source community
1. Own it
Working with a changing
open source community
Selena Deckelmann
PostgreSQL Global Development Group
2. “[C]ommunities are composed of individuals
who collaborate toward a common goal but
do not share a common employer
and are not governed by an
employment hierarchy.”
The Role of Participation Architecture in Growing
Sponsored Open Source Communities
Joel West and Siobhán O’Mahony
4. • MySQL
• Percona Server
• MariaDB
• MySQLAtFacebook
• Google patchset
• Drizzle
5. • MySQL - Core
• Percona Server - Branch
• MariaDB - Branch (more Forky now)
• MySQLAtFacebook - Branch
• Google patchset - Branch
• Drizzle - Fork
6. User
Deployer-Developer
Extending
Co-Developer
Co-Developer
Free Software
Commons
From http://webmink.com/essays/community-types/
7. User
{
What we
had with Deployer-Developer
MySQL Extending
Community Co-Developer
Co-Developer
Free Software
Commons
From http://webmink.com/essays/community-types/
8. User
Deployer-Developer
Extending
Co-Developer
{
Co-Developer
What forks
enable now Free Software
Commons
From http://webmink.com/essays/community-types/
9. Where we
are growing
the fastest
{ User
Deployer-Developer
}
Extending
Co-Developer Postgres
Co-Developer has always
focused here
Free Software
Commons
From http://webmink.com/essays/community-types/
10. “However, the category of
traditional encyclopedias and
reference material has changed.
People today seek and consume
information in considerably
different ways than the past.”
http://mashable.com/2009/03/30/microsoft-encarta-to-close/
12. “Companies or foundations that run open source
project are not software firms, they are community
management firms whose communities happen to make
software. Consequently to survive and thrive these
projects need to invest less in enhancing governance
structures or employees who will improve their
capacity to code.
“Instead, we should consider skills and structures that
emphasize facilitation, mediation, and conflict
management – tools, skills and structures that will
enable the community to better collaborate.”
http://eaves.ca/2006/12/17/community-management-as-open-sources-core-competency/
26. Huge patches suck
• Unknown contributors: too much at stake
to support
• Trusted contributors: too much to review,
digest and spend time on while other work
goes on in parallel OR is stopped to deal
with the huge patch
• It sucks for the developer (and company)
to be rejected after all that work
28. • "Get someone from the community involved in
your ideas as early as possible so that you can
even get half-baked ideas vetted early, rather than
creating something in a vacuum.”
• “[C]oncentrate on the smallest portion of the
idea you can execute perfectly.”
• “Resist the temptation to build a giant patch all at
once, as those are much less likely to be reviewed
usefully and therefore committed."
http://wiki.postgresql.org/wiki/Submitting_a_Patch
![“[C]ommunities are composed of individuals
who collaborate toward a common goal but
do not share a common employer
and are not governed by an
employment hierarchy.”
The Role of Participation Architecture in Growing
Sponsored Open Source Communities
Joel West and Siobhán O’Mahony](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)