1 |
On Wed, 26 Nov 2014 16:52:07 -0500 |
2 |
Rich Freeman <rich0@g.o> wrote: |
3 |
|
4 |
> On Wed, Nov 26, 2014 at 4:21 PM, Tom Wijsman <TomWij@g.o> |
5 |
> wrote: |
6 |
> > On Sat, 22 Nov 2014 00:34:33 +0000 (UTC) |
7 |
> > Duncan <1i5t5.duncan@×××.net> wrote: |
8 |
> > |
9 |
> >> While it pains me to say this, unfortunately it looks like we have |
10 |
> >> another "toxic person" situation to deal with, with all the |
11 |
> >> implications that come with it. Maybe it's time to deal with it. |
12 |
> > |
13 |
> > Toxic wars have casualties; in one of the sides, or in both of them. |
14 |
> > |
15 |
> > IOTW; you're already dealing with it, you can only change the |
16 |
> > outcome. |
17 |
> > |
18 |
> |
19 |
> Can you be clear as to what you're recommending? |
20 |
|
21 |
To look at the outcome and shape it for the better, whichever way fits. |
22 |
|
23 |
> Are you suggesting that instead of trying to mediate between people |
24 |
> who don't get a long, it would be better to just pick one or the other |
25 |
> as the winner and boot the other out? |
26 |
|
27 |
"..., or in both of them"; and to be complete, let me add "or neither". |
28 |
|
29 |
> One of the challenges here is that if we were talking about just one |
30 |
> productive person who tended to drive everybody away that would be one |
31 |
> thing. The problem is that we have a lot of productive people who |
32 |
> have different sorts of personality quirks. They range from blowing |
33 |
> up in public, to constant passive-aggression, to just silently doing |
34 |
> their own thing completely ignoring any input whatsoever. I'm sure I |
35 |
> missed a few, like writing excessively-long emails. :) |
36 |
|
37 |
The challenge lies in how far to push and/or hold back people and/or |
38 |
their content; exploring the spectrum between active and passive |
39 |
moderation, as well as the different types of warnings and actions. |
40 |
One or more clear positive messages, followed by an action of 24h, ... |
41 |
|
42 |
> I guess one of the advantages of a model where devs turn into |
43 |
> reviewers instead of authors is that you can prioritize people skills |
44 |
> since their main role isn't to actually write the code so much as to |
45 |
> coordinate things. However, this assumes that people would still |
46 |
> contribute in such a model. |
47 |
|
48 |
It also assumes the model to change attitude. |