Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Own itWorking with a changingopen source community          Selena Deckelmann PostgreSQL Global Development Group
“[C]ommunities are composed of individualswho collaborate toward a common goal butdo not share a common employerand are no...
Forks open doors.
• MySQL• Percona Server• MariaDB• MySQLAtFacebook• Google patchset• Drizzle
• MySQL - Core• Percona Server - Branch and Redist• MariaDB - Branch and Redist• MySQLAtFacebook - Branch• Google patchset...
UserDeployer-Developer   Extending  Co-Developer  Co-Developer  Free Software    Commons From http://webmink.com/essays/co...
User        { What we had with   Deployer-Developer MySQL         ExtendingCommunity     Co-Developer              Co-Deve...
User             Deployer-Developer                Extending               Co-Developer         {               Co-Develop...
Where weare growing the fastest               {         User               Deployer-Developer                             ...
“However, the category of traditional encyclopedias andreference material has changed.People today seek and consume  infor...
Ingredients• Revision control• Peer review• Public discussion
“Companies or foundations that run open source   project are not software firms, they are community   management firms whose...
“owning” code            ==first class project citizen
How does that affect   businesses?
Open door #1Make friends
Trust and reputation
People are not companies.
Developers must haverelationships and represent       your company.
Community is thatfriend that helps you        move.
Core developers are     catalysts.
Open Door #2  Chunk it
(“it” == contributions)
The Pottery Barn Rule
Huge patches suck• Unknown contributors: too much at stake  to support• Trusted contributors: too much to review,  digest ...
You will have to change     your code.
•    "Get someone from the community involved in     your ideas as early as possible so that you can     even get half-bak...
Get out ofyour oval office.
Open Door #3Take responsible action
Do-ocracy
People are already  doing things.
Contribute what the community needs.
Commitfest tool
Peace Corp Model
Things you can do now• User Groups• Answer questions• Fund travel• Sponsor conferences• Comment on blog posts
What Business Can Do      Make Friends.        Chunk it.Take responsible action.
Thanks.@selenamarieselena@chesnok.comhttp://chesnok.com
Own it: working with a changing open source community
Own it: working with a changing open source community
Upcoming SlideShare
Loading in …5
×

Own it: working with a changing open source community

1,250 views

Published on

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

Own it: working with a changing open source community

  1. 1. Own itWorking with a changingopen source community Selena Deckelmann PostgreSQL Global Development Group
  2. 2. “[C]ommunities are composed of individualswho collaborate toward a common goal butdo not share a common employerand are not governed by anemployment hierarchy.” The Role of Participation Architecture in Growing Sponsored Open Source Communities Joel West and Siobhán O’Mahony
  3. 3. Forks open doors.
  4. 4. • MySQL• Percona Server• MariaDB• MySQLAtFacebook• Google patchset• Drizzle
  5. 5. • MySQL - Core• Percona Server - Branch and Redist• MariaDB - Branch and Redist• MySQLAtFacebook - Branch• Google patchset - Branch• Drizzle - Fork
  6. 6. UserDeployer-Developer Extending Co-Developer Co-Developer Free Software Commons From http://webmink.com/essays/community-types/
  7. 7. User { What we had with Deployer-Developer MySQL ExtendingCommunity Co-Developer Co-Developer Free Software Commons From http://webmink.com/essays/community-types/
  8. 8. User Deployer-Developer Extending Co-Developer { Co-DeveloperWhat forksenable now Free Software Commons From http://webmink.com/essays/community-types/
  9. 9. Where weare 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. 10. “However, the category of traditional encyclopedias andreference 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/
  11. 11. Ingredients• Revision control• Peer review• Public discussion
  12. 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/
  13. 13. “owning” code ==first class project citizen
  14. 14. How does that affect businesses?
  15. 15. Open door #1Make friends
  16. 16. Trust and reputation
  17. 17. People are not companies.
  18. 18. Developers must haverelationships and represent your company.
  19. 19. Community is thatfriend that helps you move.
  20. 20. Core developers are catalysts.
  21. 21. Open Door #2 Chunk it
  22. 22. (“it” == contributions)
  23. 23. The Pottery Barn Rule
  24. 24. 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
  25. 25. You will have to change your code.
  26. 26. • "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
  27. 27. Get out ofyour oval office.
  28. 28. Open Door #3Take responsible action
  29. 29. Do-ocracy
  30. 30. People are already doing things.
  31. 31. Contribute what the community needs.
  32. 32. Commitfest tool
  33. 33. Peace Corp Model
  34. 34. Things you can do now• User Groups• Answer questions• Fund travel• Sponsor conferences• Comment on blog posts
  35. 35. What Business Can Do Make Friends. Chunk it.Take responsible action.
  36. 36. Thanks.@selenamarieselena@chesnok.comhttp://chesnok.com

×