List of maintainers and how to submit changes

Please try to follow the guidelines below.  This will make things
easier on the maintainers.  Not all of these guidelines matter for every
trivial patch so apply some common sense.

1.	Always _test_ your changes, however small, on at least 4 or
	5 people/computers, preferably many more.

2.	Release ALPHA versions as you code so people are aware of the
	issue and progress made. Announce patches or bugs via e-mail.

3.	Make sure your changes work correctly in multiple configurations.

4.	When you are happy with a change make it known and available.

5.	Make a patch available to the relevant maintainer in the list. Use
	'diff -u' to make the patch easy to merge. Be prepared to get your
	changes sent back with seemingly silly requests about formatting
	and variable names.  These aren't as silly as they seem. One
	job the maintainers (and especially Linus) do is to keep things
	looking the same. Sometimes this means that the clever hack in
	your driver to get around a problem actually needs to become a
	generalized kernel feature ready for next time.

	PLEASE check your patch with the automated style checker
	(scripts/checkpatch.pl) to catch trival style violations.
	See Documentation/CodingStyle for guidance here.

	PLEASE try to include any credit lines you want added with the
	patch. It avoids people being missed off by mistake and makes
	it easier to know who wants adding and who doesn't.

	PLEASE document known bugs. If it doesn't work for everything
	or does something very odd once a month document it.

	PLEASE remember that submissions must be made under the terms
	of the OSDL certificate of contribution and should include a
	Signed-off-by: line.  The current version of this "Developer's
	Certificate of Origin" (DCO) is listed in the file
	Documentation/SubmittingPatches.

6.	Make sure you have the right to send any changes you make. If you
	do changes at work you may find your employer owns the patch
	not you.

7.	When sending security related changes or reports to a maintainer
	please Cc: security@kernel.org, especially if the maintainer
	does not respond.

8.	Happy hacking.

		-----------------------------------

Maintainers List (try to look for most precise areas first)

Note: For the hard of thinking, this list is meant to remain in alphabetical
order. If you could add yourselves to it in alphabetical order that would be
so much easier

P: Person
M: Mail patches to
L: Mailing list that is relevant to this area
W: Web-page with status/info
T: SCM tree type and location.  Type is one of: git, hg, quilt.
S: Status, one of the following:

	Supported:	Someone is actually paid to look after this.
	Maintained:	Someone actually looks after it.
	Odd Fixes:	It has a maintainer but they don't have time to do
			much other than throw the odd patch in. See below..
	Orphan:		No current maintainer [but maybe you could take the
			role as you write your new code].
	Obsolete:	Old code. Something tagged obsolete generally means
			it has been replaced by a better system and you
			should be using that.
	Holding:	In a holding pattern while other areas are being
			devoloped further.
	Feature Freeze:	No new features are being introduced into the code.
			Common at major packaging time.
	Fix Only:	Headed to obsolete.

Suite
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/suite

Applet
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Maintained
W:	http://PHPIRC.VJTD3.com/package/applet

Admin
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/admin

phpBB
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/phpbb

YaBB
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/yabb

X-Chat
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/xchat

mIRC
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/mirc

EggDrop
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/eggdrop

Services
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/services

IRCD
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/ircd

EggDropWeb
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/eggdropweb

ServicesWeb
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/servicesweb

IRCdWeb
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com/package/ircdweb

Community Tools
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com

Backward Tools
S:	Obsolete
W:	http://PHPIRC.VJTD3.com

Documentation
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com

Rest
P:	VJTD3
M:	phpirc at VJTD3 dot com
S:	Holding
W:	http://PHPIRC.VJTD3.com