| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Tim Yamin wrote: |
| 5 |
>> So, here is my proposal. I hope it's not the only one. |
| 6 |
>> |
| 7 |
>> creation of a etiquette enforcement group. This group should be a |
| 8 |
>> subproject of devrel, but should not be made up of devrel members. I |
| 9 |
>> say this because the actions and powers of this group need to be |
| 10 |
>> separated from devrel. |
| 11 |
> |
| 12 |
> Who will lead the group? Also is the enforcer's powers limited purely to |
| 13 |
> spurs on IRC and mailing lists; i.e. behaviour issues and/or repetitive |
| 14 |
> patterns still go to devrel for discussion; complaints to Bugzilla, etc? |
| 15 |
|
| 16 |
Not me, I feel I can't do it while still belonging to the groups that |
| 17 |
I'm currently in unless there in a public vote and I'm voted in. |
| 18 |
|
| 19 |
>> - - enforcer sets modes +q troll for #foobar |
| 20 |
> |
| 21 |
> Devs (well, ops in the channel) have always had this capability; nothing |
| 22 |
> new. Also address problem of enforcer himself being an ass on IRC/MLs, |
| 23 |
> what happens then; we don't want a "that guy did it and he's reponsible |
| 24 |
> for good behaviour so I can do it too" happening... |
| 25 |
Yes, and what happens? someone else kicks the kicker. Addressing a |
| 26 |
enforcer who acts out is no different than addressing a devrel member |
| 27 |
who does the same. we try to select people that won't do that, but when |
| 28 |
it happens we deal with it in the best possible way. |
| 29 |
|
| 30 |
>> Sometimes people need a bigger kick in the ass though, which is where a |
| 31 |
>> short term ban helps. When I say a short term ban, I mean 30-90 |
| 32 |
>> minutes. it allows everyone to cool off without them using bad judgment |
| 33 |
>> and popping back in. I do similar enforcement in #-amd64 and it works |
| 34 |
>> very well. |
| 35 |
> |
| 36 |
> ... making sure that said person is informed of the ban, otherwise it |
| 37 |
> might be useless and have no effect. |
| 38 |
agreed. |
| 39 |
|
| 40 |
>> 1. any and every action that the enforcer uses to enforce etiquette |
| 41 |
>> needs to be immediately and publicly documented. as a start I recommend |
| 42 |
>> sending a email to gentoo-devrel ML. This includes full logs/archive |
| 43 |
>> pointers. |
| 44 |
> |
| 45 |
> gentoo-devrel isn't a database for etiquette violations given that it's |
| 46 |
> archived all over the place. You need a more appropriate place. |
| 47 |
|
| 48 |
make it bugs or a webpage or whatever. I don't care so long as it's public. |
| 49 |
|
| 50 |
>> 4. if an enforcer has effected a ban on a person/group and the subject |
| 51 |
>> was a time sensitive topic, then the enforcer is obligated to relay |
| 52 |
>> messages verbatim from the person/group for the duration of the ban. |
| 53 |
> |
| 54 |
> Topic such as? And if it's verbatim what's the point of the ban? |
| 55 |
The point here is that in a time sensitive situation that even the troll |
| 56 |
should get his fair say. This is the best that I could come up with. I |
| 57 |
hope that someone else can suggest a better way. |
| 58 |
|
| 59 |
- -- |
| 60 |
======================================================= |
| 61 |
Mike Doty kingtaco@g.o |
| 62 |
Gentoo/AMD64 Strategic Lead PGP Key: 0xA797C7A7 |
| 63 |
Gentoo Developer Relations |
| 64 |
===GPG Fingerprint=== |
| 65 |
0094 7F06 913E 78D6 F1BB 06BA D0AD D125 A797 C7A7 |
| 66 |
======================================================= |
| 67 |
-----BEGIN PGP SIGNATURE----- |
| 68 |
Version: GnuPG v1.4.3 (GNU/Linux) |
| 69 |
|
| 70 |
iD8DBQFEbNzN0K3RJaeXx6cRAleVAJ9a9fwOEW+54AsxpGJHakD4R4uvtwCeOL73 |
| 71 |
tgFG3yNLkvK6thRRqzyShsg= |
| 72 |
=uQBK |
| 73 |
-----END PGP SIGNATURE----- |
| 74 |
-- |
| 75 |
gentoo-devrel@g.o mailing list |
Archives