1 |
Steve, |
2 |
|
3 |
I've in lined my words of wisdom ... you may not agree with them but |
4 |
they are mine, after all. |
5 |
|
6 |
On 2007.08.05 02:36, Steve Long wrote: |
7 |
> I was thinking about the recent discussion re flames and firefighting |
8 |
> on the dev m-l. One thing that occurred to me, as a user who has been |
9 |
> on one side of those, is that it would have been better if I had |
10 |
> never been able to post more than two posts in a day. (I mean this |
11 |
> for the technical dev m-l, not project.) |
12 |
That's ok as long as you only want to respond to flames and be off |
13 |
topic. It would limit the noise a non dev can create. As soon as you |
14 |
want to use -dev for its intended purpose, it would cramp your style. |
15 |
This could not be usefully automated |
16 |
|
17 |
> |
18 |
> That's plenty for me to say "I think that's out of order" and to |
19 |
> answer a response, but it also means I can't get too emotional if I |
20 |
> get flamed by a stressed-out dev. |
21 |
Nor can you easily take part in technical discussions, should you want |
22 |
to :) |
23 |
|
24 |
> After all, since the proctors have gone, there's no one to respond in |
25 |
> anything like mail-list time in the (admittedly unlikely ;) event |
26 |
> that there is another flamewar on the dev list and more cogently |
27 |
> no-one to mute a troublesome user (in real time). A dev who is |
28 |
> consistently anti-social (especially out of the blue when they should |
29 |
> just ignore the thread) can be dealt with by devrel. (And have been |
30 |
> in the past.) |
31 |
After the fallout from the "Bubble thread" that lead directly to the |
32 |
death of the proctors, -dev appears to have calmed down. I'm not sure |
33 |
if that's because the proctors got so much publicity over that one |
34 |
incident that everyone knows of it and reviewed their behavior, or if |
35 |
they have just gone on summer holidays. I think this list will help |
36 |
take the pressure of -dev too. |
37 |
> |
38 |
> If the user is making a valid point, surely others will post in |
39 |
> support, and in any event they can respond the next day. That would |
40 |
> minimise the chance that a user unused to the rough-and-tumble of dev |
41 |
> behaviour would react in a hostile manner, and can in no way be seen |
42 |
> as censorship of the user community, at least to my mind. |
43 |
If you are making a valid technical point, your posts don't need to be |
44 |
throttled. If not, you should not post to -dev at all. |
45 |
|
46 |
> |
47 |
> What do you think? |
48 |
> |
49 |
Social problems demand human in the loop control. That's why courts |
50 |
have (skilled ?) judges for sentencing, not just a look up table of |
51 |
offence - punishment. |
52 |
|
53 |
A part of Gentoos problem and probably other OS projects, is that most |
54 |
devs are still learning their social skills. They are school or |
55 |
university students. |
56 |
> -- |
57 |
> gentoo-project@g.o mailing list |
58 |
> |
59 |
|
60 |
Regards, |
61 |
|
62 |
Roy Bamford |
63 |
(NeddySeagoon) |
64 |
-- |
65 |
gentoo-project@g.o mailing list |