From: Brad Hubbard <bhubbard@redhat.com>
To: Mark Nelson <mnelson@redhat.com>
Cc: "Piotr Dałek" <branch@predictor.org.pl>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Weekly performance meeting APAC time?
Date: Wed, 18 May 2016 21:37:36 -0400 (EDT) [thread overview]
Message-ID: <104170944.77164509.1463621856704.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <09a57ed5-d9b4-d599-ddd3-a3b3496dd9c5@redhat.com>
----- Original Message -----
> From: "Mark Nelson" <mnelson@redhat.com>
> To: "Piotr Dałek" <branch@predictor.org.pl>
> Cc: "ceph-devel" <ceph-devel@vger.kernel.org>
> Sent: Thursday, 19 May, 2016 7:18:14 AM
> Subject: Re: Weekly performance meeting APAC time?
>
> On 05/18/2016 02:08 PM, Piotr Dałek wrote:
> > On Wed, May 18, 2016 at 11:41:36AM -0500, Mark Nelson wrote:
> >> Josh mentioned at today's performance meeting that the current
> >> 8:00AM PST time is inconvenient for some folks he's talked with that
> >> live in the APAC region who would like to attend. I'd like to find
> >> out how many other folks feel this way as well? Would folks be
> >> interested in staggering the meeting every other week with something
> >> like a 6:00PM PST (9:00AM Beijing) next day) time?
> >
> > This means 3:00 AM for everyone in CET and 2:00 AM in GMT... Well,
> > cant't satisfy everyone I guess.
> >
>
> Yeah, that's what I'm concerned about. Even if we did it, it would only
> be every other week. First I want to see how many people respond saying
> they would even like this change though.
I was actually the driver behind this I think. Primarily I just wanted to
discuss a project I'm working on and get some feedback from the perf team. The
regular scheduled meeting is at 0100 my time so I raised that as a bit of an
issue (soft, I know :) ). I think any modification to the meeting time though
needs to be proportional so maybe 1 in 4 is more appropriate? I guess it
depends on the level of interest here in the APAC region which you are trying
to gauge. For me this is probably more of a one off than an ongoing commitment
to attending the meeting.
While we are at it I noticed that http://pad.ceph.com/p/performance_weekly
does not seem to include any recordings from this year although each meeting
entry says "See recording...". Are these archived somewhere else or maybe the
dates are incorrect?
Cheers,
Brad
>
> Mark
> --
> 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
next prev parent reply other threads:[~2016-05-19 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:41 Weekly performance meeting APAC time? Mark Nelson
2016-05-18 19:08 ` Piotr Dałek
2016-05-18 21:18 ` Mark Nelson
2016-05-18 21:56 ` Shinobu Kinjo
2016-05-19 0:36 ` Xinze Chi (信泽)
2016-05-19 1:37 ` Brad Hubbard [this message]
2016-05-19 2:01 ` Mark Nelson
2016-05-19 6:16 ` Piotr Dałek
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=104170944.77164509.1463621856704.JavaMail.zimbra@redhat.com \
--to=bhubbard@redhat.com \
--cc=branch@predictor.org.pl \
--cc=ceph-devel@vger.kernel.org \
--cc=mnelson@redhat.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.