Open Stack

Mark,

Thank you for chasing this down.. Using the same mediums as the rest of the openstack community will be a great help and hopefully will increase attendance!

Thanks,
Shep
On Jun 2, 2015, at 7:33 PM, Mark Voelker <mvoelker at vmware.com<mailto:mvoelker at vmware.com>> wrote:

Tony Breeds from the infra team just pointed out that since we’re doing the 15:00 UTC meeting on odd-numbered weeks, we’ll actually avoid a perceived conflict with some other meetings on the official meeting channels that meet during that time.  That means we can actually host both the 01:00 UTC Thursday (even weeks) and 15:00 UTC Wednesday (odd weeks) on #openstack-meeting-4 without any conflicts!  Hosting on an official channel means we we’ll hopefully make life easier for folks who attend other OpenStack meetings (which is probably most of us) and we can take advantage of meetbot, so this is a Good Thing.

Egle: could you please update the calendar invite you sent for tomorrow to use #openstack-meeting-4?  In case anyone shows up on #openstack-defcore we’ll have someone hanging around to redirect you just in case (hi!).  I’ve also sent in a patch [1] to infra to get the official meeting page [2] updated and I’ll clean up the now-obsolete [3] meeting wiki page [4] once everything lands.

[1] https://review.openstack.org/#/c/187821/
[2] http://eavesdrop.openstack.org/
[3] http://lists.openstack.org/pipermail/openstack-dev/2015-May/064873.html
[4] https://wiki.openstack.org/wiki/Meetings

At Your Service,

Mark T. Voelker
OpenStack Architect
+1 (970) 203-4974

On Jun 2, 2015, at 1:24 PM, Mark Voelker <mvoelker at vmware.com<mailto:mvoelker at vmware.com>> wrote:

Hi Folks,

I’ve added some notes to the ether pad for Flag.2 on the rationale for the new meeting times:

https://etherpad.openstack.org/p/DefCoreFlag.2

Basically the plan is to combine the process/capabilities meetings, do them on IRC, and hold them on an alternate-week schedule that will hopefully be reasonably friendly for our global respondents.  I’ve included links to the survey data there as well for those who are curious.  We’ll try out this new meeting structure for roughly a month and then pause at the July 8th meeting to discuss if it’s working out or if we need to reconsider.

At Your Service,

Mark T. Voelker
OpenStack Architect
+1 (970) 203-4974

On Jun 2, 2015, at 12:48 PM, Egle Sigler <egle.sigler at rackspace.com> wrote:

Hello Everyone,

Thanks to everyone that filled out the time surveys and provided feedback on IRC/phone meetings. For now, we will try IRC meetings, alternating weeks at different times.

Odd week, starting tomorrow: 15:00 UTC or 10 AM CST
Even week, starting next week: 01:00 UTC or 8 PM CST

Etherpad: https://etherpad.openstack.org/p/DefCoreFlag.2

Info on OpenStack IRC: https://wiki.openstack.org/wiki/IRC
Web IRC link if you are not using IRC client: https://urldefense.proofpoint.com/v2/url?u=http-3A__webchat.freenode.net_-3Fchannels-3Dopenstack-2Ddefcore&d=BQIF-g&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Q8IhPU-EIzbG5YDx5LYO7zEJpGZykn7RwFg-UTPWvDc&m=ma8vFSju4evkK_AlL9xsmo5vstzVFA6mf1NbZs3SEU4&s=8rJV_jTvRGUIeTff91H_eP2bYafqNG0lOvM6zXrqQUI&e=

Thank you,
Egle
_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20150603/9bcb3682/attachment-0001.html>