lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130718160754.GC5440@xanatos>
Date:	Thu, 18 Jul 2013 09:07:54 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Guenter Roeck <linux@...ck-us.net>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	stable <stable@...r.kernel.org>,
	Darren Hart <dvhart@...ux.intel.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [ 00/19] 3.10.1-stable review

On Thu, Jul 18, 2013 at 12:39:07PM +0200, Ingo Molnar wrote:
> 
> * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> > On Mon, Jul 15, 2013 at 1:41 PM, Sarah Sharp
> > <sarah.a.sharp@...ux.intel.com> wrote:
> > >
> > > Oh, FFS, I just called out on private email for "playing the victim
> > > card".  I will repeat: this is not just about me, or other minorities.
> > > I should not have to ask for professional behavior on the mailing lists.
> > > Professional behavior should be the default.
> > 
> 
> > [...]
> > 
> > Because if you want me to "act professional", I can tell you that I'm 
> > not interested. I'm sitting in my home office wearign a bathrobe. The 
> > same way I'm not going to start wearing ties, I'm *also* not going to 
> > buy into the fake politeness, the lying, the office politics and 
> > backstabbing, the passive aggressiveness, and the buzzwords. Because 
> > THAT is what "acting professionally" results in: people resort to all 
> > kinds of really nasty things because they are forced to act out their 
> > normal urges in unnatural ways.
> 
> Sarah, that's a pretty potent argument by Linus, that "acting 
> professionally" risks replacing a raw but honest culture with a
> polished but dishonest culture - which is harmful to developing
> good technology.
> 
> That's a valid concern. What's your reply to that argument?

I don't feel the need to comment, because I feel it's a straw man
argument.  I feel that way because I disagree with the definition of
professionalism that people have been pushing.

To me, being "professional" means treating each other with respect.  I
can show emotion, express displeasure, be direct, and still show respect
for my fellow developers.

For example, I find the following statement to be both direct and
respectful, because it's criticizing code, not the person:

"This code is SHIT!  It adds new warnings and it's marked for stable
when it's clearly *crap code* that's not a bug fix.  I'm going to revert
this merge, and I expect a fix from you IMMEDIATELY."

The following statement is not respectful, because it targets the
person:

"Seriously, Maintainer.  Why are you pushing this kind of *crap* code to
me again?  Why the hell did you mark it for stable when it's clearly
not a bug fix?  Did you even try to f*cking compile this?"

I would appreciate it if people would replace the word "professional"
with "respectful" in this thread.  It means something different to me
than other people, and respect is much closer to what I'm looking for.

I would appreciate it if kernel developers would show respect for each
other, while focusing on criticizing code.  As Rusty said, be gentle
with people.  You've called their baby ugly.

Sarah Sharp
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ