Open Stack

I totally understand the concern.

I don't know if I have stressed it before, but team photos are 100%
optional. If its going to be too much of a distraction for anyone's team,
they definitely don't need to sign up.

The plan is to meet at reg, walk to the field entrance where the escort
will take us onto the pitch, take the photo and go back. It won't be like
this next time either, we just wanted to try to take advantage of what the
location has to offer.

-Kendall (diablo_rojo)

On Thu, Feb 15, 2018 at 2:11 PM Sean McGinnis <sean.mcginnis at gmail.com>
wrote:

> On Thu, Feb 15, 2018 at 3:56 PM, Kendall Nelson <kennelson11 at gmail.com>
> wrote:
>
>> Updates!
>>
>> So, we have gotten permission to do photos down on the pitch at the
>> stadium which is awesome!
>>
>> The only issue is that we need to condense into a more dense blocks
>> (Tuesday afternoon or Thursday morning) so looking at the schedule we have
>> to move some teams. If the following teams could move their times so that
>> we can make this happen:
>>
>>    - QA
>>    - SIG K8s
>>    - Cyborg
>>    - Neutron
>>    - Octavia
>>    - Requirements
>>    - Release Mgmt
>>    - OpenStack Ansible
>>    - Cinder
>>
>> I'm really sorry to make you guys move, but since we need to pay for an
>> escort (with a 4 hour minimum) and don't want to conflict with lunch, we
>> need to shift.
>>
>>
> That sounds fun, but should we really do this?
>
> At past PTG's, it was a disruption for teams to put things on hold to
> quick run down a couple floors to take a photo. I think it is worth the
> brief disruption - something like this is definitely worthy of taking the
> time to have a photo of the team.
>
> But in those cases it was quick and fairly easy to context switch back to
> what had been the topic before the break. Now, if we are going to need to
> leave the building, wait for the photo, then walk back to the in to the
> venue, that seems like it's going to be a longer disruption that would be a
> bigger context switch and require more time to remember where things were
> before the break.
>
> I'm fine doing it either way, but I have some concerns about how big of a
> disruption this could now be.
>
> Sean
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180216/21a59526/attachment.html>