Puppet

3

This is a list of the different roles within the community and who

4

1

is helping out in those roles. If you are interested in officially

5

1

helping with any of them, please contact the person listed as the

6

1

community manager.

7

1

8

1

# Community Puppetmaster

9

1

10

1

Responsibilities:

11

1

Making sure the needs of the community as a whole are being met,

12

1

including being the fall back for all other roles.

13

1

Delegate:

15

1

# Release & Ticket Management

16

1

18

1

with the Puppet community. All bugs and enhancements need to go

19

1

through it, so efficiently managing the tickets is critical to

20

1

Puppet's continued development and stability.

21

1

22

1

After triage and assignments tickets are assigned to release

23

1

milestones. Release management and milestone planning are then used

24

1

to ensure tickets are appropriately prioritized and assigned to a

25

1

suitable release.

26

1

27

1

## Puppeteers

28

1

29

1

Responsibilities:

30

1

There are a variety of activities associated with release and

31

1

ticket management:

32

1

1.  Assessment and triage of tickets

33

1

2.  Some bug fixes

34

1

3.  General ticket management

35

1

4.  Milestone detail management

36

1

5.  Release management

37

1

38

1

Responsibility for final veto on the contents of a release and

39

1

development of the milestone roadmap rests with

40

1

41

1

Delegates:

42

1

43

1

List:

45

1

# Documentation

46

1

47

1

Puppet's documentation is critical to everyone in the community,

48

1

from prospective users trying to decide whether Puppet is

49

1

appropriate for them, to new users looking for help getting

50

1

started, to veterans needing reference information, all the way to

51

1

developers needing to communicate about new features and bugs.

52

1

53

1

## Puppetmaster

54

1

55

1

Responsibilities:

56

1

The big picture of the documentation, with a focus more on flow,

57

1

organization, and coverage than details. Also maintains the

58

1

[[Documentation Standards]] .

59

1

Delagate:

60

1

62

1

## Puppeteers

63

1

64

1

Responsibilities:

65

1

Keeping all of the documentation as high quality as possible. This

66

1

includes monitoring community changes to the documentation and

67

1

modifying them if necessary to keep them within accepted

68

1

guidelines. Also works with the documentation manager to set

69

1

documentation guidelines.

70

1

Delegates:

71

1

72

1

List:

73

1

# Community Support

74

1

75

1

Puppet's community is growing quickly and it has a wide range of

76

1

experience and talent. As a result, there is a constant flurry of

77

1

questions in email and on IRC, and getting these questions answered

78

1

quickly and correctly is an important part of keeping the community

79

1

together.

80

1

81

1

## Email

82

1

84

1

current we need people answering questions and converting threads

85

1

into documentation.

86

1

87

1

### Documenters

88

1

89

1

Responsibilities:

90

1

Make sure information provided in answers on the mailing lists is

91

1

converted to appropriately categorized documentation. This could

92

1

mean either writing new documentation or making existing

93

1

documentation easier to find.

94

1

Delegates:

95

1

96

1

## IRC

97

1

98

1

Day or night you can find a lot of people on #puppet on

99

1

freenode.net talking about Puppet. Because it's a very

100

1

low-commitment way to find out about Puppet, new users often pop

101

1

in, ask a few questions, then leave, especially when they're having

102

1

simple problems getting started. The better we answer these

103

1

questions, and then document the answers, the faster people can get

104

1

up and running with Puppet and become contributing community

105

1

members themselves.

106

1

107

1

You can find further information about the IRC channel at [[Irc

108

1

Channel]]

109

1

110

1

### Documenters

111

1

112

1

Responsibilities:

113

1

Make sure information provided in answers on IRC is converted to

114

1

appropriately categorized documentation. As with email, could mean

115

1

either writing new documentation or making existing documentation

116

1

easier to find.

117

1

Delegates:

118

1

119

1

# Platforms

120

1

121

1

One of Puppet's primary functions is to provide cross-platform

122

1

support. Platforms vary widely, both in implementation and style,

123

1

so each platform supported by Puppet has an associated platform

124

1

advocate, responsible for the stability and function of Puppet on

125

1

that platform. Every platform listed in the [[Stable Platforms]]

126

1

page should have an advocate listed here.

127

1

128

1

If you have questions or recommendations about Puppet on a specific

129

1

platform, please do not hesitate to contact the advocate for the

130

1

platform in question.

131

1

132

1

-   **Red Hat** (both Fedora and RHEL):

133

1

-   **Gentoo**:

134

1

-   **Debian**: Thom May

135

1

-   **Mac OS X**:

136

1

-   **SuSE**:

137

1

-   **Solaris**

138

1

-   **OpenBSD**: None

139

1

-   **AIX**: None

140

1

-   **CentOS**: None

141

1

142

1

List:

143

1

[Puppet-platforms](https://mail.madstop.com/mailman/listinfo/puppet-platforms)

144

1

# Development

145

1

146

1

The developers are the people who translate community needs into a

147

1

functional product, either through development from scratch or by

148

1

accepting patches from other members of the community. There's a

149

1

reason why development is mentioned last, though; while it's a

150

1

critical part of the community, it is the community itself that

151

1

matters, not the developers or the development. A great community

152

1

can overcome a shoddy product, but a great product can't fix a

153

1

dysfunctional community.

154

1

155

1

## Puppetmaster

156

1

157

1

Responsibilities:

158

1

Vetting of all patches to the core code and deciding which features

159

1

and bug fixes make it into which release. Also responsible for the

160

1

overall roadmap and feature list.

161

1

Delegate:

162

1

163

1

## Puppeteers

164

1

165

1

Responsibilities:

166

1

Applying accepted patches, writing missing test code, verifying

167

1

filed bugs, and just about anything else related to development.

168

1

Delegates:

Community Roles