From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: PATCH: Driver Maintainers
Date: Tue, 5 Nov 2002 18:22:31 +0000 (GMT) [thread overview]
Message-ID: <E1898LP-0003Ie-00@the-village.bc.nu> (raw)
I've been getting more and more people talking to me looking to pay people to
fix small Linux bugs but having problems finding smaller companies. Obviously
wanting to send $1000 to have someone fix a driver simply doesn't work when
you talk to big companies.
One thing the FSF do which is rather sensible is keep a list in the packages
of people who you can pay to fix stuff in them. I asked on Linux-kernel
and got a small initial set of company responses. hopefully more will appear
once its merged.
The order is alphabetical logically enough
[Marcelo this seems to apply cleanly to 2.4 as well]
Alan
--
--- ../linux.2.5.46/MAINTAINERS 2002-11-05 13:54:42.000000000 +0000
+++ MAINTAINERS 2002-11-05 16:11:31.000000000 +0000
@@ -1,6 +1,9 @@
List of maintainers and how to submit kernel changes
+ (Please also see Documentation/DriverFixers for people who offer driver
+ development and fixing as a business)
+
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.
--- /dev/null 2002-08-31 00:31:37.000000000 +0100
+++ Documentation/DriverFixers 2002-11-05 18:41:26.000000000 +0000
@@ -0,0 +1,37 @@
+People who fix drivers as a business - ie for money. (No recommendation,
+business association or other relationship implied. This for the benefit of
+American lawyers is just a list of people who have asked to be listed - nothing
+more).
+
+
+Company: BitWizard
+Contact: Rogier Wolff
+E-Mail: R.E.Wolff@BitWizard.nl
+
+Company: Caederus
+Contact: Justin Mitchell
+E-Mail: info@caederus.com
+URL: http://www.caederus.com/
+Location: Swansea, Wales, UK
+
+Company: Weinigel Ingenjörsbyrå AB
+Contact: Christer Weinigel
+E-Mail: christer@weinigel.se
+Location: Stockholm, Sweden
+
+Company: WildOpenSource
+Contact: Martin Hicks
+E-Mail: info@wildopensource.com
+
+
+To be added to the list: email <alan@lxorguk.ukuu.org.uk> giving the
+following information
+
+Company: CompanyName [Required]
+Contact: ContactName [Required]
+E-Mail: An email address [Required]
+URL: Web site [Optional]
+Location: Area/Country [Optional]
+Telephone: Contact phone number [Optional]
+Notes: Any other notes (eg certifications, specialities)
+
next reply other threads:[~2002-11-05 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 18:22 Alan Cox [this message]
2002-11-05 18:43 ` Linus Torvalds
2002-11-05 20:16 ` Alan Cox
2002-11-05 21:24 ` Joel Becker
2002-11-06 8:36 ` Leif Nixon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1898LP-0003Ie-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®