On 12/16/2015 4:50 PM, Ian Cordasco wrote:


On 12/16/15, 16:41, "Tony Breeds" <[email protected]> wrote:

On Wed, Dec 16, 2015 at 01:12:13PM -0600, Matt Riedemann wrote:
I'm not entirely sure what the geo distribution is for everyone that
works
on stable, but I know we have people in Europe and some people in
Australia.
So I was thinking alternating weekly meetings:

Mondays at 2100 UTC

Tuesdays at 1500 UTC

Does that at least sort of work for people that would be interested in
attending a meeting about stable? I wouldn't expect a full hour
discussion,
my main interests are highlighting status, discussing any issues that
come
up in the ML or throughout the week, and whatever else people want to go
over (work items, questions, process discussion, etc).

The Monday meeting works for me :)

Yours Tony.

I'm not a stable team member, but I'm intrigued and I'll definitely join
all of you, at least to lurk. :)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


The more the merrier.

The proposed meeting schedule was approved so we have this:

http://eavesdrop.openstack.org/#Stable_Team_Meeting

Now I guess the question is if anyone wants to meet next week (Tuesday 12/22 at 1500 UTC)?

I'm working Monday and Tuesday next week and then I'm out for the rest of the year, so I'm fine with skipping an initial meeting before a long break and I'm assuming most other people are too. If anyone feels otherwise and really wants to meet next Tuesday, let me know and I'll get an agenda put together. Otherwise I'll plan for the first meeting in early January.

--

Thanks,

Matt Riedemann


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to