All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Vaz <lvaz@redhat.com>
To: Ceph Users <ceph-users@ceph.com>,
	Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Ceph Developer Monthly - January 2018
Date: Wed, 3 Jan 2018 01:38:24 -0200	[thread overview]
Message-ID: <20180103033824.GA23444@t460.local> (raw)

Hey Cephers,

This is just a friendly reminder that the next Ceph Developer Montly
meeting is coming up:

 http://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_03-JAN-2018

This edition happens on APAC friendly hours (21:00 EST) and we will
use the following Bluejeans URL for the video conference:

 https://bluejeans.com/9290089010/

If you have questions or comments, please let us know.

Kindest regards,

Leo

-- 
Leonardo Vaz
Ceph Community Manager
Open Source and Standards Team

             reply	other threads:[~2018-01-03  3:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03  3:38 Leonardo Vaz [this message]
2018-01-04 11:20 ` Ceph Developer Monthly - January 2018 Leonardo Vaz

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=20180103033824.GA23444@t460.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.