All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: ram mohan <madhaviram123@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Contribute - How to
Date: Thu, 02 Dec 2004 20:55:52 -0800	[thread overview]
Message-ID: <41AFF1D8.5000104@osdl.org> (raw)
In-Reply-To: <20041203043932.57460.qmail@web90004.mail.scd.yahoo.com>

ram mohan wrote:
> 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.

Maybe someone else has some suggestions on that.

For Linux networking patches and discussion, please
use the "netdev" mailing list:
   netdev@oss.sgi.com
You can subscribe to it at:
   http://oss.sgi.com/ecartis
and the netdev archives are at:
   http://oss.sgi.com/projects/netdev/archive/


> --- "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


-- 
~Randy

  reply	other threads:[~2004-12-03  4:59 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 [this message]
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=41AFF1D8.5000104@osdl.org \
    --to=rddunlap@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.