From: Bill Davidsen <davidsen@tmr.com>
To: ram mohan <madhaviram123@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Contribute - How to
Date: Tue, 07 Dec 2004 12:32:22 -0500 [thread overview]
Message-ID: <41B5E926.7040302@tmr.com> (raw)
In-Reply-To: <20041203042003.57961.qmail@web90007.mail.scd.yahoo.com>
ram mohan wrote:
> Hi,
> I am willing to contribute to the development of Linux
> kernel. I googled a bit and found that I should join
> the list and then I can go ahead.
> I would like to know.
> 1. What are the features currently being worked upon?
> 2. Are there any things-to-do lists maintained?
See bugzilla for a list of current problems. Pick one, start small, test
the fix and submit patches. Alternately if you have any of hardware
around for which the 2.6 driver is marked broken, you can unbreak it. If
you do a good job you might become the maintainer for that driver (good
news/bad news).
> 3. How are new features selected?
> 4. Can I suggest new features?
Usually by someone coding them as proof of concept. However, before
starting code on anything large, an RFC (req for comments) post may
reveal someone else solving the problem, or that the cure is worse than
the problem for some inobvious reason, or that someone important (Linus,
akpm, DavidM) just doesn't like it even though it works perfectly and
introduces no new problems.
Good luck, glad to see someone ready to help.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-12-07 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 4:20 Contribute - How to ram mohan
2004-12-03 4:27 ` Randy.Dunlap
2004-12-03 4:39 ` ram mohan
2004-12-03 4:55 ` Randy.Dunlap
2004-12-03 9:46 ` Manu Abraham
2004-12-03 10:17 ` ram mohan
2004-12-03 12:16 ` Manu Abraham
2004-12-03 12:34 ` Magnus Damm
2004-12-03 17:58 ` Tim Hockin
2004-12-03 18:06 ` Zwane Mwaikambo
2004-12-03 4:56 ` Mark Miller
2004-12-03 4:58 ` Randy.Dunlap
2004-12-07 17:32 ` Bill Davidsen [this message]
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=41B5E926.7040302@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhaviram123@yahoo.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