CEPH filesystem development
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Li Wang <liwang@ubuntukylin.com>
Cc: Patrick McGarry <patrick@inktank.com>,
	Wido den Hollander <wido@42on.com>,
	Loic Dachary <loic@dachary.org>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	Sage Weil <sage@inktank.com>,
	Justin Erenkrantz <justin@erenkrantz.com>
Subject: Re: What should the Ceph Foundation be about ?
Date: Tue, 6 May 2014 17:49:11 -0400 (EDT)	[thread overview]
Message-ID: <1010129935.191.1399412951552.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <217643357.189.1399412810326.JavaMail.root@thunderbeast.private.linuxbox.com>

Hi,

Is there a known time at the Summit when this discussion might be taking place?
I have limited time window during which I could be present, but would make an
effort to do so.  I'm mostly interested in listening in, but have some useful context (OpenAFS foundation, not a board member).

Regards,

Matt

----- "Li Wang" <liwang@ubuntukylin.com> wrote:

> On 2014/5/6 11:54, Sage Weil wrote:
> > On Mon, 5 May 2014, Justin Erenkrantz wrote:
> >> On Thu, May 1, 2014 at 12:32 PM, Patrick McGarry
> <patrick@inktank.com> wrote:
> >>> People like Jim Jagielski, Brian Stevens, Michael Tiemann, and
> many
> >>> others are bound to have years of experience that can help us make
> the
> >>> best decisions for the Ceph community.  I'm really looking forward
> to
> >>> exploring this topic with them as they have been very welcoming
> so
> >>> far.
> >> Given our backgrounds, I'm sure that my advice will be similar to
> >> Jim's; but, I'm happy to act as a sounding board as someone who
> has
> >> been an advocate for Ceph for a while now.  =)
> >>
> >> I'll be in Atlanta next week for the OpenStack Summit - happy to
> >> discuss this over drinks if you or anyone else will be there!  --
> > Excellent-- I look forward to seeing you there!
> I will be there as well, see you then
> >
> > sage
> > --
> > 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
> 
> --
> 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

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

       reply	other threads:[~2014-05-06 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <217643357.189.1399412810326.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-05-06 21:49 ` Matt W. Benjamin [this message]
2014-05-01 14:35 What should the Ceph Foundation be about ? Loic Dachary
2014-05-01 14:44 ` Wido den Hollander
2014-05-01 16:32   ` Patrick McGarry
2014-05-06  3:35     ` Justin Erenkrantz
2014-05-06  3:54       ` Sage Weil
2014-05-06  7:03         ` Li Wang
2014-05-06  7:11           ` Loic Dachary

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=1010129935.191.1399412951552.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=justin@erenkrantz.com \
    --cc=liwang@ubuntukylin.com \
    --cc=loic@dachary.org \
    --cc=patrick@inktank.com \
    --cc=sage@inktank.com \
    --cc=wido@42on.com \
    /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