To simply answer the question:<br><br>Yes I have experience about this specific matter of things as I’m now working with the exact setup for more than 5 years. I’m even exclusively working remotely with some studios of my employer.<br><br>It’s not that expensive as long as you get correct rules, hardware and the stream owner physically on the room to act as a conductor.<br><br>Remember that the 4th mantra of the Openstack project HAVE to be respected if we really want to get people to join us and share. They need to feel at home in order to contribute as they have to feel useful to really be interested to participate. Additionally, Openstack being way more vast than let say Kubernetes it NEED such extra care in order to keep its community strong and passionate at a point where they will naturally advocate and work on it.<br><br>That’s indeed my first year of participating into the Openstack community even if I’m working on Openstack since the Essex version because I didn’t felt skilled and included enough until now.<br><br>Why did I change my mind? Because of the sidney summit and presentation of these Open rules plus my communication with you people over irc/emails etc.<br><div class="gmail_quote"><div dir="ltr">Le jeu. 8 mars 2018 à 21:06, Anita Kuno <<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2018-03-08 02:18 PM, Tim Bell wrote:<br>
> Fully agree with Doug. At CERN, we use video conferencing for 100s, sometimes >1000 participants for the LHC experiments, the trick we've found is to fully embrace the chat channels (so remote non-native English speakers can provide input) and chairs/vectors who can summarise the remote questions constructively, with appropriate priority.<br>
><br>
> This is actually very close to the etherpad approach, we benefit from the local bandwidth if available but do not exclude those who do not have it (or the language skills to do it in real time).<br>
<br>
Just expanding on the phrase 'the etherpad approach' one instance on the<br>
Friday saw some infra team members discussing the gerrit upgrade in<br>
person and one infra team member (snowed in at the same hotel as Doug)<br>
following along on the etherpad as it was updated and weighing in on the<br>
updates (either via the etherpad or irc, I'm not sure, my laptop was not<br>
open).<br>
<br>
So again echoing the chorus, there are possibilities, but those<br>
possibilities require effort and usually prior knowledge of participants<br>
and their habits.<br>
<br>
Thank you,<br>
Anita<br>
<br>
><br>
> Tim<br>
><br>
> -----Original Message-----<br>
> From: Doug Hellmann <<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>><br>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Date: Thursday, 8 March 2018 at 20:00<br>
> To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [openstack-dev] Pros and Cons of face-to-face meetings<br>
><br>
> Excerpts from Jeremy Stanley's message of 2018-03-08 18:34:51 +0000:<br>
> > On 2018-03-08 12:16:18 -0600 (-0600), Jay S Bryant wrote:<br>
> > [...]<br>
> > > Cinder has been doing this for many years and it has worked<br>
> > > relatively well. It requires a good remote speaker and it also<br>
> > > requires the people in the room to be sensitive to the needs of<br>
> > > those who are remote. I.E. planning topics at a time appropriate<br>
> > > for the remote attendees, ensuring everyone speaks up, etc. If<br>
> > > everyone, however, works to be inclusive with remote participants<br>
> > > it works well.<br>
> > ><br>
> > > We have even managed to make this work between separate mid-cycles<br>
> > > (Cinder and Nova) in the past before we did PTGs.<br>
> > [...]<br>
> ><br>
> > I've seen it work okay when the number of remote participants is<br>
> > small and all are relatively known to the in-person participants.<br>
> > Even so, bridging Doug into the TC discussion at the PTG was<br>
> > challenging for all participants.<br>
><br>
> I agree, and I'll point out I was just across town (snowed in at a<br>
> different hotel).<br>
><br>
> The conversation the previous day with just the 5-6 people on the<br>
> release team worked a little bit better, but was still challenging<br>
> at times because of audio quality issues.<br>
><br>
> So, yes, this can be made to work. It's not trivial, though, and<br>
> the degree to which it works depends a lot on the participants on<br>
> both sides of the connection. I would not expect us to be very<br>
> productive with a large number of people trying to be active in the<br>
> conversation remotely.<br>
><br>
> Doug<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>