Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Open-Source Maintainership and Community in 2016

7f7fe07c6402a15a4888c3ba00efca45?s=47 Eric Sorenson
November 15, 2016

Open-Source Maintainership and Community in 2016

Large open-source projects are changing the way they operate to reflect changes in maintainership and contribution patterns. Improvements in GitHub, test frameworks, and communication tools like chatops have made parts of OSS easier... and others way harder. In this talk, I'll walk through the evolution of our contribution and community processes on Puppet and its related projects over the last several years, to examine our successes -- and a few notable failures. I'll close with some ideas and suggestions, both to help maintainers improve the quality and quantity of their contributions, and to help both new and seasoned contributors have a great experience working on open-source projects.

7f7fe07c6402a15a4888c3ba00efca45?s=128

Eric Sorenson

November 15, 2016
Tweet

Transcript

  1. Open Source, Open Communities Maintainership and contribution in 2016 Eric

    Sorenson // @ahpook eric.sorenson@puppet.com
  2. Old models Forces for Change Adaptations What you can do

    next
  3. Ye olden days

  4. None
  5. None
  6. None
  7. None
  8. None
  9. Cathedral and Bazaar / ORA

  10. None
  11. None
  12. oh my zsh

  13. None
  14. None
  15. Recent Developments

  16. Recent Developments

  17. Recent Developments

  18. Recent Developments

  19. Recent Developments Registries and small modules

  20. Recent Developments

  21. Recent Developments meritocracy considered harmful

  22. Recent Developments meritocracy considered harmful

  23. Recent Developments

  24. None
  25. - look for a project that suits your temperament as

    well as your technical skills. - if you're going to embark on a big feature or refactor, spend a little time talking about it first! - work on PRs iteratively and don't be afraid to push up a bunch of commits and squash it later. - work with your organisation to get approval to contribute back
  26. - set up testing infrastructure so you can give commit

    bits - find or create a slack community - don't tolerate jerks. - have design discussions in the open - find some way to flag your issues as being newbie-friendly.
  27. Photo Credits Photos are by Eric Sorenson CC/SA/NC except where

    noted. PDP-11 - https://commons.wikimedia.org/wiki/File%3APdp-11-70-panel.jpg Collabocats - https://octodex.github.com/collabocats oh my zsh - https://medium.freecodecamp.com/d-oh-my-zsh-af99ca54212c#.g865cff22 disrupt band logo - http://billtmiller.com/kp/disrupt.gif bicycle evolution - worlds best bike stickers fryman / chatops - talk at rackspace https://www.youtube.com/watch?v=IhzxnY7FIvg meritocracy rug - collaboration rug - http://www.dailydot.com/debug/tech-industry-lesbians-who-tech/