Hey all, The vPTG will be upon us soon, the week of March 27. I booked the following times on behalf of Ironic + BM SIG Operator hour, in accordance with what times worked in Antelope. It's my hope that since we've had little contributor turnover, these times continue to work. I'm completely open to having things moved around if it's more convenient to participants. I've booked the following times, all in Folsom: - Tuesday 1400 UTC - 1700 UTC - Wednesday 1300 UTC Operator hour: baremetal SIG - Wednesday 1400 UTC - 1600 UTC - Wednesday 2200 - 2300 UTC I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time. Again, this is all meant to be a suggestion, I'm happy to move things around but didn't want us to miss out on getting things booked. - Jay Faulkner Ironic PTL TC Member
Greetings! Time slot wise, I think that works for me. Time wise, in regards to the amount, I'm wondering if we need more. By my count, we have 11 new topics, 4 topics to revisit, in about six hours of non-operator dedicated time, not accounting for breaks for coffee/tea. Granted, some topics might be super quick at the 10 minute quick poll of the room, whereas other topics I feel like will require extensive discussion. If I were to size them, I think we would have 6 large-ish topics along with 3-4 medium sized topics. -Julia On Thu, Mar 9, 2023 at 3:19 PM Jay Faulkner <jay@gr-oss.io> wrote:
Hey all,
The vPTG will be upon us soon, the week of March 27.
I booked the following times on behalf of Ironic + BM SIG Operator hour, in accordance with what times worked in Antelope. It's my hope that since we've had little contributor turnover, these times continue to work. I'm completely open to having things moved around if it's more convenient to participants.
I've booked the following times, all in Folsom: - Tuesday 1400 UTC - 1700 UTC - Wednesday 1300 UTC Operator hour: baremetal SIG - Wednesday 1400 UTC - 1600 UTC - Wednesday 2200 - 2300 UTC
I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time.
Again, this is all meant to be a suggestion, I'm happy to move things around but didn't want us to miss out on getting things booked.
- Jay Faulkner Ironic PTL TC Member
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 On Mon, Mar 13, 2023 at 11:43 AM Julia Kreger <juliaashleykreger@gmail.com> wrote:
Greetings!
Time slot wise, I think that works for me.
Time wise, in regards to the amount, I'm wondering if we need more. By my count, we have 11 new topics, 4 topics to revisit, in about six hours of non-operator dedicated time, not accounting for breaks for coffee/tea. Granted, some topics might be super quick at the 10 minute quick poll of the room, whereas other topics I feel like will require extensive discussion. If I were to size them, I think we would have 6 large-ish topics along with 3-4 medium sized topics.
-Julia
On Thu, Mar 9, 2023 at 3:19 PM Jay Faulkner <jay@gr-oss.io> wrote:
Hey all,
The vPTG will be upon us soon, the week of March 27.
I booked the following times on behalf of Ironic + BM SIG Operator hour, in accordance with what times worked in Antelope. It's my hope that since we've had little contributor turnover, these times continue to work. I'm completely open to having things moved around if it's more convenient to participants.
I've booked the following times, all in Folsom: - Tuesday 1400 UTC - 1700 UTC - Wednesday 1300 UTC Operator hour: baremetal SIG - Wednesday 1400 UTC - 1600 UTC - Wednesday 2200 - 2300 UTC
I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad ( https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time.
Again, this is all meant to be a suggestion, I'm happy to move things around but didn't want us to miss out on getting things booked.
- Jay Faulkner Ironic PTL TC Member
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@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]
That sync is exactly what I hoped
I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time. ^ that would be. Does that sound good to you? If it comes out in there we need more time, we should also have interested parties around to book it. -Jay On Tue, Mar 14, 2023 at 2:41 PM Julia Kreger <juliaashleykreger@gmail.com> wrote:
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@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]
Sounds good to me! Thanks! -Julia On Tue, Mar 14, 2023 at 2:54 PM Jay Faulkner <jay@gr-oss.io> wrote:
That sync is exactly what I hoped
I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time.
^ that would be.
Does that sound good to you? If it comes out in there we need more time, we should also have interested parties around to book it.
-Jay
On Tue, Mar 14, 2023 at 2:41 PM Julia Kreger <juliaashleykreger@gmail.com> wrote:
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@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]
Hey all, Based on the results of our quick vPTG sync this morning, I've done the following: * I booked one additional slot for Ironic; Wednesday 1600 UTC - 1700 UTC, to ensure we'd have plenty of discussion time once accounting for breaks that we'll certainly need. * I've tentatively scheduled all topics here: https://etherpad.opendev.org/p/ironic-bobcat-ptg -- please review, if there's anything that creates a hardship lets work it out, in the the etherpad, IRC, or on the mail list :). Thanks, looking forward to planning another release of Ironic with you all! -Jay On Thu, Mar 9, 2023 at 3:15 PM Jay Faulkner <jay@gr-oss.io> wrote:
Hey all,
The vPTG will be upon us soon, the week of March 27.
I booked the following times on behalf of Ironic + BM SIG Operator hour, in accordance with what times worked in Antelope. It's my hope that since we've had little contributor turnover, these times continue to work. I'm completely open to having things moved around if it's more convenient to participants.
I've booked the following times, all in Folsom: - Tuesday 1400 UTC - 1700 UTC - Wednesday 1300 UTC Operator hour: baremetal SIG - Wednesday 1400 UTC - 1600 UTC - Wednesday 2200 - 2300 UTC
I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time.
Again, this is all meant to be a suggestion, I'm happy to move things around but didn't want us to miss out on getting things booked.
- Jay Faulkner Ironic PTL TC Member
participants (2)
-
Jay Faulkner
-
Julia Kreger