kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: sarah.a.sharp@linux.intel.com (Sarah Sharp)
To: kernelnewbies@lists.kernelnewbies.org
Subject: New member queries..
Date: Mon, 22 Oct 2012 11:59:17 -0700	[thread overview]
Message-ID: <20121022185917.GC19999@xanatos> (raw)
In-Reply-To: <506E9063.7010802@gmail.com>

On Fri, Oct 05, 2012 at 01:16:43PM +0530, shampavman.cg wrote:
> Hi Guys,
> 
> I'm new to linux kernel development (only a few hrs old i may say). I've 
> been working with the solaris kernel from the past year and now would 
> like to concentrate on linux as well.
> "My area of expertise is Filesystems".
> 
> Here are a few things i would like to know from you guys.
> 1.) I've looked at the bugzilla pages, how do i choose a bite sized bug 
> to start with? (Is there such a concept at all?)

Not really.  Most Linux kernel developers don't keep track of their
byte-sized bugs in bugzilla.  Most just keep them in their heads and
don't have time to share.

> 2.) I looked at kernelJanitors page as well hoping to find info but 
> nothing much there .
> 
> Can anyone help me get started?

You might try joining the various filesystem mailing lists and watching
the traffic to see where the current areas of work are:

http://vger.kernel.org/vger-lists.html

For example, I see the lists ecryptfs, linux-btrfs, linux-cifs,
linux-fsdevel, linux-nfs, linux-xfs, and linux-ext4.

I would suggest working on either ext4 or btrfs.  B-tree FS (or btrfs)
is one of the newer filesystems, and it needs a lot more work than, say,
nfs.  Ted T'so is the maintainer for ext4, and Chris Mason is the
maintainer for btrfs.  Emailing them to find out what tasks need to be
done would be a good start.

Sarah Sharp

  reply	other threads:[~2012-10-22 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05  7:46 New member queries shampavman.cg
2012-10-22 18:59 ` Sarah Sharp [this message]
2012-10-22 21:25   ` Greg Freemyer
2012-10-23  3:55     ` Dave Hellewell

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=20121022185917.GC19999@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).