William L. Thomson Jr. wrote:

> On Sat, 2007-07-14 at 10:24 -0600, Ryan Hill wrote:
>> Alin N?stac wrote:
>> 
>> > Do you have a solution to filter flamefests out of a ml? If you do,
>> > please share it with the list.
>> 
>> Please give one example of a mailing list plagued by flamefests that
>> successfully solved their problems by adopting moderation without
>> completely alienating their communities.
> 
> With two lists we could potentially reduce a single unified bonfire into
> two controlled burns :)
> 
You already have two lists. Your argument that core is for more private
stuff, but not developer communication seems odd. My impression (never
having seen a core message) is that core doesn't actually function that
well, since dev v dev flames spill onto this list. If you are saying that
all developer discussion is supposed to happen on dev, fine, but I really
do not understand why that should mean users are not allowed to contribute
as you suggested in your other post.

As for moderation, the simple fact is that your devs have neither the time
nor the experience to do such a job. The ones that have the inclination
should probably be kept from it, in the same way that those who lust after
power should never get it. If you want the list to function of course you
need to have moderators who can suspend access or warn people to back off.
When my access was suspended, I didn't like it but I accepted the team's
decision-- because it was a team decision, from experienced moderators, not
just the decision of some random dev.

Good luck with reinventing everything and discussing the same stuff you have
for the last year that led to the formation of the Proctors. I accept that
the decision to disband them has been taken, although it seems odd that no
notification of the meeting which led to this latest change was given.
Obviously I think this is a major strategic error, and it's sad that rather
than one member admit a mistake, the present Council has to override the
consensus that took so long to reach.


-- 
[EMAIL PROTECTED] mailing list

Reply via email to