linux-kernel - Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML

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: <1374022296.6458.118.camel@gandalf.local.home>
Date:	Tue, 16 Jul 2013 20:51:36 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jeff Liu <jeff.liu@...cle.com>
Cc:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	David Lang <david@...g.hm>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Darren Hart <dvhart@...ux.intel.com>,
	Olivier Galibert <galibert@...ox.com>,
	stable <stable@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Willy Tarreau <w@....eu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML

On Wed, 2013-07-17 at 08:32 +0800, Jeff Liu wrote:

> Another thing might deviated from the main theme, but I'd like to raise it
> here because I would like to see what's the proper way for that.
> 
> For instance, people A posted a patch set to the mailing list at first,
> people B think that there are some issues in A's implementation, and he
> happened to play around the same stuff recently, so he submitted another
> patch series.  Finally, people B made it.
> (In that period, people A kept silent, maybe because he/she was unhappy) 
> 
> This is a actual occurrence I once observed from a subsystem list(my
> apologies, I just want to talk this case rather than against somebody),
> it seems people A is a new comer(because I can not searched any past
> commits of him/her from the git log), people B is definitely a senior guy.
> 
> So that's my question, is that a proper collaboration form in kernel
> community?  Does it better if people B could give some suggestions to
> help A to improve the code, especially if those help would help A stepping
> into the kernel development -- maybe it's depend largely on one's opinion. :(

This is a completely different issue from the one in this thread, but it
is also a legitimate issue and honestly, a bigger one than perceived
insults.

Is it proper collaboration? Absolutely not. Something that I try to be
sensitive to as it's something I can do as well. There's been things on
my todo list, where someone would send me patches that do it. I would be
thinking "darn it, I wanted to do it" and even worse, the patches that
were sent wouldn't be of the way I wanted them. But I've tried to be
good, and instead of just going about and implementing it myself, I
would try to help the person massage the patches into what I wanted.
That takes a lot of effort and discipline, and honestly, helping someone
else do the work you wanted is much harder than just doing it yourself. 

Sometimes the maintainer just takes the easier route, and does the work
themselves (because it's also more fun too). But that's really a slap in
the face of the person that submitted the work in the first place. If
anything hurts the community, it's this behavior. Not Linus giving
someone an ass wipe.

-- Steve

--
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/