1 |
Michał Górny wrote: |
2 |
> Hello, everyone. |
3 |
> |
4 |
> Since the things around ComRel seem to have cooled down a bit, I think |
5 |
> we can now start a serious discussion on how disciplinary action |
6 |
> handling could be improved. While the recent complaints were focused on |
7 |
> ComRel, I would like to take a more generic approach since ComRel is |
8 |
> not the only body in Gentoo capable of disciplinary action. |
9 |
> |
10 |
> Therefore, I'd like my proposal to concern all cases of disciplinary |
11 |
> action, involving but not limited to: ComRel, QA, Forum moderators, IRC |
12 |
> moderators, Wiki admins and any other entity capable of enforcing |
13 |
> a disciplinary action against developers and users. |
14 |
> |
15 |
> Note: throughout the mail 'users' include all people involved on |
16 |
> the Gentoo communication channels, developers, users, bystanders |
17 |
> and bots alike. |
18 |
> <<< SNIPPAGE >>> |
19 |
> |
20 |
> |
21 |
> What do you think? |
22 |
> |
23 |
|
24 |
I help moderate/admin a social site. I sometimes have to remove |
25 |
content, restrict and ban members. I don't know how much of this can |
26 |
apply because I don't know if some or any of this is possible on Gentoo |
27 |
sites including B.G.O., IRC etc etc. |
28 |
|
29 |
As a example of how we do things. If I remove content, I take |
30 |
screenshots of it and then document it in a private staff only area. It |
31 |
doesn't matter if it is text, images or what. If the site owner gets a |
32 |
complaint or question, or another staff member wants to see what the |
33 |
member did, they can look and see what it was for even if I'm not |
34 |
online. If it is severe enough to require restriction of posting |
35 |
privileges, then I go do that as well. When the member comes back |
36 |
online, they get a notice that the account is restricted and to provide |
37 |
further notice to the member, plus anyone else wondering, the word |
38 |
Restricted is shown next to their name publicly. It's a |
39 |
yellowish/orange color but that may not matter here. Also, the member |
40 |
can see who did the restriction, how long it will last and the reason |
41 |
for it. I enter that in during the restriction process. Other members |
42 |
can see that the member is restricted but not what for or how long or by |
43 |
who. Only the member is question can see that part. |
44 |
|
45 |
If the post/content is severe enough to require a ban, then the member |
46 |
when they return is shown that their account has been banned, the reason |
47 |
for it and who did it. Also, next to the members name, it shows in red |
48 |
the word Banned. Again, other members know the ban occurred but not who |
49 |
did it or why. The member that is banned tho does see who did it and |
50 |
why. Again, it provides privacy but also lets other members know not |
51 |
to expect future communication. |
52 |
|
53 |
With that system, the person that action was taken on knows who did it, |
54 |
why and for how long or if they are banned. At the same time, other |
55 |
members can not see anything but that they are restricted or banned. |
56 |
That allows some privacy which you seem to want maintained but also |
57 |
gives enough info in public as to why they are no longer active. |
58 |
|
59 |
This is the good thing about this system. Let's say ComRel John gets a |
60 |
complaint and suspends posting privileges for one week for member xyz. |
61 |
The member that is suspended can see that they can no longer post, that |
62 |
it was either done by John or ComRel, your choice on that, plus others |
63 |
can see why they are no longer participating in whatever activity was |
64 |
going on. Also, if John did something he shouldn't have, other ComRel |
65 |
members can see it but you may can set it so that the council members |
66 |
can see it as well. This way the people that need to know the details |
67 |
have it available but it is not public. Also, you may or may not want |
68 |
to set it up so that another person, team lead or council, can reverse |
69 |
the action of John. |
70 |
|
71 |
Again, this may not be possible for Gentoo. However, it may give some |
72 |
out of the Gentoo box thinking. One thing about it, the person may not |
73 |
even have to appeal what John did. If it is set so that the ComRel lead |
74 |
or council can see what happened and why, and they disagree, it could be |
75 |
corrected fairly quickly. It all depends on just how you can set this |
76 |
up on Gentoo. The private staff area may be bugzilla or something |
77 |
else. On mailing lists, I'm not sure how this would work unless a email |
78 |
is sent to the mailing list the person is subscribed to that says member |
79 |
xyz is restricted. Maybe some automatic method that is scripted or |
80 |
something. |
81 |
|
82 |
Just throwing out ideas. I hope it makes sense. ;-) Putting it into |
83 |
text isn't so easy. |
84 |
|
85 |
Dale |
86 |
|
87 |
:-) :-) |