1 |
While larger improvements may need some more time and discussion, we should at |
2 |
least do a minimal update to the Code of Conduct to bring it back into sync |
3 |
with organizational structure. This only affects the "Consequences" section. |
4 |
|
5 |
Here's the old, currently valid text and my draft as a starting point for |
6 |
discussion: |
7 |
|
8 |
===OLD TEXT=== |
9 |
|
10 |
=== Consequences === |
11 |
|
12 |
Disciplinary action will be up to the descretion of the proctors. What is a |
13 |
proctor? A proctor is an official charged with the duty of maintaining good |
14 |
order. Currently this responsibility falls to two existing Gentoo projects: |
15 |
[http://www.gentoo.org//proj/en/devrel DevRel] and |
16 |
[http://www.gentoo.org//proj/en/userrel UserRel]. |
17 |
|
18 |
If you perceive a breach of the Code of Conduct guidelines, let the |
19 |
appropriate proctors know. Though they will also be watching many of the |
20 |
public mediums for any problems, they can not be expected to catch |
21 |
everything. If the offender is a Gentoo developer, contact {{Mail| |
22 |
devrel@g.o}}, otherwise contact {{Mail|userrel@g.o}}. |
23 |
|
24 |
The proctors will attempt to resolve the problem by talking to involved |
25 |
parties, potentially issuing warnings if appropriate. If the problem repeats |
26 |
itself, there are various options open to the proctors, including |
27 |
temporary or permanent suspension of a person's ability to post to mailing |
28 |
lists, removal of Bugzilla access, or in more severe cases suspension of |
29 |
developer privileges. |
30 |
|
31 |
If discplinary measures are taken and the affected person wishes to appeal, |
32 |
appeals should be addressed to the Gentoo Council via email at |
33 |
{{Mail|council@g.o}}. To prevent conflicts of interest, Council members may |
34 |
not perform the duties of a proctor. |
35 |
|
36 |
|
37 |
===NEW DRAFT TEXT=== |
38 |
|
39 |
=== Consequences === |
40 |
|
41 |
Disciplinary action will be up to the discretion of the members of the |
42 |
[[Project:ComRel|Community Relations project]]. In the future, a sub-project |
43 |
of Community Relations may be founded to take care of this. |
44 |
|
45 |
If you perceive a breach of the Code of Conduct guidelines, let the |
46 |
appropriate people know. Though they will also be watching many of the public |
47 |
mediums for any problems, they can not be expected to catch everything. |
48 |
Community Relations can be contacted by e-mail via {{Mail|comrel@g.o}}. |
49 |
|
50 |
Community Relations members may attempt to resolve the problem by talking to |
51 |
involved parties, potentially issuing warnings if appropriate. If the problem |
52 |
repeats itself, there are various options open, including temporary or |
53 |
permanent suspension of a person's ability to post to mailing lists, removal |
54 |
of Bugzilla access, or in more severe cases suspension of developer |
55 |
privileges. Details on current guidelines can be found on the |
56 |
[[Project:ComRel|Community Relations project page]]. |
57 |
|
58 |
If discplinary measures are taken and the affected person wishes to appeal, |
59 |
appeals should be addressed to the Gentoo Council via email at {{Mail| |
60 |
council@g.o}}. To prevent conflicts of interest, Council members are expected |
61 |
not to participate in appeals proceedings if they have been active in the |
62 |
respective Community Relations code of conduct case. |
63 |
|
64 |
|
65 |
|
66 |
|
67 |
Am Dienstag, 3. Dezember 2013, 13:39:36 schrieb Donnie Berkholz: |
68 |
> In one week, the council will have its regular monthly meeting. Now is |
69 |
> the time to raise and prepare items that the council should put on the |
70 |
> agenda to discuss or vote on. |
71 |
> |
72 |
> (Apologies for the delay, I was on vacation most of last week for the |
73 |
> Thanksgiving holiday and am in London through tomorrow.) |
74 |
> |
75 |
> Please respond to this message with agenda items. Do not hesitate to |
76 |
> repeat your agenda item here with a pointer if you previously suggested |
77 |
> one (since the last meeting). |
78 |
> |
79 |
> I'd like to get the agenda out on Thursday or Friday to give everyone at |
80 |
> least a few days to prepare, so please reply promptly. |
81 |
> |
82 |
> Your responses should go to the gentoo-project list. |
83 |
|
84 |
|
85 |
|
86 |
-- |
87 |
|
88 |
Andreas K. Huettel |
89 |
Gentoo Linux developer |
90 |
dilfridge@g.o |
91 |
http://www.akhuettel.de/ |