Gentoo Archives: gentoo-commits

From: William Hubbs <williamh@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] data/glep:comrel commit in: /
Date: Mon, 17 Feb 2020 22:06:10
Message-Id: 1581977140.cd38ad5a2271b13227e75bf2f52b32fd76af6db3.williamh@gentoo
1 commit: cd38ad5a2271b13227e75bf2f52b32fd76af6db3
2 Author: William Hubbs <williamh <AT> gentoo <DOT> org>
3 AuthorDate: Mon Feb 17 21:56:25 2020 +0000
4 Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
5 CommitDate: Mon Feb 17 22:05:40 2020 +0000
6 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=cd38ad5a
7
8 pre-glep: community relations team role and purpose
9
10 Bug: https://bugs.gentoo.org/709994
11 Signed-off-by: William Hubbs <williamh <AT> gentoo.org>
12
13 glep-9999.rst | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
14 1 file changed, 109 insertions(+)
15
16 diff --git a/glep-9999.rst b/glep-9999.rst
17 new file mode 100644
18 index 0000000..bbf667f
19 --- /dev/null
20 +++ b/glep-9999.rst
21 @@ -0,0 +1,109 @@
22 +---
23 +GLEP: 9999
24 +Title: Community Relations Team's Role and Purpose
25 +Author: William Hubbs <williamh@g.o>
26 +Type: Standards Track
27 +Status: Draft
28 +Version: 1
29 +Created: 2020-02-17
30 +Last-Modified: 2020-02-17
31 +Post-History:
32 +Content-Type: text/x-rst
33 +---
34 +
35 +
36 +Abstract
37 +========
38 +
39 +This GLEP outlines the abilities and purpose of the Community Relations team
40 +for Gentoo.
41 +
42 +Motivation
43 +==========
44 +
45 +For years Gentoo has had a Community Relations team which assists with
46 +inter-developer and developer-user conflict resolution.
47 +This GLEP provides the formal structure for this team and specifies the
48 +roles the team fulfills.
49 +
50 +Specification
51 +=============
52 +
53 +General
54 +-------
55 +
56 +The Community Relations team should be given certain abilities which it
57 +can use to assist in solving non-technical conflicts between our developers
58 +and users in a fair and impartial manor. These abilities include
59 +mediation and disciplinary actions.
60 +
61 +* The purpose of the Community Relations team is to assist with
62 + resolving inter-developer and developer-user conflicts by mediation,
63 + or disciplinary actions if necessary.
64 +* The team is directed by a lead, chosen yearly by private or
65 + public election among the members, and confirmed by the council.
66 +* The lead's term expires one year after confirmation.
67 + * If the lead's position is vacant at any point during the term, the
68 + council may appoint an interim lead.
69 +* The lead must approve developers who would like to join the project.
70 + Because of the nature of Community Relations, it is important that
71 + applicants are respectful in how they handle themselves in the
72 + community. By accepting the applicant the lead will accept the
73 + responsibility to direct them as part of the team and will be held
74 + responsible for any action they take on behalf of the team.
75 +* To keep the distribution healthy, no Community Relations team member
76 + may serve on the council, QA Team, or as a proctor.
77 +* In the case of disagreement among members regarding an action, the
78 + majority of members must agree with the action.
79 +* Because of the nature of this work, it is important for the community
80 + relations team to respond within a reasonable amount of time when
81 + someone reaches out to them. If a contact isn't responded to within
82 + 72 hours, the council may be notified. At that point, someone on the
83 + council will attempt to discover why the team isn't responding and
84 + give the person an update.
85 +* If Community Relations decides that no action will be taken on an
86 + incident, the appropriate response is to close the incident and
87 + explain why no action will be taken. This may be appealed to the
88 + council by the person who filed the original complaint if they do not
89 + understand the reason the complaint was closed.
90 +* Anyone who is subject to a disciplinary action by Community Relations
91 + may appeal to the council. If this happens, the council will look over the
92 + complaint and make its own decision. If the council's decision is
93 + different from the Community Relations decision, the council's
94 + decision will be respected.
95 +
96 +Monthly Reporting
97 +-----------------
98 +
99 +Due to its nature, most of Community Relations work is private. This is
100 +important to protect the identities of the users and developers
101 +involved. However, it means that the rest of the community does not
102 +have a way to gauge the activities of Community Relations.
103 +
104 +To resolve this issue, the lead will be required to report the following
105 +monthly to the gentoo-project mailing list:
106 +
107 + * number of new mediation requests
108 + * number of mediation requests in process
109 + * number of resolved mediation requests
110 +* number of new complaints
111 +* number of complaints resolved with communication or disciplinary action
112 + * number of complaints resolved with no action.
113 +* number of complaints in process
114 + * number of withdrawn complaints
115 +
116 +If this information is not reported for three consecutive months, the
117 +lead will be replaced.
118 +
119 +
120 +Backwards Compatibility
121 +=======================
122 +
123 +Not a problem for this GLEP.
124 +
125 +Copyright
126 +=========
127 +
128 +This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
129 +Unported License. To view a copy of this license, visit
130 +https://creativecommons.org/licenses/by-sa/3.0/.