From: ram mohan <madhaviram123@yahoo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Contribute - How to
Date: Thu, 2 Dec 2004 20:39:32 -0800 (PST) [thread overview]
Message-ID: <20041203043932.57460.qmail@web90004.mail.scd.yahoo.com> (raw)
In-Reply-To: <41AFEB48.60800@osdl.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1729 bytes --]
I am interested to work in the following areas:
1. embedded systems
2. networking
I was wondering how can I contribute in embedded
without actual hardware.
Thanks.
--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> 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?
> It's all over the map:
> Large-systems performance & scalability.
> Embedded. Desktop issues.
> Journaling + extents-based filesystems.
> Drivers (new development in Infiniband and iscsi).
> VM fixes. Processor scheduling improvements.
> IO scheduler improvements.
> Fixing bugs. :)
>
> > 2. Are there any things-to-do lists maintained?
> There are by some projects, others are more informal
> and
> just discuss TODO on a mailing list.
>
> > 3. How are new features selected?
> a. scratch your favorite itch
> or
> b. what someone pays for
>
> What do you want to work on?
>
> > 4. Can I suggest new features?
> Of course. But part of the Linux culture is that
> ideas/suggestions don't carry much weight. It's
> sometimes phrased as:
> Shut up and code.
> or
> Show us the code.
> so send patches too. :)
>
> --
> ~Randy
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
__________________________________
Do you Yahoo!?
All your favorites on one personal page Try My Yahoo!
http://my.yahoo.com
next prev parent reply other threads:[~2004-12-03 4:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 4:20 ram mohan
2004-12-03 4:27 ` Randy.Dunlap
2004-12-03 4:39 ` ram mohan [this message]
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
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=20041203043932.57460.qmail@web90004.mail.scd.yahoo.com \
--to=madhaviram123@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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®