[openstack-dev] [kolla][ptg] Denver PTG on-site or virtual

Adam Harwell flux.adam at gmail.com
Fri Aug 17 11:54:15 UTC 2018


As one of the other two in the etherpad, I will say that I was looking
forward to getting together face to face with other contributors for the
first time (as I am new to the project), but I guess the majority won't
actually be there, and I understand that we need to do what is best for the
majority as well.
I know that at least one or maybe two other people from my team were also
planning to attend some Kolla sessions, so I'll see if I can get them to
sign up.
The other projects I'll be focused on are Octavia and Barbican, and I know
both have been successful with a hybrid approach in the past (providing
video of the room and allowing folks to dial in and contribute, while also
having a number of people present physically).
Since the room is already reserved, I don't see a huge point in avoiding
its use either.

   --Adam

On Fri, Aug 17, 2018, 20:27 Mark Goddard <mark at stackhpc.com> wrote:

> As one of the lucky three kolleagues able to make the PTG, here's my
> position (inline).
>
> On 17 August 2018 at 11:52, Eduardo Gonzalez <dabarren at gmail.com> wrote:
>
>> Fellow kolleages.
>>
>> In september is Denver PTG, as per the etherpad [0] only 3 contributors
>> confirmed their presence in the PTG, we expected more people to be there as
>> previous PTGs were full of contributors and operators.
>>
>> In the last kolla meeting [1] with discussed if we should make a virtual
>> PTG rather than a on-site one as we will probably reach a bigger number of
>> attendance.
>>
>> This set us in a bad possition as per:
>>
>> If we do an on-site PTG
>>
>> - Small representation for a whole cycle design, being this one larger
>> than usual.
>> - Many people whiling to attend is not able to be there.
>>
>
> I agree that three is too small a number to justify an on-site PTG. I was
> planning to split my time between kolla and ironic, so being able to focus
> on one project would be beneficial to me, assuming the virtual PTG takes
> place at a different time. I could still split my time if the virtual PTG
> occurs at the same time.
>
>
>>
>> If we do a virtual PTG
>>
>> - Some people already spend money to travel for kolla PTG
>>
>
> I would be going anyway.
>
>
>> - PTG rooms are already reserved for kolla session
>>
>
> If the virtual PTG occurs at the same time, we could use the (oversized)
> reserved room to dial into calls.
>
> - No cross project discussion
>>
>
> Happy to attend on behalf of kolla and feed back to the team.
>
>>
>> If there are more people who is going to Denver and haven't signed up at
>> the etherpad, please confirm your presence as it will probably influence on
>> this topic.
>>
>> Here is the though question...
>>
>> What kind of PTG do you prefer for this one, virtual or on-site in Denver?
>>
>
> Virtual makes sense to me.
>
>>
>> CC to Kendall Nelson from the foundation if she could help us on this
>> though decission, given the small time we have until the PTG both ways have
>> some kind of bad consecuencies for both the project and the contributors.
>>
>> [0] https://etherpad.openstack.org/p/kolla-stein-ptg-planning
>> [1]
>> http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-08-15-15.00.log.html#l-13
>>
>> Regards
>>
>> __________________________________________________________________________
>> 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
>>
>>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180817/68498850/attachment.html>


More information about the OpenStack-dev mailing list