Open Stack

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.

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).

Tim

-----Original Message-----
From: Doug Hellmann <doug at doughellmann.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Thursday, 8 March 2018 at 20:00
To: openstack-dev <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] Pros and Cons of face-to-face meetings

    Excerpts from Jeremy Stanley's message of 2018-03-08 18:34:51 +0000:
    > On 2018-03-08 12:16:18 -0600 (-0600), Jay S Bryant wrote:
    > [...]
    > > Cinder has been doing this for many years and it has worked
    > > relatively well. It requires a good remote speaker and it also
    > > requires the people in the room to be sensitive to the needs of
    > > those who are remote. I.E. planning topics at a time appropriate
    > > for the remote attendees, ensuring everyone speaks up, etc. If
    > > everyone, however, works to be inclusive with remote participants
    > > it works well.
    > > 
    > > We have even managed to make this work between separate mid-cycles
    > > (Cinder and Nova) in the past before we did PTGs.
    > [...]
    > 
    > I've seen it work okay when the number of remote participants is
    > small and all are relatively known to the in-person participants.
    > Even so, bridging Doug into the TC discussion at the PTG was
    > challenging for all participants.
    
    I agree, and I'll point out I was just across town (snowed in at a
    different hotel).
    
    The conversation the previous day with just the 5-6 people on the
    release team worked a little bit better, but was still challenging
    at times because of audio quality issues.
    
    So, yes, this can be made to work. It's not trivial, though, and
    the degree to which it works depends a lot on the participants on
    both sides of the connection. I would not expect us to be very
    productive with a large number of people trying to be active in the
    conversation remotely.
    
    Doug
    
    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev