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/