On Thu, Oct 5, 2023 at 11:23 PM Frode Nordahl <frode.nord...@canonical.com> wrote: > > On Thu, Oct 5, 2023 at 9:20 PM Ilya Maximets <i.maxim...@ovn.org> wrote: > > > > On 10/5/23 19:31, Dumitru Ceara wrote: > > > Hi all, > > > > > > On 9/22/23 09:19, Frode Nordahl wrote: > > >> Hello Dumitru and Team, > > >> > > >> On Thu, Sep 21, 2023 at 5:25 PM Dumitru Ceara <dce...@redhat.com> wrote: > > >>> > > >>> Hi all, > > >>> > > >>> As you probably know and as the ovn.org website mentions [0] we have > > >>> weekly OVN IRC meetings, in #openvswitch on irc.libera.chat (the time is > > >>> slightly wrong but that's a different issue [1]). > > >>> > > >>> In my opinion these meetings are useful because we (well, anyone > > >>> interested) can share status updates about what they currently work on > > >>> in the OVN world. > > >> > > >> The weekly IRC meetings are indeed valuable, they are very useful for > > >> coordinating ongoing community activities and highlighting/discussing > > >> any issues that are not obvious across company barriers on a day to > > >> day basis. > > >> > > >>> I wonder however if it would make sense to have an alternative technical > > >>> meeting (it doesn't necessarily have to replace the weekly IRC one but > > >>> it may) where slightly more in depth technical discussion can happen. > > >>> I'm thinking of this as an optional first step that might happen before > > >>> posting the first (RFC) version of a feature, for example. Or as a > > >>> place where objectives for a new LTS can be defined from a community > > >>> perspective. > > >>> > > >>> At the same time I wonder if such a meeting would be more effective if a > > >>> different communication medium would be used (e.g., an online video > > >>> conference system). > > >>> > > >>> In short, would a monthly (audio/video) technical community meeting > > >>> sound like an interesting idea to you? > > >> > > >> Thank you for bringing this up. My immediate reaction is positive, an > > >> audio/video meeting would carry more bandwidth for exchanging thoughts > > >> and ideas on any topic discussed. If we manage to create a safe space > > >> for bouncing not necessarily fully thought through ideas off each > > >> other, it could be quite powerful. > > >> > > >> I'm wondering a bit about the cadence though, IIUC the examples of > > >> potential topics to discuss fall into the planning ahead category. > > >> Would it perhaps make sense to have these meetings before the start of > > >> each development cycle, i.e. a set of meetings every 6 months or so, > > >> perhaps with touch points in between? > > >> > > > > > > I'm going to try to summarize the points/concerns that were raised > > > so far in this email thread and during the IRC meetings. Please > > > do correct me if I missed or mis-interpreted something. > > > > > > - there seems to be positive reaction from the community to the > > > proposal of having an occasional A/V technical community > > > meeting. > > > > > > - there's a request to not replace the IRC weekly (that should > > > stay weekly and be used for informal status updates). > > > > > > - the cadence of this new community meeting is not yet agreed > > > upon: > > > - there were a few suggestions to have a monthly meeting > > > with a pre-defined agenda and with the option of > > > cancelling the meeting if there's not enough to talk > > > about. > > > - an alternative would be to have these technical meetings > > > at the beginning of each development cycle (every ~6 months) > > > with an option of ad-hoc touching points in between. > > > > > > - there was a suggestion of recording the meetings and posting > > > the recordings to ovn.org. Personally I'm not sure I'd favor > > > that; the reason being that I think it might cause people to > > > be more reluctant to join. I'm OK either way though. Related > > > to this point, there was a suggestion to take and share > > > meeting notes. > > > > > > - we briefly discussed about the medium to use and, at least > > > during the IRC meeting, it seemed like Google Meet would > > > be an OK option for now. > > Thank you for summarizing, your account above resonates with my > perspective on the discussions so far as well. > > > > With all this in mind and (luckily) because we're at the > > > beginning of the 24.03 development cycle, my suggestion > > > would be to schedule a first community A/V technical meeting > > > with two agenda items: > > > > > > 1. What new features or relevant changes does the community > > > think are important to have in the next release (24.03.0)? > > > 2. Decide on a cadence for the technical meetings. > > > > > > Here are some proposals for dates and times for a first > > > meeting. Please reply with a list of what works best for > > > you, preferably best options first. Alternative suggestions > > > are also fine. > > > > > > Monday October 23rd 3PM UTC / 8PM PDT > > > Tuesday October 24th 3PM UTC / 8PM PDT > > > Monday October 23rd 7PM UTC / 12PM PDT > > > Monday October 30th 3PM UTC / 8PM PDT (this is just before the ovn-k8s community meeting) > > > > FWIW, 3PM UTC on any Monday sounds fine to me. > > > > Monday 7PM is the second best, but not particularly desirable. :) > > And I may have a conflict on Tuesdays on and off. > > 3PM UTC Monday works for me too, I'm traveling October 30th though. >
3PM UTC Mondays work for me, too. Han > -- > Frode Nordahl > > > > > > > > > I can share a Google Meet invite link as soon as we agree > > > on the best time for this first meeting. We can decide > > > about recording the meeting/taking notes on the spot in > > > the beginning of the meeting. > > > > > > Thanks, > > > Dumitru > > > > > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
