[Openstack-operators] OPs Midcycle location discussion.
jlk at bluebox.net
Tue Nov 17 19:07:50 UTC 2015
Lets calm down the negative positioning here.
Matt offered his experience in trying what exists today. Others second it
(including me). That's not putting a stake in the ground and claiming "THOU
SHALT NOT PERMIT REMOTE PARTICIPATION". It's offering an opinion, which is
what the point of these threads are. Please have some respect for the
Nobody is saying we can't innovate. In fact, it was suggested to make it a
stretch goal. So... stretch. Try something. If it works, great, if not, be
prepared for it to not work, and don't derail the in-person activities to
try and make a trial work.
On Tue, Nov 17, 2015 at 10:45 AM, Erik McCormick <emccormick at cirrusseven.com
> On Tue, Nov 17, 2015 at 1:24 PM, Donald Talton <DonaldTalton at fico.com>
> > If only there we some kind of chat medium where people could listen in to
> > the live meetup and follow along in chat…
> > Seriously though, how hard is it to find/designate someone as an IRC
> > translator for the main points of discussion? Probably not ideal, but
> > than nothing. There has to be some solution we can find to increase
> > partipation from outside Europe.
> > Saying that we can add to an etherpad before the meetup starts is
> > exclusionary to everyone who would attend if not for distance. I know
> > conversely this applies to EU participants when we hold this in NA.
> > as technologists, can we not sort this out? It’s a simple problem,
> > considering the scope of everything else we do.
> We're deciding not to innovate a solution to allow people to
> participate in a group that is attempting to provide innovative ideas.
> How ironic. I actually don't think it would require much innovation.
> The Ceph guys run their entire design summit remotely, and I'm certain
> that it way beyond one or two people. If anyone has participated in
> that process, pointers would be welcome. If not, we can certainly post
> to their list and ask for suggestions. I imagine Sage might pipe up
> with some interesting thoughts at the very least.
> > From: tadowguy at gmail.com [mailto:tadowguy at gmail.com] On Behalf Of Matt
> > Fischer
> > Sent: Tuesday, November 17, 2015 10:48 AM
> > To: Donald Talton
> > Cc: Joe Topjian; Jonathan Proulx;
> openstack-operators at lists.openstack.org
> > Subject: Re: [Openstack-operators] OPs Midcycle location discussion.
> > On Mon, Nov 16, 2015 at 1:00 PM, Donald Talton <DonaldTalton at fico.com>
> > wrote:
> > I’ll +1 option 1 too, if we can get remote participation that would
> > Having been to several of these I think that we can call remote
> > participation a stretch goal at best, and if I'm being honest, I just
> > think it's going to be very feasible.
> > It's often times difficult enough to follow the conversation in a room
> > 100 people, some speaking without a mic; not sure how a remote person
> can be
> > expected to jump into that type of discussion. Perhaps different for
> > smaller, focused WGs sitting around a conference table would work for
> > remote participation? I think for main sessions the best you can hope
> for is
> > someone adding to the etherpad before the discussion (this is my plan for
> > the UK midcycle). Not physically being there also puts you at a timezone
> > disadvantage and for me it's sometimes difficult to connect from my "real
> > job".
> > We do these in-person because there's a benefit to being in-person and I
> > don't want to detract from that with conference lines etc.
> > This email and any files transmitted with it are confidential,
> > and intended solely for the individual or entity to whom they are
> > If you have received this email in error please delete it immediately.
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators