OT: General behaviour of the community (from 'Why winetools is
utterly useless, once and for all')
chmorgan at gmail.com
Wed Mar 29 17:56:33 CST 2006
> > I'm pretty sure people are capable of filtering their own email.
> > Afaict the offending emails were between two individuals. You may not
> > like them but that has no bearing on whether they should be allowed to
> > post to the mailing list given that those emails to the mailing list
> > are appropriate.
> > Chris
> Be that as it may, the person who made those comments made them as a direct
> attack on someone who posted to the list. Regardless of whether or not the
> insults were posted to the list, he shouldn't have made them. As the person
> who reported the incident said, had it been a new developer interested in
> helping wine (either directly by contributing code to the project, or
> indirectly by writing a support app), he probably would have said screw
> this, I'm not going to help out a project that has developers who verbally
> attack me. I know I would have.
How do you propose we prevent people from emailing people that post to
wine-devel? How do we choose who gets to email people directly and
who doesn't? How do we filter the contents of their email?
Segin doesn't speak for the entire community and he isn't a lead on
the project. If that were the case this would be a more serious
matter. If people quit because of him then what are we to do? Given
the lack of relationship between wine and Segin they might as well
have quit wine development because of some Nigerian money transfer
email or other spam.
My point is that the solution isn't trying to enforce censorship where
you simply cannot and where it doesn't impact the community. As long
as he doesn't abuse his list membership we have no reason to become
involved in this issue. You won't find me supporting any kind of
restrictions on what he says or which mailing lists he can belong to
at this point in time.
More information about the wine-devel