From: Chris Mason <chris.mason@oracle.com>
To: Spyros Lyberis <lyberis@csd.uoc.gr>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Way to contribute?
Date: Fri, 19 Dec 2008 11:08:13 -0500 [thread overview]
Message-ID: <1229702893.6695.14.camel@think.oraclecorp.com> (raw)
In-Reply-To: <loom.20081219T130706-90@post.gmane.org>
On Fri, 2008-12-19 at 13:20 +0000, Spyros Lyberis wrote:
> Hi,
>
> I heard of the btrfs development and I'd like to know how can I contribute to
> the project. My apologies if this is the wrong place to post, but I couldn't
> find any contribution-related information in the wiki or elsewhere.
>
> I am a 30-yr old experienced hardware design engineer, who currently works as a
> software development lead for an Electronic Design Automation software startup.
> I'm experienced in straight C development (over 12 years), algorithmic
> development as well as lower level programming (e.g. I have programmed device
> registers, implemented an I2C controller for linux parallel port, built a simple
> MIDI sound card device driver for x86 Solaris back in 98, etc).
>
> I heavily use the linux raid for almost all my workstations and servers for
> years now, and having had some bad experiences I'm very interested in the
> integrated approach that btrfs is taking.
Btrfs is a fairly complex project, and so it is best to start small.
The first thing to do is give btrfs a try and look for bugs ;) Feel
free to ask questions here or on irc about how the code works.
Reading it is a great start, as it trying your workloads and seeing how
well it works.
-chris
prev parent reply other threads:[~2008-12-19 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 13:20 Way to contribute? Spyros Lyberis
2008-12-19 16:08 ` Chris Mason [this message]
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=1229702893.6695.14.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lyberis@csd.uoc.gr \
/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