	List of maintainers and how to submit changes (borrowed from Linux)

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, preferably many more.

2.	When you are happy with a change make it generally available for
	testing and await feedback.

3.	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. 

	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.

4.	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.

5.	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 by responsible area. If you could add yourselves to it in alphabetical order that would
so much easier. 

P: Person
M: Mail patches to
L: Mailing list that is relevant to this area
W: Web-page with status/info
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.

AWARE CORE 
P: Russell Leighton
M: russ@elegant-software.com
W: http://www.elegant-software.com/software/aware
S: Maintained

SQL Server (FREETDS) Probe/Handler
P: Ramesh Mendu
M: rmendu@loginsoft.com
W: 
S: Maintained





