Upstream Oslo IRC Meetings Are Back.
Hello everyone, I hope you are all doing well! I sent an email a while ago to reestablish the Upstream Oslo IRC meetings. With the removal of Eventlet, this makes even more sense. I have received two positive responses, and we also mentioned it during the PTG last week. I propose to hold these meetings every other Monday, starting today, at 4:00 PM UTC. Does this work for everyone? Thank you for your feedback! -- Daniel Bengtsson Software engineer
LGTM, thanks Daniel. Le lun. 28 oct. 2024 à 13:25, Daniel Bengtsson <dbengt@redhat.com> a écrit :
Hello everyone,
I hope you are all doing well!
I sent an email a while ago to reestablish the Upstream Oslo IRC meetings. With the removal of Eventlet, this makes even more sense. I have received two positive responses, and we also mentioned it during the PTG last week.
I propose to hold these meetings every other Monday, starting today, at 4:00 PM UTC. Does this work for everyone?
Thank you for your feedback!
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
I assume the proposed time slot may work for the interested party so I'd not argue this strongly, but 16:00 UTC is 1:00 am in my tz. As I already have another too-late-meeting in a different day of week I may not guarantee my consistent attendance. On 10/28/24 10:17 PM, Herve Beraud wrote:
LGTM, thanks Daniel.
Le lun. 28 oct. 2024 à 13:25, Daniel Bengtsson <dbengt@redhat.com <mailto:dbengt@redhat.com>> a écrit :
Hello everyone,
I hope you are all doing well!
I sent an email a while ago to reestablish the Upstream Oslo IRC meetings. With the removal of Eventlet, this makes even more sense. I have received two positive responses, and we also mentioned it during the PTG last week.
I propose to hold these meetings every other Monday, starting today, at 4:00 PM UTC. Does this work for everyone?
Thank you for your feedback!
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
Thinking twice about your proposal... Concerning myself, the official meeting slots https://meetings.opendev.org/#Oslo_Team_Meeting which do not match anymore with my personal calendar. Still concerning myself, if we decide to go with 4pm UTC I won't be able to assist the whole meeting. Maybe choosing another day would best fit everyone? If we decide to change the hour, then, the meeting page should be updated ( https://meetings.opendev.org/#Oslo_Team_Meeting). Le lun. 28 oct. 2024 à 14:24, Takashi Kajinami <kajinamit@oss.nttdata.com> a écrit :
I assume the proposed time slot may work for the interested party so I'd not argue this strongly, but 16:00 UTC is 1:00 am in my tz. As I already have another too-late-meeting in a different day of week I may not guarantee my consistent attendance.
On 10/28/24 10:17 PM, Herve Beraud wrote:
LGTM, thanks Daniel.
Le lun. 28 oct. 2024 à 13:25, Daniel Bengtsson <dbengt@redhat.com <mailto:dbengt@redhat.com>> a écrit :
Hello everyone,
I hope you are all doing well!
I sent an email a while ago to reestablish the Upstream Oslo IRC meetings. With the removal of Eventlet, this makes even more sense. I have received two positive responses, and we also mentioned it during the PTG last week.
I propose to hold these meetings every other Monday, starting today, at 4:00 PM UTC. Does this work for everyone?
Thank you for your feedback!
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
On 2024-10-28 15:55, Herve Beraud wrote:
Thinking twice about your proposal... Concerning myself, the official meeting slots https:// meetings.opendev.org/#Oslo_Team_Meeting <https://meetings.opendev.org/ #Oslo_Team_Meeting> which do not match anymore with my personal calendar. Still concerning myself, if we decide to go with 4pm UTC I won't be able to assist the whole meeting. Maybe choosing another day would best fit everyone? What is the best time for you? We can do another time.
-- Daniel Bengtsson Software engineer
On 2024-10-28 15:55, Herve Beraud wrote:
If we decide to change the hour, then, the meeting page should be updated (https://meetings.opendev.org/#Oslo_Team_Meeting <https:// meetings.opendev.org/#Oslo_Team_Meeting>). Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
I don't think we can answer that question here. I'd encourage you to propose time slots and day and then to run a doodle vote on them. Le lun. 28 oct. 2024 à 17:22, Daniel Bengtsson <dbengt@redhat.com> a écrit :
On 2024-10-28 15:55, Herve Beraud wrote:
If we decide to change the hour, then, the meeting page should be updated (https://meetings.opendev.org/#Oslo_Team_Meeting <https:// meetings.opendev.org/#Oslo_Team_Meeting>). Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
+1 for using doodle vote to decide the slot. Just dumping my preference here for your refernce but I'll reflect these in the vote once it is open. Regarding the time slot, assuming we have more people from US/EMEA TZ attending the meeting, I'm ok with having the meeting late, but I hope we can finish it before 16:00 UTC (25:00 JST). Regarding the day, here in Japan we have more local holidays on Monday than the other days of a week, so I hope we can avoid Monday as I mentioned in my reply to the previous thread. I more likely get my own things on Friday or Wednesday. So I personally prefer Tuesday and Thursday, and then Wednesday as a fallback. On 10/29/24 1:59 AM, Herve Beraud wrote:
I don't think we can answer that question here. I'd encourage you to propose time slots and day and then to run a doodle vote on them.
Le lun. 28 oct. 2024 à 17:22, Daniel Bengtsson <dbengt@redhat.com <mailto:dbengt@redhat.com>> a écrit :
On 2024-10-28 15:55, Herve Beraud wrote: > If we decide to change the hour, then, the meeting page should > be updated (https://meetings.opendev.org/#Oslo_Team_Meeting <https://meetings.opendev.org/#Oslo_Team_Meeting> <https:// > meetings.opendev.org/#Oslo_Team_Meeting <http://meetings.opendev.org/#Oslo_Team_Meeting>>). Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
On Tue, 2024-10-29 at 15:43 +0900, Takashi Kajinami wrote:
+1 for using doodle vote to decide the slot.
Just dumping my preference here for your refernce but I'll reflect these in the vote once it is open.
Regarding the time slot, assuming we have more people from US/EMEA TZ attending the meeting, I'm ok with having the meeting late, but I hope we can finish it before 16:00 UTC (25:00 JST).
Regarding the day, here in Japan we have more local holidays on Monday than the other days of a week, so I hope we can avoid Monday as I mentioned in my reply to the previous thread. I more likely get my own things on Friday or Wednesday. So I personally prefer Tuesday and Thursday, and then Wednesday as a fallback.
Just thinking out loud: is it possible to alternate between (European) mornings and afternoons to catch both audiences? I don't think the Doodle captures this option. Stephen
On 10/29/24 1:59 AM, Herve Beraud wrote:
I don't think we can answer that question here. I'd encourage you to propose time slots and day and then to run a doodle vote on them.
Le lun. 28 oct. 2024 à 17:22, Daniel Bengtsson <dbengt@redhat.com <mailto:dbengt@redhat.com>> a écrit :
On 2024-10-28 15:55, Herve Beraud wrote: > If we decide to change the hour, then, the meeting page should > be updated (https://meetings.opendev.org/#Oslo_Team_Meeting <https://meetings.opendev.org/#Oslo_Team_Meeting> <https:// > meetings.opendev.org/#Oslo_Team_Meeting <http://meetings.opendev.org/#Oslo_Team_Meeting>>). Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
Le mer. 30 oct. 2024 à 13:06, Stephen Finucane <stephenfin@redhat.com> a écrit :
+1 for using doodle vote to decide the slot.
Just dumping my preference here for your refernce but I'll reflect these in the vote once it is open.
Regarding the time slot, assuming we have more people from US/EMEA TZ attending the meeting, I'm ok with having the meeting late, but I hope we can finish it before 16:00 UTC (25:00 JST).
Regarding the day, here in Japan we have more local holidays on Monday than the other days of a week, so I hope we can avoid Monday as I mentioned in my reply to the previous thread. I more likely get my own things on Friday or Wednesday. So I personally prefer Tuesday and Thursday, and
On Tue, 2024-10-29 at 15:43 +0900, Takashi Kajinami wrote: then
Wednesday as a fallback.
Just thinking out loud: is it possible to alternate between (European) mornings and afternoons to catch both audiences? I don't think the Doodle captures this option.
This is a good idea, I was thinking of maybe doing the same for the IRC meetings related to eventlet-removal. It would leave a chance for everybody to attend. The eventlet meetings are a bit different because they are bimonthly meetings so we could easily shift the time slot between the first and the second meeting. But as Daniel pushed to run it each week, IMO, it would be more complexe to apply it to oslo meetings. I'm far from a doodle expert, but from what I observed, doodle want specific dates so... maybe the trick is to propose 2 time slots on fake dates that more represent days of the week (monday, tuesday, wed...) than real dates, and then to select the both opposite time slots that best cover our extended time zone needs.
Stephen
On 10/29/24 1:59 AM, Herve Beraud wrote:
I don't think we can answer that question here. I'd encourage you to
propose time slots and day and then to run a doodle vote on them.
Le lun. 28 oct. 2024 à 17:22, Daniel Bengtsson <dbengt@redhat.com
<mailto:dbengt@redhat.com>> a écrit :
On 2024-10-28 15:55, Herve Beraud wrote: > If we decide to change the hour, then, the meeting page should > be updated (https://meetings.opendev.org/#Oslo_Team_Meeting <
https://meetings.opendev.org/#Oslo_Team_Meeting> <https://
> meetings.opendev.org/#Oslo_Team_Meeting <
http://meetings.opendev.org/#Oslo_Team_Meeting>>).
Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
---- On Wed, 30 Oct 2024 08:06:11 -0700 Herve Beraud wrote ---
Le mer. 30 oct. 2024 à 13:06, Stephen Finucane stephenfin@redhat.com> a écrit : On Tue, 2024-10-29 at 15:43 +0900, Takashi Kajinami wrote:
+1 for using doodle vote to decide the slot.
Just dumping my preference here for your refernce but I'll reflect these in the vote once it is open.
Regarding the time slot, assuming we have more people from US/EMEA TZ attending the meeting, I'm ok with having the meeting late, but I hope we can finish it before 16:00 UTC (25:00 JST).
Regarding the day, here in Japan we have more local holidays on Monday than the other days of a week, so I hope we can avoid Monday as I mentioned in my reply to the previous thread. I more likely get my own things on Friday or Wednesday. So I personally prefer Tuesday and Thursday, and then Wednesday as a fallback.
Just thinking out loud: is it possible to alternate between (European) mornings and afternoons to catch both audiences? I don't think the Doodle captures this option.
This is a good idea, I was thinking of maybe doing the same for the IRC meetings related to eventlet-removal. It would leave a chance for everybody to attend.The eventlet meetings are a bit different because they are bimonthly meetings so we could easily shift the time slot between the first and the second meeting.But as Daniel pushed to run it each week, IMO, it would be more complexe to apply it to oslo meetings. I'm far from a doodle expert, but from what I observed, doodle want specific dates so... maybe the trick is to propose 2 time slots on fake dates that more represent days of the week (monday, tuesday, wed...) than real dates, and then to select the both opposite time slots that best cover our extended time zone needs.
++ on alternate TZ meetings, and that way, EU and Asia TZ can be covered in one of the meetings. To keep it simple, we can have separate doodle poll for each TZ meeting. -gmann
Stephen
On 10/29/24 1:59 AM, Herve Beraud wrote:
I don't think we can answer that question here. I'd encourage you to propose time slots and day and then to run a doodle vote on them.
Le lun. 28 oct. 2024 à 17:22, Daniel Bengtsson dbengt@redhat.com dbengt@redhat.com>> a écrit :
On 2024-10-28 15:55, Herve Beraud wrote: > If we decide to change the hour, then, the meeting page should > be updated (https://meetings.opendev.org/#Oslo_Team_Meeting https://meetings.opendev.org/#Oslo_Team_Meeting> <https:// > meetings.opendev.org/#Oslo_Team_Meeting http://meetings.opendev.org/#Oslo_Team_Meeting>>). Yes I will updated but what is the best time and day for everyone?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://github.com/4383/>
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/
On 10/30/24 5:57 PM, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
++ on alternate TZ meetings, and that way, EU and Asia TZ can be covered in one of the meetings. To keep it simple, we can have separate doodle poll for each TZ meeting. Ok so maybe instead we can have one meeting per week. As you proposed like one for the Europeean and Asia and one for the us? I have create a first UTC pool here[1] afternoon and here[2] you have the morning one.
[1] https://www.vyte.in/e/1cnp51e4sd [2] https://www.vyte.in/e/2j0to257cd
I noticed that eventlet removal meeting is independent from the oslo meeting proposed in this thread. I'm ok to have dedicated slot to discuss oslo specific topics but may need to have clear scope definition. (Since it was mentioned that eventlet removal is the core topic we want to discuss in this meeting, right ?). Regarding the time slot, EMEA/NA slots might work better for me because I can join these after I settle down my own things, but I think it's generally got to have more Asia friendly slots if anyone from Asia (especially east-Asia) is interested in joining us. On 10/31/24 7:07 PM, dbengt@redhat.com wrote:
On 10/30/24 5:57 PM, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
++ on alternate TZ meetings, and that way, EU and Asia TZ can be covered in one of the meetings. To keep it simple, we can have separate doodle poll for each TZ meeting. Ok so maybe instead we can have one meeting per week. As you proposed like one for the Europeean and Asia and one for the us? I have create a first UTC pool here[1] afternoon and here[2] you have the morning one.
[1] https://www.vyte.in/e/1cnp51e4sd [2] https://www.vyte.in/e/2j0to257cd
Le jeu. 31 oct. 2024 à 18:38, Takashi Kajinami <kajinamit@oss.nttdata.com> a écrit :
I noticed that eventlet removal meeting is independent from the oslo meeting proposed in this thread. I'm ok to have dedicated slot to discuss oslo specific topics but may need to have clear scope definition. (Since it was mentioned that eventlet removal is the core topic we want to discuss in this meeting, right ?).
Oslo meetings are Oslo meetings, isn't the lifecycle of Oslo and the Oslo deliverables a clear scope? Oslo owns more than 40 deliverables, I don't think it would be difficult to find Oslo things to discuss. Another option would be to follow the series agenda, and to base our Oslo meetings over the series lifecycle (milestones, FF, etc.). Are people supposed to use this meeting agenda ( https://wiki.openstack.org/wiki/Meetings/Oslo) to put their topics and to retrieve the topics you propose? If you propose to base our discussions on a series lifecycle, maybe it could worth basing our meetings on an agenda like the one used by the release team https://etherpad.opendev.org/p/epoxy-relmgt-tracking,The release team created tooling to generate this kind of etherpad, perhaps you could reuse it... Concerning Eventlet. Eventlet may impact Oslo in some ways, but Oslo meetings are not the right place to host all the Eventlet discussions. Eventlet discussions will cover a wide range of topics, from neutron, to packaging, passing by requirements, and surely also Oslo at some points, so I don't think Oslo meetings is the right place. Nova, Neutron, Glance and surely many other deliverables already have internal discussions about Eventlet in their own IRC meetings, IMO Oslo should follow the same path.
Regarding the time slot, EMEA/NA slots might work better for me because I can join these after I settle down my own things, but I think it's generally got to have more Asia friendly slots if anyone from Asia (especially east-Asia) is interested in joining us.
You are the chair [1] of the Oslo meeting, so "joining us" mostly means "joining you". Asia time slots are before EMEA/NA so if you have your "own things before", my question is: would you be able to join and manage the Asia time slot? If your answer is no, IMO, it is useless to propose an Asia time slot, as people will wait for the meeting chair. It is up to you. [1] https://meetings.opendev.org/#Oslo_Team_Meeting
On 10/31/24 7:07 PM, dbengt@redhat.com wrote:
On 10/30/24 5:57 PM, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
++ on alternate TZ meetings, and that way, EU and Asia TZ can be
To keep it simple, we can have separate doodle poll for each TZ meeting. Ok so maybe instead we can have one meeting per week. As you proposed
covered in one of the meetings. like one for the Europeean and Asia and one for the us? I have create a first UTC pool here[1] afternoon and here[2] you have the morning one.
[1] https://www.vyte.in/e/1cnp51e4sd [2]
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
On 11/4/24 6:00 PM, Herve Beraud wrote:
Le jeu. 31 oct. 2024 à 18:38, Takashi Kajinami <kajinamit@oss.nttdata.com <mailto:kajinamit@oss.nttdata.com>> a écrit :
I noticed that eventlet removal meeting is independent from the oslo meeting proposed in this thread. I'm ok to have dedicated slot to discuss oslo specific topics but may need to have clear scope definition. (Since it was mentioned that eventlet removal is the core topic we want to discuss in this meeting, right ?).
Oslo meetings are Oslo meetings, isn't the lifecycle of Oslo and the Oslo deliverables a clear scope? Oslo owns more than 40 deliverables, I don't think it would be difficult to find Oslo things to discuss. Another option would be to follow the series agenda, and to base our Oslo meetings over the series lifecycle (milestones, FF, etc.).
Are people supposed to use this meeting agenda (https://wiki.openstack.org/wiki/Meetings/Oslo <https://wiki.openstack.org/wiki/Meetings/Oslo>) to put their topics and to retrieve the topics you propose?
If you propose to base our discussions on a series lifecycle, maybe it could worth basing our meetings on an agenda like the one used by the release team https://etherpad.opendev.org/p/epoxy-relmgt-tracking,The <https://etherpad.opendev.org/p/epoxy-relmgt-tracking,The> release team created tooling to generate this kind of etherpad, perhaps you could reuse it...
I totally agree with you about these points and these are exactly what I'd propose for oslo specific meeting. I just wanted to make sure that Daniel's expectation is similar, because in his initial email sounded that the eventlet removal is the key motivation to restore the meeting.
Concerning Eventlet. Eventlet may impact Oslo in some ways, but Oslo meetings are not the right place to host all the Eventlet discussions. Eventlet discussions will cover a wide range of topics, from neutron, to packaging, passing by requirements, and surely also Oslo at some points, so I don't think Oslo meetings is the right place. Nova, Neutron, Glance and surely many other deliverables already have internal discussions about Eventlet in their own IRC meetings, IMO Oslo should follow the same path.
+1
Regarding the time slot, EMEA/NA slots might work better for me because I can join these after I settle down my own things, but I think it's generally got to have more Asia friendly slots if anyone from Asia (especially east-Asia) is interested in joining us.
You are the chair [1] of the Oslo meeting, so "joining us" mostly means "joining you". Asia time slots are before EMEA/NA so if you have your "own things before", my question is: would you be able to join and manage the Asia time slot? If your answer is no, IMO, it is useless to propose an Asia time slot, as people will wait for the meeting chair.
This is the question to Daniel who is the primary chair (though I can help when he is not available on best effort basis). I wanted to make you aware of my preference assuming you may count me as a participant from Asia.
It is up to you.
[1] https://meetings.opendev.org/#Oslo_Team_Meeting <https://meetings.opendev.org/#Oslo_Team_Meeting>
On 10/31/24 7:07 PM, dbengt@redhat.com <mailto:dbengt@redhat.com> wrote: > > > On 10/30/24 5:57 PM, Ghanshyam Mann <gmann@ghanshyammann.com <mailto:gmann@ghanshyammann.com>> wrote: >> ++ on alternate TZ meetings, and that way, EU and Asia TZ can be covered in one of the meetings. >> To keep it simple, we can have separate doodle poll for each TZ meeting. > Ok so maybe instead we can have one meeting per week. As you proposed like one for the Europeean and Asia and one for the us? I have create a first UTC pool here[1] afternoon and here[2] you have the morning one. > > [1] https://www.vyte.in/e/1cnp51e4sd <https://www.vyte.in/e/1cnp51e4sd> [2] https://www.vyte.in/e/2j0to257cd <https://www.vyte.in/e/2j0to257cd> >
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
Le lun. 4 nov. 2024 à 13:51, Takashi Kajinami <kajinamit@oss.nttdata.com> a écrit :
On 11/4/24 6:00 PM, Herve Beraud wrote:
Le jeu. 31 oct. 2024 à 18:38, Takashi Kajinami <
kajinamit@oss.nttdata.com <mailto:kajinamit@oss.nttdata.com>> a écrit :
I noticed that eventlet removal meeting is independent from the oslo meeting proposed in this thread. I'm ok to have dedicated slot to discuss oslo specific topics but may need to have clear scope definition. (Since it was mentioned that eventlet removal is the core topic we want to discuss in this meeting, right ?).
Oslo meetings are Oslo meetings, isn't the lifecycle of Oslo and the
Oslo deliverables a clear scope? Oslo owns more than 40 deliverables, I don't think it would be difficult to find Oslo things to discuss. Another option would be to follow the series agenda, and to base our Oslo meetings over the series lifecycle (milestones, FF, etc.).
Are people supposed to use this meeting agenda (
https://wiki.openstack.org/wiki/Meetings/Oslo < https://wiki.openstack.org/wiki/Meetings/Oslo>) to put their topics and to retrieve the topics you propose?
If you propose to base our discussions on a series lifecycle, maybe it
could worth basing our meetings on an agenda like the one used by the release team https://etherpad.opendev.org/p/epoxy-relmgt-tracking,The < https://etherpad.opendev.org/p/epoxy-relmgt-tracking,The> release team created tooling to generate this kind of etherpad, perhaps you could reuse it...
I totally agree with you about these points and these are exactly what I'd propose for oslo specific meeting. I just wanted to make sure that Daniel's expectation is similar, because in his initial email sounded that the eventlet removal is the key motivation to restore the meeting.
Concerning Eventlet. Eventlet may impact Oslo in some ways, but Oslo meetings are not the right place to host all the Eventlet discussions. Eventlet discussions will cover a wide range of topics, from neutron, to packaging, passing by requirements, and surely also Oslo at some points, so I don't think Oslo meetings is the right place. Nova, Neutron, Glance and surely many other deliverables already have internal discussions about Eventlet in their own IRC meetings, IMO Oslo should follow the same path.
+1
Regarding the time slot, EMEA/NA slots might work better for me
because
I can join these after I settle down my own things, but I think it's generally got to have more Asia friendly slots if anyone from Asia (especially east-Asia) is interested in joining us.
You are the chair [1] of the Oslo meeting, so "joining us" mostly means
"joining you". Asia time slots are before EMEA/NA so if you have your "own things before", my question is: would you be able to join and manage the Asia time slot? If your answer is no, IMO, it is useless to propose an Asia time slot, as people will wait for the meeting chair.
This is the question to Daniel who is the primary chair (though I can help when he is not available on best effort basis). I wanted to make you aware of my preference assuming you may count me as a participant from Asia.
Thanks for pointing out that point, indeed, Daniel is the primary chair. I misread the "sender" of your previous answer. I wrote my previous response thinking that the email was sent by Daniel, that's why I spoke about the meeting chair and about the duties related to this role. My bad.
It is up to you.
https://meetings.opendev.org/#Oslo_Team_Meeting>
On 10/31/24 7:07 PM, dbengt@redhat.com <mailto:dbengt@redhat.com>
wrote:
> > > On 10/30/24 5:57 PM, Ghanshyam Mann <gmann@ghanshyammann.com
<mailto:gmann@ghanshyammann.com>> wrote:
>> ++ on alternate TZ meetings, and that way, EU and Asia TZ can be
covered in one of the meetings.
>> To keep it simple, we can have separate doodle poll for each TZ
meeting.
> Ok so maybe instead we can have one meeting per week. As you
proposed like one for the Europeean and Asia and one for the us? I have create a first UTC pool here[1] afternoon and here[2] you have the morning one.
> > [1] https://www.vyte.in/e/1cnp51e4sd <
https://www.vyte.in/e/1cnp51e4sd> [2] https://www.vyte.in/e/2j0to257cd < https://www.vyte.in/e/2j0to257cd>
>
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ <https://github.com/4383/>
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
Thanks for pointing out that point, indeed, Daniel is the primary chair. I misread the "sender" of your previous answer. I wrote my previous response thinking that the email was sent by Daniel, that's why I spoke about the meeting chair and about the duties related to this role. My bad. Since we didn’t receive many votes, we’ve decided on a flexible approach
On 2024-11-04 14:39, Herve Beraud wrote: that could work for everyone. We can alternate times each week: one week at 1:00 pm UTC (to accommodate European time zones), and the following week at 5:00 pm UTC (to suit US time zones). This week, we’ll start with the 1:00 pm UTC slot. Let me know if this works for everyone, and feel free to share any additional feedback -- Daniel Bengtsson Software engineer
Le lun. 11 nov. 2024 à 09:10, Daniel Bengtsson <dbengt@redhat.com> a écrit :
Thanks for pointing out that point, indeed, Daniel is the primary chair. I misread the "sender" of your previous answer. I wrote my previous response thinking that the email was sent by Daniel, that's why I spoke about the meeting chair and about the duties related to this role. My bad. Since we didn’t receive many votes, we’ve decided on a flexible approach
On 2024-11-04 14:39, Herve Beraud wrote: that could work for everyone. We can alternate times each week: one week at 1:00 pm UTC (to accommodate European time zones), and the following week at 5:00 pm UTC (to suit US time zones). This week, we’ll start with the 1:00 pm UTC slot. Let me know if this works for everyone, and feel free to share any additional feedback
Which day?
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
Le mar. 12 nov. 2024 à 11:32, Herve Beraud <hberaud@redhat.com> a écrit :
Le lun. 11 nov. 2024 à 09:10, Daniel Bengtsson <dbengt@redhat.com> a écrit :
Thanks for pointing out that point, indeed, Daniel is the primary chair. I misread the "sender" of your previous answer. I wrote my previous response thinking that the email was sent by Daniel, that's why I spoke about the meeting chair and about the duties related to this role. My bad. Since we didn’t receive many votes, we’ve decided on a flexible approach
On 2024-11-04 14:39, Herve Beraud wrote: that could work for everyone. We can alternate times each week: one week at 1:00 pm UTC (to accommodate European time zones), and the following week at 5:00 pm UTC (to suit US time zones). This week, we’ll start with the 1:00 pm UTC slot. Let me know if this works for everyone, and feel free to share any additional feedback
Which day?
Answered here https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
-- Daniel Bengtsson Software engineer
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/
participants (6)
-
Daniel Bengtsson
-
dbengt＠redhat.com
-
Ghanshyam Mann
-
Herve Beraud
-
Stephen Finucane
-
Takashi Kajinami