June 2014 PDX PUG: Ways to Plug Into the Puppet Community by Eric Sorenson, Puppet Labs

1. This page is intentionally
left blank

2. Contributing
The dos and don’ts of

3. con·tri·bu·tion
noun: contribution
plural noun: contributions
!
!
1. the part played by a person or thing in bringing about
a result or helping something to advance.
2. an article or other piece of writing submitted for
publication in a collection.
!
!
from late Latin contributio(n-),
from Latin contribuere ‘bring together, add’

4. But notice that this is
not very prescriptive:
!
nothing about having to write code,
or what degree you have, or where
you’re from, or what you look like

5. If you can move things
forward,we’d love for
you to get involved!

6. users
authors
devs

7. Bug reports
Documentation fixes
Testing
Mailing list/Ask help
Community building
Comment on proposals
Code!

8. On bugs

9. Search for duplicates
File a good bug
Metadata
Updating your bug

10. This works for both
old and new bugs!
!
adding info to existing
tickets helps a ton!

12. Feature requests
help too,especially
with use cases.
!
focus on the problem

13. On documentation

14. Docs are hugely
important; thousands
of people look at them
every day!
!
how many of you have used
Google as a debugger?

15. https://github.com/puppetlabs/puppet-docs

16. https://github.com/puppetlabs/puppetdb

17. Perfection is not
required; content is
king!
!
don’t need perfect grammar or
speling; focus on building
new and updated content

18. On testing

19. Software is only as
good as the people
that test it

20. Test new builds,
release candidates,
experimental features
!
and try out fixes for
bugs you’re following!

21. On performance

22. How many people
think puppet is as fast
as it can be?

23. Profile our stuff!
Send us results!
Tell us what’s slow,
and when we regress!

24. Need
more
input!

25. On community

27. On code

28. "This is the Puppet
community.There are
many like it,but this
one is ours."

29. Core platform
FactsProviders Modules Layered tools

30. Patches

31. The CLA

32. What happens after
you file a pull request?

35. PR triage
Announce on
mailing list
Start hangout Pick a PR
Discuss Merge!
Close
Submitter
follow-up
Committer
follow-up
Needs more
discussion

36. http://resresres.deviantart.com/art/

37. Show up to the triage,
Respond to comments,
Be your own advocate

38. There are many
reasons why a pull
request may not get
merged

39. Basic form,
Quality,
Correctness,
Verification,
Consensus

40. However!

42. Incorrect code helps!
Incomplete code
helps!
!
you are not your code, and
discussing ideas as a group can be
highly valuable

43. Anti-patterns

45. Being impatient won’t
get your bugs fixed
more quickly.

46. Being hostile or overly
confrontational does
not help.

47. Wanting to be right at
all costs is "scorched
earth"collaboration.

48. Claiming to represent
all puppet users is
wishful thinking.

49. Expecting other
community members
to do work for you is
unlikely to work.

50. Food for thought

51. We’re looking for more
maintainers!

52. How can we improve
ticket triage?

53. How can we get better
diagnostic information
from users when they
encounter bugs?

54. How can we help new
contributors find
things to work on?

55. We’re all in this together,
people!

56. deepak
giridharagopal
eric
sorenson
original talk by