linux-kernel - Re: [ATTEND] How to act on LKML (was: [ 00/19] 3.10.1-stable review)

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]

Date:	Mon, 15 Jul 2013 15:36:15 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Guenter Roeck <linux@...ck-us.net>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.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>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	Willy Tarreau <w@....eu>
Subject: Re: [ATTEND] How to act on LKML (was: [ 00/19] 3.10.1-stable review)

On Mon, Jul 15, 2013 at 06:08:29PM -0400, Steven Rostedt wrote:
> On Mon, 2013-07-15 at 14:50 -0700, Linus Torvalds 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.
> > 
> > Bullshit.
> > 
> 
> Can we please make this into a Kernel Summit discussion. I highly doubt
> we would solve anything, but it certainly would be a fun segment to
> watch :-)

I agree, KS is where this conversation should be taking place.
Attendees for this conversation (so far) should be Greg KH, Linus,
Darren Hart, Steve Rostedt, Willy Tarreau, and me.

> > So as far as I'm concerned, the discussion is about "how to work
> > together DESPITE people being different". Not about trying to make
> > everybody please each other. Because I can pretty much guarantee that
> > I'll continue cursing. To me, the discussion would be about how to
> > work together despite these kinds of cultural differences, not about
> > "how do we make everybody nice and sing songs sound the campfire"
> > 
> > Do you think you might be interested in *that* kind of discussion
> > instead of the "you are abusing me" kind of discussion?
> > 
> > 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.

Yes, let's move this conversation into the "how to work together DESPITE
people being different" realm.  I would be happy to have that
discussion.  As Linus said, some people work together better than
others.  Some people have different expectations of appropriate ways to
interact with co-workers.  Sometimes that means that people only work
with certain other co-workers, like Greg and I.

The people who want to work together in a civil manner should get
together and create a "Kernel maintainer's code of conduct" that
outlines what they expect from fellow kernel developers.  The people who
want to continue acting "unprofessionally" should document what
behaviors set off their cursing streaks, so that others can avoid that
behavior.  Somewhere in the middle is the community behavior all
developers can thrive in.

Some people won't agree with everything in that document.  The point is,
they don't have to agree.  They can read the document, figure out what
the community expects, and figure out whether they can modify their
behavior to match.  If they are unwilling to change, they simply don't
have to work with the developers who have signed it.

Perhaps a trusted third party could take a stab at a first draft of this
document?  Greg KH?  Steve Rostedt?  Darren Hart?

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/