All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prakash Surya <surya1@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Interested in contributing to Lustre
Date: Mon, 13 May 2013 14:34:54 -0700	[thread overview]
Message-ID: <20130513213454.GF7378@llnl.gov> (raw)
In-Reply-To: <5a77f40fe7860376e5bcdfaeb8e6cb7a.squirrel@webmail.andrew.cmu.edu>

I wish you luck in your endeavour!

Here are some links which might prove useful to you:

 * https://jira.hpdd.intel.com - New issues are opened here

 * http://review.whamcloud.com - New patches are reviewed here

 * https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes - Some
   info on the development cycle used by the Lustre project.

Unfortunately, there isn't nearly enough documentation as there should
be in the Lustre tree (especially for new comers), so feel free to ask
questions.

As far as potential projects, in my opinion, the project list you
linked to is a bit dated. There are *many* open issues which need to be
fixed, so I would suggest finding something that interests you on the
JIRA bug tracker that I linked to above, since that is a more up to date
source of information.

If you are completely new, a good place to start is just downloading the
git tree, building, and running the unit tests locally to get familiar
with the project. Then you can start to modify the source and explore
some of the areas that interest you.

-- 
Cheers, Prakash

On Fri, May 10, 2013 at 06:03:27PM -0400, twanjari at andrew.cmu.edu wrote:
> Hi all,
> 
> I am a grad student at Carnegie Mellon University. I had my course work in
> advanced storage systems in previous semester, and I am interested to work
> on Lustre. I prefer to take up a project that could be completed in a
> duration of a month or two.
> 
> Since I am a novice w.r.t. my familiarity with Lustre code base, I seek
> your opinion to choose a project from the list:
> http://wiki.lustre.org/index.php/Lustre_Project_List
> 
> My preferences (in order) are:
> 1. fallocate() API - https://bugzilla.lustre.org/show_bug.cgi?id=15064
> 2. kernel patch removal - https://bugzilla.lustre.org/show_bug.cgi?id=21524
> 3. ioctl() number cleanups -
> https://bugzilla.lustre.org/show_bug.cgi?id=20731
> I am also open to other suggestion.
> 
> Any suggestions regarding code walkthrough or documentation to help
> ramping up are also welcome.
> 
> Thanks,
> Tejas Wanjari
> 
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel

  reply	other threads:[~2013-05-13 21:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 22:03 [Lustre-devel] Interested in contributing to Lustre twanjari at andrew.cmu.edu
2013-05-13 21:34 ` Prakash Surya [this message]
2013-05-14  6:49   ` Drokin, Oleg
2013-05-14 14:58     ` Cory Spitz
2013-05-14 15:23       ` Nikitas Angelinas
2013-05-21 14:08     ` [Lustre-devel] building the 'lustre kernel' Ron Croonenberg
2013-05-21 14:11     ` [Lustre-devel] lustre kernel configuration Ron Croonenberg
2013-05-21 18:16       ` Christopher J. Morrone
2013-05-21 19:04         ` Ron Croonenberg
2013-05-21 19:24           ` Cory Spitz
2013-05-21 19:36             ` Ron Croonenberg
2013-05-14  0:55 ` [Lustre-devel] Interested in contributing to Lustre Dilger, Andreas
2013-05-14 14:07 ` Cory Spitz

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=20130513213454.GF7378@llnl.gov \
    --to=surya1@llnl.gov \
    --cc=lustre-devel@lists.lustre.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 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.