From: Loic Dachary <loic@dachary.org>
To: Cheng Cheng <ccheng.leo@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: Seeking for Mentor
Date: Thu, 04 Sep 2014 22:33:40 +0200 [thread overview]
Message-ID: <5408CCA4.4060301@dachary.org> (raw)
In-Reply-To: <CAC13JXaE0H8xh2rX2c+-x-c0jUGV+nKMuoG3Kg+8ZKj-TKTsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
I'd be happy to help. Would you like to start with a chat on irc.oftc.net#ceph ? My nick is loicd.
On 04/09/2014 22:02, Cheng Cheng wrote:
> Hi Ceph Developers,
>
> I am just starting to use Ceph and find it is a great platform for
> hosting VM storage.
>
> As I want to dive further and learn more about Ceph, I want to take a
> starter task to familiarize myself with Ceph codebase. In particular,
> I found this copy-on-read is an interesting task
> (https://wiki.ceph.com/Planning/Sideboard/rbd%3A_copy-on-read_for_clones).
>
> However I find it is hard to get my hands dirty without mentorship. So
> I am wondering can anyone give me some bootstrap about how to
> contribute to Ceph and how to setup developing environment?
>
> Any help would be greatly appreciated!
>
> Sincerely,
> Cheng
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-09-04 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 20:02 Seeking for Mentor Cheng Cheng
2014-09-04 20:33 ` Loic Dachary [this message]
2014-09-05 3:10 ` About the copy-on-read blueprint Li Wang
2014-09-05 3:50 ` Cheng Cheng
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=5408CCA4.4060301@dachary.org \
--to=loic@dachary.org \
--cc=ccheng.leo@gmail.com \
--cc=ceph-devel@vger.kernel.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.