Re: Dealing with ITS abuse
Russ Allbery wrote:
Chris Knadle<Chris.Knadle@coredump.us> writes:
> On Thursday, April 11, 2013 23:49:18, Filipus Klutiero wrote:
>> In absolute terms, contacting email@example.com is not a good way
>> of dealing with any problem, as firstname.lastname@example.org is - as indicated
>> inhttps://lists.debian.org/debian-project/2011/11/msg00030.html - a
>> private email alias, with little chance of solving the issue. If that
>> doesn't work, you can escalate the issue to project leadership as a
>> last resort... but you'll also hit a private email alias there.
> Emailing anyone privately leads down the path of "privatization". [I've
> already been down this road.] As such I think it might be better to
> publicly CC leadership, to invite public comment rather than private
> conversation, because private conversation cannot address the public
I think both of you have a very strange understanding of how human
psychology works if you think public callouts are the best first step in
dealing with inappropriate behavior. I also wonder what places you've
worked in and what sorts of management interactions you've had if you
don't believe private conversation can ever address public problems.
Although Chris's reply could sound like that out of context, I for one
have never stated that private conversation can never address public
problems (which doesn't mean that private conversation is always the
best way to address a public problem).
Nobody suggested public callouts neither - in a hierarchical context,
referring a controversial decision to a higher decision-making instance
is natural and a pacific way to try to reach a better decision.
However, Debian doesn't have a habit (for all the psychological reasons I
mention above) of creating a public wall of shame to record places where
people have been given a "penalty flag." If you weren't involved in the
issue, you probably didn't hear about it, and IMO that's how it should be.
Again, nobody's suggesting to create a public wall of shame, but that
doesn't mean consequences should be secret. Sorry but to avoid
rehashing, please see