This is a list of the different roles within the community and who is helping out in those roles. If you are interested in officially helping with any of them, please contact the person listed as the community manager.
Community Puppetmaster
| Responsibilities: | |
|---|---|
| Making sure the needs of the community as a whole are being met, including being the fall back for all other roles. | |
| Delegate: | Luke Kanies |
Release & Ticket Management
Puppet's Trac ticket database is the primary vehicle to engagement with the Puppet community. All bugs and enhancements need to go through it, so efficiently managing the tickets is critical to Puppet's continued development and stability.
After triage and assignments tickets are assigned to release milestones. Release management and milestone planning are then used to ensure tickets are appropriately prioritized and assigned to a suitable release.
Puppeteers
| Responsibilities: | |
|---|---|
| There are a variety of activities associated with release and ticket management: | |
- Assessment and triage of tickets
- Some bug fixes
- General ticket management
- Milestone detail management
- Release management
Responsibility for final veto on the contents of a release and development of the milestone roadmap rests with Luke Kanies.
| Delegates: | Luke Kanies, James Turnbull |
|---|---|
| List: | Puppet-tickets |
Documentation
Puppet's documentation is critical to everyone in the community, from prospective users trying to decide whether Puppet is appropriate for them, to new users looking for help getting started, to veterans needing reference information, all the way to developers needing to communicate about new features and bugs.
Puppetmaster
| Responsibilities: | |
|---|---|
| The big picture of the documentation, with a focus more on flow, organization, and coverage than details. Also maintains the Documentation Standards. | |
| Delagate: | Luke Kanies |
Puppeteers
| Responsibilities: | |
|---|---|
| Keeping all of the documentation as high quality as possible. This includes monitoring community changes to the documentation and modifying them if necessary to keep them within accepted guidelines. Also works with the documentation manager to set documentation guidelines. | |
| Delegates: | Digant C Kasundra, Juri Rischel Jensen, Jeff McCune |
| List: | Puppet-docs |
Community Support
Puppet's community is growing quickly and it has a wide range of experience and talent. As a result, there is a constant flurry of questions in email and on IRC, and getting these questions answered quickly and correctly is an important part of keeping the community together.
Puppet's user mailing list is a critical forum for communication, and to keep it useful and current we need people answering questions and converting threads into documentation.
Documenters
| Responsibilities: | |
|---|---|
| Make sure information provided in answers on the mailing lists is converted to appropriately categorized documentation. This could mean either writing new documentation or making existing documentation easier to find. | |
| Delegates: | Luke Kanies |
IRC
Day or night you can find a lot of people on #puppet on freenode.net talking about Puppet. Because it's a very low-commitment way to find out about Puppet, new users often pop in, ask a few questions, then leave, especially when they're having simple problems getting started. The better we answer these questions, and then document the answers, the faster people can get up and running with Puppet and become contributing community members themselves.
You can find further information about the IRC channel at IrcChannel
Documenters
| Responsibilities: | |
|---|---|
| Make sure information provided in answers on IRC is converted to appropriately categorized documentation. As with email, could mean either writing new documentation or making existing documentation easier to find. | |
| Delegates: | Luke Kanies, James Turnbull |
Platforms
One of Puppet's primary functions is to provide cross-platform support. Platforms vary widely, both in implementation and style, so each platform supported by Puppet has an associated platform advocate, responsible for the stability and function of Puppet on that platform. Every platform listed in the Stable Platforms page should have an advocate listed here.
If you have questions or recommendations about Puppet on a specific platform, please do not hesitate to contact the advocate for the platform in question.
- Red Hat (both Fedora and RHEL): David Lutterkort
- Gentoo: José González Gómez
- Debian: Thom May
- Mac OS X: Jeff McCune
- SuSE: Martin Vuk
- Solaris Gary Law
- OpenBSD: None
- AIX: None
- CentOS: None
| List: | Puppet-platforms |
|---|
Development
The developers are the people who translate community needs into a functional product, either through development from scratch or by accepting patches from other members of the community. There's a reason why development is mentioned last, though; while it's a critical part of the community, it is the community itself that matters, not the developers or the development. A great community can overcome a shoddy product, but a great product can't fix a dysfunctional community.
Puppetmaster
| Responsibilities: | |
|---|---|
| Vetting of all patches to the core code and deciding which features and bug fixes make it into which release. Also responsible for the overall roadmap and feature list. | |
| Delegate: | Luke Kanies |
Puppeteers
| Responsibilities: | |
|---|---|
| Applying accepted patches, writing missing test code, verifying filed bugs, and just about anything else related to development. | |
| Delegates: | Luke Kanies, David Lutterkort |
