Open Stack

I think there is a bit of a challenge to navigate though in that the PTG as
a sync point is needed especially on items which may take more than just
one cycle to deliver. A great example is driver composition. The other
unknown is if people are just not interested in some topics, which can
result in that topic being very quick.

One thing we also did in the past is guess how much time as a group in
advance. I know for a few cycles we had a quick 15 minute call to discuss
sizing.  Based upon output from that, I think we could adjust the time
slots accordingly. Maybe that might make sense to do?

-Julia

On Tue, Mar 14, 2023 at 2:08 PM Jay Faulkner <jay at gr-oss.io> wrote:

> I'm not opposed to adding more time necessarily, but I wonder if the
> solution is to triage what we talk about better.
>
> Last PTG, we planned several features which we didn't have enough
> contribution to complete. IMO, it might be better to limit what we discuss
> to things that are likely to be accomplished next cycle. If we can't
> determine that without more discussion, then sure, let's add vPTG sessions..
>
> Is there a suggestion as to specifically what times, and how much to add?
>
> Thanks,
> Jay Faulkner
>
>> [trim]
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230314/3776e554/attachment.htm>