linux-kernel - My pledge as a maintainer to the developers sending me patches.

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>] [day] [month] [year] [list]

Message-ID: <20120618211510.GA11479@kroah.com>
Date:	Mon, 18 Jun 2012 14:15:10 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	linux-kernel@...r.kernel.org
Cc:	linux-usb@...r.kernel.org, linux-serial@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: My pledge as a maintainer to the developers sending me patches.

As I recently posted here:
	http://www.kroah.com/log/linux/maintainer_pledge.html
there's been lots of discussion about maintainers, their general
grumpiness, and how to handle this.  I don't want to duplicate what was
said in that post, except for the following.

Here's what I, as a kernel subsystem maintainer, will strive to do for
all patches sent to me by developers:

 1) I will review your patch within 1-2 weeks (see details below).
 2) I will offer semi-constructive criticism of your patches.
 3) I will let you know the status of your patch if it is rejected, or if
    it is accepted, what tree it has gone into, where you can find it,
    and when you can expect to see it merged into Linus's tree.

Notes on the above:

1) Of course, if I'm sick, or traveling on insane Asia trips, my
response time will be delayed, but feel free to email me asking the
status of a patch you have sent me, I'm happy to respond back that I
just haven't gotten to it.  I would much rather field these kinds of
inquiries (after waiting a few weeks) then loose patches and make people
mad.

Also, consider the kernel merge window requirements, during the merge
window, I can't accept new patches into my tree that are not bugfixes
for this specific kernel release, so that means there is usually a 3
week window starting about 1 week before Linus's release,
lasting until after a -rc1 kernel is released, before I can get to your
patch.  During that time period hundreds of patches accrue, so please
give me some time to dig out from all of them.  Usually by -rc3 I'm
caught up, if not, email me and ask.

2) Sorry, it can't always be constructive, but I'll try my best.  I'll
also try to not cast aversions about your cat, but if you taunt me, all
bets are off.

3) I have scripts that automatically do this, that were based on Andrew
Morton's older scripts, that any maintainer is more than willing to have
a copy of.  Here's the most recent copy at the moment, if you want to
look at it:
	https://github.com/gregkh/gregkh-linux/blob/master/work/do.sh

So, that's it, comments?  Criticism?

Note, I don't expect anyone else to do this, it's just what I am willing
to do.  I know some subsystem maintainers do a much better job than I do
(some subsystem response times to patches is amazing!), but I figured
I'd put this out there if anyone else wanted to rift on it.

thanks,

greg k-h
--
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/