You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+39-11Lines changed: 39 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -18,14 +18,15 @@ Contributors. Contributors are individuals who have contributed code,
18
18
documentation, designs or other work to one or more Project repositories,
19
19
or who have done significant work to empower the Community,
20
20
moderating on [Discourse](http://docs.pymc.io),
21
-
organizing [PyMCon]() or helped on other platforms and events.
21
+
organizing [PyMCon](https://pymcon.com) or helped on other platforms and events.
22
22
Anyone can be a Contributor. Contributors can be affiliated with any legal
23
23
entity or none. Contributors participate in the project by submitting,
24
24
reviewing and discussing GitHub Pull Requests and Issues and participating in
25
-
open and public Project discussions on GitHub, Slack, Gitter chat rooms and mailing lists. The foundation of Project participation is openness
26
-
and transparency.
25
+
open and public Project discussions on GitHub, Slack, Gitter chat rooms and mailing lists.
26
+
The foundation of Project participation is openness and transparency.
27
27
28
-
There have been over 250 Contributors to the Project, their contributions are listed in the logs of the PyMC GitHub repositories as well as those of associated projects and venues.
28
+
There have been over 250 Contributors to the Project, their contributions are listed in the
29
+
logs of the PyMC GitHub repositories as well as those of associated projects and venues.
29
30
30
31
The Project Community consists of all Contributors and Users of the Project.
31
32
Contributors work on behalf of and are responsible to the larger Project
@@ -81,6 +82,8 @@ questions where dedicated teams will prevail.
81
82
The PyMC project currently counts with the Developer and Documentation teams.
82
83
Team members can be part of one, some or none of these dedicated teams.
83
84
85
+

86
+
84
87
Anyone working with The Project has the responsibility to personally uphold
85
88
the Code of Conduct. Core Contributors have the additional responsibility
86
89
of _enforcing_ the Code of Conduct to maintain a safe community.
@@ -160,6 +163,10 @@ if they are an institutional contributor/council member -->
160
163
- Adrian Seyboldt
161
164
- Thomas Wiecki
162
165
166
+
### Past Steering Council members
167
+
168
+
- Name (year-year)
169
+
163
170
### Council membership
164
171
165
172
To become eligible for being a Steering Council Member an individual must be a
@@ -187,12 +194,12 @@ Council members can renounce at any time and are
187
194
encouraged to do so if they foresee they won't be able to attend their
188
195
responsibilities for an extended interval of time.
189
196
190
-
If a Council member becomes inactive in the project for a period of one year,
197
+
If a Council member becomes inactive in the project for a period of six months,
191
198
they will be considered for removal from the Council. Before removal, inactive
192
199
Member will be approached by the BDFL to see if they plan on returning to
193
200
active participation. If not they will be removed immediately upon a Council
194
201
vote. If they plan on returning to active participation soon, they will be
195
-
given a grace period of half year. If they don’t return to active participation
202
+
given a grace period of six months. If they don’t return to active participation
196
203
within that time period they will be removed by vote of the Council without
197
204
further grace period. All former Council members can be considered for
198
205
membership again at any time in the future, like any other Core Contributor.
@@ -272,17 +279,23 @@ The current NumFOCUS Subcommittee consists of:
272
279
273
280
## Core Contributors
274
281
Core Contributors are those individuals with commit or managing rights to any of
275
-
the repositories or services of the PyMC Project. Therefore, some Core Contributors
276
-
may act as Recurring or Core Contributors depending on the work at hand.
282
+
the repositories or services of the PyMC Project. However, the exact permissions
283
+
of all Core Contributors may not be the same and depend on their team memberships.
284
+
Therefore, Core Contributors may act as Recurrent Contributors depending
285
+
on the task at hand.
277
286
We believe this to be necessary given the current size and scope of
278
287
the PyMC project. Contributors may be proficient in some areas of the
279
288
project while being inexperienced in some others.
280
289
281
290
### Core Contributor membership
282
291
To become a Core Contributor, one must already be a Recurring Contributor.
283
-
Core Contributors can nominate any Recurring Contributor to receive commit rights
284
-
and become a Core Contributor. For the nomination to go forward, it has to be
292
+
Core Contributors can nominate any Recurring Contributor to become a
293
+
Core Contributor. For the nomination to go forward, it has to be
285
294
ratified by the Steering Council and the BDFL.
295
+
For a nomination to be rejected, clear reasoning behind the decision must be
296
+
shared with the rest of the team. People whose nomination has been rejected can
297
+
be nominated at any time again in the future, three months after the previous
298
+
nomination at the earliest.
286
299
287
300
### Current Core Contributors
288
301
@@ -307,6 +320,10 @@ Recurring Contributors can nominate any Contributor to participate in the
307
320
Project private communication channels and become a Recurring Contributor.
308
321
For the nomination to go forward, it has to be ratified by
309
322
the Steering Council and the BDFL.
323
+
For a nomination to be rejected, clear reasoning behind the decision must be
324
+
shared with the rest of the team. People whose nomination has been rejected can
325
+
be nominated at any time again in the future, three months after the previous
326
+
nomination at the earliest.
310
327
311
328
#### Current Recurring Contributors
312
329
@@ -366,7 +383,7 @@ These dedicated teams have no difference in how they are governed.
366
383
Decisions should be reached by consensus within the team with the Steering
367
384
Council and the BDFL acting if necessary.
368
385
369
-
The dedicated teams are a work units with two main objectives: better
386
+
The dedicated teams are work units with two main objectives: better
370
387
distributing the work related to The Project, and to better showcase all the task
371
388
involved in The Project to attract more diverse Contributors.
372
389
@@ -393,7 +410,18 @@ but also making sure there are resources to learn Bayesian statistics with
0 commit comments