1 |
> All this team's actions must be approved by the lead within a short time |
2 |
> period or must be reverted. It's expected that many actions will range |
3 |
> from 6-12 hours, so 12 hours seems like a reasonable time to require |
4 |
> lead approval. Whenever the lead is unavailable, approval falls to the |
5 |
> council. (Remember, two council members together can make decisions.) |
6 |
|
7 |
My only problem with this is if we are going to impower a team to |
8 |
enforce a CoC we should be prepared to stick by them. Also what is a |
9 |
short period of time wrt 12 hours? So either I would would hope that |
10 |
the approval of council with either be removed, or never used. |
11 |
|
12 |
Some solutions to this might be that (just making them up) the CoC team |
13 |
members can use there own judgment for actions lasting less than 6 |
14 |
hours, and this cannot be appealed or overruled. Also an offender may |
15 |
appeal to the CoC Team Leader (or Council) any offense punished by an |
16 |
action lasting 6-12 hours. I would like that to be implemented with the |
17 |
following as well. |
18 |
|
19 |
> The council |
20 |
> must approve all members of this team, and it must reassess them |
21 |
> annually to ensure they still interpret the CoC in the same way. |
22 |
> Furthermore, the team's lead will be appointed by the council to further |
23 |
> ensure a cohesive CoC interpretation. |
24 |
|
25 |
I believe that the reassessment of the CoC team should occur more |
26 |
frequently to begin with (at least). i.e. every 6 month's. As time |
27 |
progresses we may find that the period can be extended. But im sure we |
28 |
are all aware of the importance of setting this up correctly to begin with. |
29 |
|
30 |
I would therefore like to propose that initially there is something |
31 |
along the lines of:- |
32 |
|
33 |
* 3 Monthly Meetings, between council and CoC Team Leader where cases |
34 |
are reviewed and advice/discussion can occur. This should be followed |
35 |
shortly with a CoC meeting. |
36 |
|
37 |
* 6 Monthly Meeting, where council evaluates performance and vision of |
38 |
each CoC member. |
39 |
|
40 |
With a format like this, I hope we can strike a balance between having |
41 |
an independent CoC team but still have it tightly controlled by the |
42 |
council. I would hate for example of have the CoC team overruled |
43 |
continually by council members for minor issues ( for example, where a < |
44 |
6 hour cool down was overruled by Council). But I would also hate for |
45 |
the council to let the CoC team run a muck. |
46 |
|
47 |
If we are going to have a CoC team the council (as im sure you are well |
48 |
aware) should be prepared to stick by their decisions even when there is |
49 |
disagreement. This is especially important seeing that the Council has |
50 |
the final say on who is in the Team. Why pick them if you are going to |
51 |
be overruling them all the time. |
52 |
|
53 |
Anyway, I'm looking forward to some constructive feedback. |
54 |
|
55 |
Thank you Donnie for the work you have put in so far :) |
56 |
-- |
57 |
gentoo-council@g.o mailing list |