Puppet: State of the Community 2012

488
-1

Published on

"State of the Community" from PuppetConf 2012 by James Turnbull, VP of Technical Operations at Puppet Labs

Watch the video here: http://youtu.be/0_u_5RkVymE

Abstract: In this presentation, I'll be presenting on what's happened in the Puppet community for the last year. We'll discuss the victories, failures and lessons from the past, and ideas for the future. In addition, if we've hired a community manager by this time, I'd like to this presentation jointly. This will focus on state of the union, how to get started in the community, and how to contribute to docs and dev

Speaker Bio: James is an author and open source geek. James authored the two books about Puppet (Pro Puppet and the earlier book about Puppet. He is also the author of three other books including Pro Linux System Administration, Pro Nagios 2.0, and Hardening Linux. For a real job, James is VP of Tech Ops for Puppet Labs. He likes food, wine, books, photography and cats. He is not overly keen on long walks on the beach and holding hands.

Learn more about Puppet: http://bit.ly/QQoAP1

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
488
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Numbers from the puppet code base by looking at commits from each year. Does not include merge commits
  • Numbers from the puppet codebase by using the %aN format of author names. There may be some double counting of individuals.
  • Providers counts from looking at number or ruby files that match the location of providers. 2005 data is estimated since providers didn't exist at that time. SLOC counted by sloccount across the entire repo (lib and test dirs)
  • Puppet: State of the Community 2012

    1. 1. State of the Community James Turnbull, Dawn Foster, Andy Parker | Puppet Labs james@puppetlabs.com dawn@puppetlabs.com andy@puppetlabs.com
    2. 2. Me • Wrote some stuff • VP Technical Ops at Puppet Labs • Funny accent • Film fan# puppetconf # puppetize @ puppetlabs
    3. 3. Favorite film? # puppetconf # puppetize @ puppetlabs
    4. 4. Awwww!# puppetconf # puppetize @ puppetlabs
    5. 5. Agenda • Introductions • The state of the community • Initiatives • Ask not what your community can do for you • Questions# puppetconf # puppetize @ puppetlabs
    6. 6. Introductions New faces
    7. 7. Introductions # puppetconf # puppetize @ puppetlabs
    8. 8. Dawn Foster • 2 day at Puppet Labs as Community Manager nd • Previous Open Source Community Manager: Tizen, MeeGo, Openfire, others • Early Career: Sys Admin, Programmer, Market Researcher, Program Manager • Education: BS in Computer Science, MBA • Getting Started (1st month): Lurking, learning and working on published community metrics • Info: dawn@puppetlabs.com, @geekygirldawn, DawnFoster (IRC), fastwonderblog.com # puppetconf # puppetize @ puppetlabs
    9. 9. Andy Parker • Puppet Team Lead • Software Developer • One time (long ago) cfengine user • Cyclist • New to open source development • Come talk to me! • Info: andy@puppetlabs.com, zaphod42 (IRC) # puppetconf # puppetize @ puppetlabs
    10. 10. Eric Sorenson • Puppet Platform Product Owner • SysAdmin at a large Cupertino fruit company • Mad keen cyclist • Go talk to him! • Info: eric.sorenson@puppetlabs.com, eric0 (IRC) # puppetconf # puppetize @ puppetlabs
    11. 11. Show me the metrics!Lies, damn lies, and statistics
    12. 12. The year that was… • Puppet user mailing list membership was 3000 • With about 600 messages a month • The #puppet IRC channel averaged 400 people • Puppet on GitHub had 200 forks and 400 watchers • We had 50 modules on the Forge # puppetconf # puppetize @ puppetlabs
    13. 13. The year that is… • Puppet users mailing list membership is almost 5000 • With 1200 messages a month • The #puppet IRC channel averages 800 people • Puppet on GitHub has 350 forks and 950 watchers • We have over 500 modules on the Forge # puppetconf # puppetize @ puppetlabs
    14. 14. Inconceivable!# puppetconf # puppetize @ puppetlabs
    15. 15. You keep using that word. I do not think it means what you think it means.# puppetconf # puppetize @ puppetlabs
    16. 16. But what about the Rodents of Unu^H^H Errr…. Development?# puppetconf # puppetize @ puppetlabs
    17. 17. How much is going on? 2464 2447 Commits 1265 1254 1205 1123 9304752005 2006 2007 2008 2009 2010 2011 2012 # puppetconf # puppetize @ puppetlabs
    18. 18. But who is doing all this? 187 99 158 80 Contributors Commits/Contributor 50 41 63 34 37 19 30 22 25 24 632005 2006 2007 2008 2009 2010 2011 2012 # puppetconf # puppetize @ puppetlabs
    19. 19. What does it all add up to? 141,126 137,743 116 108 108,636 103,118 86 82 89,304 77 76,891 SLOC # Providers 58 50,497 4221,635 12 2005 2006 2007 2008 2009 2010 2011 2012 # puppetconf # puppetize @ puppetlabs
    20. 20. So what’s next?For the Puppet community
    21. 21. Initiatives • Questions and Answers • More responsive • More metrics • More awesome # puppetconf # puppetize @ puppetlabs
    22. 22. Q&A site • Not everyone likes mailing lists • Leverage success of sites like Stackoverflow # puppetconf # puppetize @ puppetlabs
    23. 23. More responsive • We suck sometimes • We’re getting better • Really. # puppetconf # puppetize @ puppetlabs
    24. 24. More responsive Call us out if we’re not! # puppetconf # puppetize @ puppetlabs
    25. 25. More metrics • It’s cool to understand how many of you there are • It’s even cooler to try to understand who you are • We’d like to actually know what you want! • We want to be transparent and accountable # puppetconf # puppetize @ puppetlabs
    26. 26. More awesome • Talk to us • Complain to us • Give us feedback we can action • Help us out! # puppetconf # puppetize @ puppetlabs
    27. 27. Ask not what your communitycan do for you but what you can do for your community
    28. 28. The Puppet Community We want you!# puppetconf # puppetize @ puppetlabs
    29. 29. We need your help! • Documentation • Facter • Code & Tests (and Testing) • Modules! # puppetconf # puppetize @ puppetlabs
    30. 30. Documentation • Docs site: http://docs.puppetlabs.com • GitHub: https://github.com/puppetlabs/puppet- docs • Redmine: http://projects.puppetlabs.com/projects/puppet- docs • Open a ticket! Or better fix a ticket! • Send us a pull request • Profit! # puppetconf # puppetize @ puppetlabs
    31. 31. Facter • Have a platform Facter doesn’t know about? • Have a resource or infrastructure component you’d like exposed? • Test coverage == teh awesome • GitHub: https://github.com/puppetlabs/facter • Redmine: http://projects.puppetlabs.com/projects/facter # puppetconf # puppetize @ puppetlabs
    32. 32. Modules • Share and publish your modules • Fork and develop modules • Module bounties! • Module A, B, and C • Forge: http://forge.puppetlabs.com/ # puppetconf # puppetize @ puppetlabs
    33. 33. Code & Testing • Triage Puppet bugs and features • Write code • Write tests • Test releases! # puppetconf # puppetize @ puppetlabs
    34. 34. I can do that? # puppetconf # puppetize @ puppetlabs
    35. 35. Yes you bloody well can # puppetconf # puppetize @ puppetlabs
    36. 36. Get some tips • Getting Started with Contributing to Puppet and Facter • Hailee, Tesca and Ruth • Meeting Room 1 at 1.15pm # puppetconf # puppetize @ puppetlabs
    37. 37. Questions
    38. 38. Oh and BTW…. • PuppetCamp Nuremberg • October 19th, 2012 • http://www.netways.de/puppetcamp# puppetconf # puppetize @ puppetlabs
    39. 39. Thank you! © All images copyright Princess Bride Ltd.

    ×