Re: Should mailing list bans be published?
On Sat, Oct 26, 2013 at 12:58:34PM -0700, Steve Langasek wrote:
> Hi Bart,
> On Sat, Oct 26, 2013 at 07:33:34PM +0000, Bart Martens wrote:
> > On Sat, Oct 26, 2013 at 10:46:41AM -0700, Steve Langasek wrote:
> > > This led to a philosophical debate about whether bans should be made public.
> > > Alexander expressed concern that having them published could be harmful to a
> > > person's reputation, since employers will google your name and see that
> > > you've been banned from a large project such as Debian.
> > I join Alexander on the above.
> > > What do the rest of you think?
> > I suggest we keep things civil, with respect for the persons involved.
> > It's really not up to Debian to harm someone's reputation, and that could
> > reflect bad on Debian's reputation.
> I don't understand this argument. What harm comes to Debian's reputation
> from showing publically that we do not tolerate abusive behavior on our
> mailing list?
The harm that could come to Debian's reputation is that Debian could be
perceived as an organization that harms people's reputation by judging them in
public about their behavior on the mailing lists.
> > Approaches I could support :
> > - post the bans with reasons on debian-private
> > - or maintain a list of bans with reasons in a text file on a Debian machine
> > where DDs can read this info.
> I think posting this on debian-private is not as good as posting it
> publically, for some of the reasons mentioned in my original mail. (E.g.,
> making it clear to outsiders that certain behavior will not be tolerated.)
That can be made clear without harming individuals' reputations.
> But it's a compromise I could support, if that's the consensus in the
I appreciate that you are open for this compromise. Let's see if it becomes a
> I don't think maintaining a list "somewhere" is sufficient; there should be
> some notification to the project when the bans take place.
I can imagine that some DDs prefer to receive notifications, which can be
obtained by simply using diff in crontab.