@@ -27,36 +27,36 @@ Active Time
27
27
-----------
28
28
29
29
This workgroup will be active indefinitely while supported by the Python
30
- Steering Council.
30
+ Steering Council.
31
31
32
32
Core Values & Internal Government
33
33
---------------------------------
34
34
35
35
The core values for this group are:
36
36
37
- - Respect
38
- - Support
39
- - Positive Atmosphere
40
- - Constructiveness
41
- - Integrity
37
+ - Respect
38
+ - Support
39
+ - Positive Atmosphere
40
+ - Constructiveness
41
+ - Integrity
42
42
43
43
The workgroup adopts the PSF Code of Conduct (https://www.python.org/psf/codeofconduct/).
44
44
Any actions (found by a majority) made against the principles in the Code of
45
- Conduct will result in the acting person being removed from the workgroup.
45
+ Conduct will result in the acting person being removed from the workgroup.
46
46
47
47
Rules & Guidelines
48
48
------------------
49
49
50
50
- At any time the Python Steering Council may, at its discretion, add any number
51
51
of non-voting observers to the working group to observe and participate in
52
- discussion.
52
+ discussion.
53
53
- The group's purview includes the Sphinx documentation included in the Python
54
54
source repository, including the doc theme, as well as separate projects such
55
55
as the developer guide. Translations and infrastructure will be managed by
56
56
Julien Palard or a Steering Council appointed member.
57
57
- The group will also maintain documentation of meetings and best practices.
58
58
- The editorial board will include people outside of the core developers who are
59
- tech writers or educators.
59
+ tech writers or educators.
60
60
61
61
Decision Making Procedures
62
62
--------------------------
@@ -66,21 +66,21 @@ propose or request a topic for a decision.
66
66
67
67
- In general, a topic for decision should address one of the workgroup's goals:
68
68
- Improve or maintain the state of Python's documentation effort by some
69
- noticeable or measurable amount.
69
+ noticeable or measurable amount.
70
70
- Increase the participation of contributors to documentation
71
71
72
72
When adding new members to the working group, prospective members must send an
73
73
email to introduce themselves along with a description of why they want to be
74
74
a member and what they bring to the process. Approval of new members will be
75
- decided using the voting procedures detailed below.
75
+ decided using the voting procedures detailed below.
76
76
77
77
Voting
78
78
------
79
79
80
80
A vote for any proposal will last for 5 days, or when all voting members have
81
81
voted, whichever comes first. For a proposal to be successful it must have at
82
82
least two +1's, more +1's than -0's, and no -1. Voting may be done in any venue
83
- given agreement of all voting members.
83
+ given agreement of all voting members.
84
84
85
85
Communication Plan
86
86
------------------
0 commit comments