From: Leonardo Vaz <lvaz@redhat.com>
To: Ceph-Users <ceph-users@ceph.com>,
Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Ceph Developers Monthly - August
Date: Tue, 1 Aug 2017 23:43:56 -0300 [thread overview]
Message-ID: <20170802024356.GB2568@oops.local> (raw)
In-Reply-To: <20170727050859.GA15435@oops.local>
On Thu, Jul 27, 2017 at 02:08:59AM -0300, Leonardo Vaz wrote:
> Hey Cephers,
>
> This is just a friendly reminder that the next Ceph Developer Montly
> meeting is coming up:
>
> https://wiki.ceph.com/Planning
>
> If you have work that you're doing that it a feature work, significant
> backports, or anything you would like to discuss with the core team,
> please add it to the following page:
>
> https://wiki.ceph.com/CDM_02-AUG-2017
>
> If you have questions or comments, please let us know.
This is another reminder, the Ceph Developer Monthly is confirmed for
this Wednesday, August 2 at 12:30-2:30pm on Eastern Time (EDT).
We will use the following Bluejeans URL for the video conference:
https://bluejeans.com/707503600
Kindest regards,
Leo
--
Leonardo Vaz
Ceph Community Manager
Open Source and Standards Team
prev parent reply other threads:[~2017-08-02 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 5:08 Ceph Developers Monthly - August Leonardo Vaz
2017-08-02 2:43 ` 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=20170802024356.GB2568@oops.local \
--to=lvaz@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.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.