Contribute - How to

Contribute - How to

[ram mohan]

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?
3. How are new features selected?
4. Can I suggest new features?

Thanks.



		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 

Re: Contribute - How to

[Randy.Dunlap]

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

Re: Contribute - How to

[ram mohan]

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

Re: Contribute - How to

[Randy.Dunlap]

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

Re: Contribute - How to

[Mark Miller]

On Thu, 02 Dec 2004 20:27:52 -0800, Randy.Dunlap <rddunlap@osdl.org> wrote:
> ram mohan wrote:

> > 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.  :)

While this may be true of those on the Linux Kernel Mailing List, I
would hope (from your statement of "Linux Culture", this would involve
things periphially related to Linux, such as KDE), that ideas and
suggestions would actually carry _some_ wait.

Although I can fully understand developers of the Linux Kernel taking
this mindset, since it is not dealing with such things as the User
Interface.

Just something I've had to deal with recently. Don't mind me.
 
> --
> ~Randy

-- 
Mark A. Miller               
mirell@gmail.com              
US +1 512 796 3592     
http://mirell.org
--------------------------------------------------------
Vice President and CFO of Linucon
http://linucon.org

Re: Contribute - How to

[Randy.Dunlap]

Mark Miller wrote:
> On Thu, 02 Dec 2004 20:27:52 -0800, Randy.Dunlap <rddunlap@osdl.org> wrote:
> 
>>ram mohan wrote:
> 
> 
>>>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.  :)
> 
> 
> While this may be true of those on the Linux Kernel Mailing List, I
> would hope (from your statement of "Linux Culture", this would involve
> things periphially related to Linux, such as KDE), that ideas and
> suggestions would actually carry _some_ wait.

Good or bad, I mostly use the word "Linux" to mean the kernel,
not the entire collection of system software.

> Although I can fully understand developers of the Linux Kernel taking
> this mindset, since it is not dealing with such things as the User
> Interface.

Sure, it's up to each open source project to deal with feature
requests or suggestions in whatever way that the people in
the project(s) choose.

> Just something I've had to deal with recently. Don't mind me.


-- 
~Randy

Re: Contribute - How to

[Manu Abraham]

On Fri December 3 2004 8:39 am, 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.

Well, to contribute you should have the hardware and or the documentation, 
depend on what you would like to contribute. You can work on with an initrd, 
if you are looking at embedded development on the x86 platform.

Even a retarded old PC can be considered as a development platform for x86 
embedded development.

Manu
>
> 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
> -
> 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/

Re: Contribute - How to

[ram mohan]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3309 bytes --]

way suggested looks interesting ..
i was thinking of contributing in terms of device
drivers/low level stuff .. searching for a todo list
in this area..
--- Manu Abraham <manu@kromtek.com> wrote:

> On Fri December 3 2004 8:39 am, 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.
> 
> Well, to contribute you should have the hardware and
> or the documentation, 
> depend on what you would like to contribute. You can
> work on with an initrd, 
> if you are looking at embedded development on the
> x86 platform.
> 
> Even a retarded old PC can be considered as a
> development platform for x86 
> embedded development.
> 
> Manu
> >
> > 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
> > -
> > 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/
> -
> 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!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

Re: Contribute - How to

[Manu Abraham]

On Fri December 3 2004 2:17 pm, ram mohan wrote:
> way suggested looks interesting ..
> i was thinking of contributing in terms of device
> drivers/low level stuff .. searching for a todo list
> in this area..
>
Well, there's lot to be done, and contributors are less. It's just an 
understanding of the hardware that you want to contribute to.

Contribution in the area of device drivers can range from small additions to 
existing drivers and or totally new and or large drivers totally from the 
ground up.

Well, it all depends just how well you know the hardware, writing a driver is 
nothing more than a technical description of what the hardware can do in a 
programming language.

Another area, could be sending in patches for bugs in existing drivers.


Manu

> --- Manu Abraham <manu@kromtek.com> wrote:
> > On Fri December 3 2004 8:39 am, 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.
> >
> > Well, to contribute you should have the hardware and
> > or the documentation,
> > depend on what you would like to contribute. You can
> > work on with an initrd,
> > if you are looking at embedded development on the
> > x86 platform.
> >
> > Even a retarded old PC can be considered as a
> > development platform for x86
> > embedded development.
> >
> > Manu
> >
> > > 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
> > > -
> > > 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/
> >
> > -
> > 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!?
> Yahoo! Mail - 250MB free storage. Do more. Manage less.
> http://info.mail.yahoo.com/mail_250

Re: Contribute - How to

[Magnus Damm]

On Thu, 2 Dec 2004 20:39:32 -0800 (PST), ram mohan
<madhaviram123@yahoo.com> wrote:
> I was wondering how can I contribute in embedded
> without actual hardware.

Use an emulator such as QEMU! It might not be suitable for all kinds
of kernel development, but it is very useful to catch high level bugs.
Use it to test the your embedded distribution with different amounts
of RAM,  use it to test serial consoles etc. I will never leave home
without it.

/ magnus

Re: Contribute - How to

[Tim Hockin]

On Thu, Dec 02, 2004 at 08:39:32PM -0800, 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.

Find something broken and fix it.  A good place to start is the kernel
janitor project.  There is a ton of code that needs to be cleaned up.

Re: Contribute - How to

[Zwane Mwaikambo]

On Fri, 3 Dec 2004, Tim Hockin wrote:

> On Thu, Dec 02, 2004 at 08:39:32PM -0800, 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.
> 
> Find something broken and fix it.  A good place to start is the kernel
> janitor project.  There is a ton of code that needs to be cleaned up.

Hey we could also use some more bodies on bugzilla.kernel.org =)

Re: Contribute - How to

[Bill Davidsen]

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