From: Leonardo Vaz <lvaz@redhat.com>
To: Webert de Souza Lima <webert.boss@gmail.com>
Cc: Patrick McGarry <pmcgarry@redhat.com>,
Ceph board <board@ceph.com>,
Ceph Devel <ceph-devel@vger.kernel.org>,
Ceph-User <ceph-users@ceph.com>
Subject: Re: [ceph-users] New Ceph Community Manager
Date: Sat, 22 Jul 2017 02:04:07 -0300 [thread overview]
Message-ID: <20170722050407.GA18285@oops.local> (raw)
In-Reply-To: <CAKtzvt9x4zfZ+b6160Q-MAwpZfJW7owmad8kvwq3BsWZ5Gt3SQ@mail.gmail.com>
On Fri, Jul 21, 2017 at 10:02:06PM -0300, Webert de Souza Lima wrote:
> Thank you for all your efforts, Patrick.
Patrick did a fantatic work all this years and I'd like to use this
opportunity to say that's an honor to serve the Ceph community. :)
> Parabéns e boa sorte Leo :)
Thanks Webert! I'm looking forward to work with you and everyone here.
Kindest regards,
Leo
> Regards,
>
> Webert Lima
> DevOps Engineer at MAV Tecnologia
> *Belo Horizonte - Brasil*
>
> On Thu, Jul 20, 2017 at 4:21 PM, Patrick McGarry <pmcgarry@redhat.com>
> wrote:
>
> > Hey cephers,
> >
> > As most of you know, my last day as the Ceph community lead is next
> > Wed (26 July). The good news is that we now have a replacement who
> > will be starting immediately!
> >
> > I would like to introduce you to Leo Vaz who, until recently, has been
> > working as a maintenance engineer with a focus on Ceph (and Gluster).
> > Leo also is a long time open source participant with efforts around
> > community organization and event management, helping to promote many
> > open source projects at places like FISL [0] and Latinoware [1]. Leo
> > is a founder and community manager of Tchelinux Free Software Users
> > group [2] and in 2009 became a Fedora Ambassador.
> >
> > Leo has a great mix of the “gritty, just-get-it-done” ethos needed in
> > a FOSS project as well as a great deal of professional drive and
> > experience. I’m sure he will be a fabulous addition to the public face
> > of Ceph, and I hope you all take the time to extend a warm welcome as
> > he starts getting settled.
> >
> > If you have any questions for me before 26 July, feel free to contact
> > me directly, otherwise I wish you all the best of luck and hope you
> > keep changing the world one Ceph install at a time!
> >
> >
> > [0] http://softwarelivre.org/fisl18
> > [1] http://latinoware.org/
> > [2] https://tchelinux.org/
> >
> >
> > --
> >
> > Best Regards,
> >
> > Patrick McGarry
> > Director Ceph Community || Red Hat
> > http://ceph.com || http://community.redhat.com
> > @scuttlemonkey || @ceph
> > _______________________________________________
> > ceph-users mailing list
> > ceph-users@lists.ceph.com
> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
--
Leonardo Vaz
Ceph Community Manager
Open Source and Standards Team
prev parent reply other threads:[~2017-07-22 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 19:21 New Ceph Community Manager Patrick McGarry
[not found] ` <CAAZbbf2-baruAhqwR=ph7MwGp2w9nKrrPCnuHdK=tv-rDBBEng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-22 1:02 ` Webert de Souza Lima
2017-07-22 5:04 ` Leonardo Vaz [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=20170722050407.GA18285@oops.local \
--to=lvaz@redhat.com \
--cc=board@ceph.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=pmcgarry@redhat.com \
--cc=webert.boss@gmail.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 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.