Search results for "canceled meeting" - openstack-discuss

Re: [manila][ptg] Victoria Cycle PTG in Vancouver - Planning

by Goutham Pacha Ravi

Hello Zorillas, As you're aware, we're going virtual for this PTG, and I've signed up for some slots on the PTG Planning Ethercalc [2]. If anyone has any concerns, please let me know. Thanks for adding and grooming the discussion items on the planning ether pad [1]. Please continue to add/change topics, we'll assign specific discussion items to the chosen time slots in the coming weeks. Please note that our meeting on Tuesday (2nd June) is split into two separate meetings: == June 1st (Monday) == 14:00 UTC - 15:00 UTC 15:00 UTC - 16:00 UTC 16:00 UTC - 17:00 UTC == June 2nd (Tuesday) == 15:00 UTC - 16:00 UTC 16:00 UTC - 17:00 UTC 21:00 UTC - 22:00 UTC 22:00 UTC - 23:00 UTC == June 3rd (Wednesday) == No Meeting == June 4th (Thursday) == No Meeting The weekly IRC Community Meeting at 15:00 UTC will be canceled as well. == June 5th (Friday) == 14:00 UTC - 15:00 UTC 15:00 UTC - 16:00 UTC 16:00 UTC - 17:00 UTC (Grab your drink and join us for an Open Discussion/Happy Hour) Thanks, Goutham Pacha Ravi (gouthamr) PTL, OpenStack Manila [1] https://etherpad.openstack.org/p/vancouver-ptg-manila-planning [2] https://ethercalc.openstack.org/126u8ek25noy On Fri, Feb 7, 2020 at 12:13 PM Goutham Pacha Ravi <gouthampravi(a)gmail.com> wrote: > > Hello Zorillas and other interested Stackers, > > We've requested space to gather at the Open Infrastructure PTG event > in Vancouver, BC between June 8th-11th 2020. This event gives us the > opportunity to catch up in person (and via telepresence) and discuss > the next set of goals for manila and its ecosystem of projects. > > As has been the norm, there's now a planning etherpad for us to > collect topics and vote upon [1]. Depending on how much space/time we > are budgeted, we will select and schedule these topics. > > Please take a look and add your topics to the etherpad. > > Thanks, > Goutham > > [1] https://etherpad.openstack.org/p/vancouver-ptg-manila-planning

5 years, 3 months

[all][tc] What's happening in Technical Committee: summary 24th Dec, 21: Reading: 5 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had a quick meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-23-15.00.log.html * Next week's meeting on 30th Dec is canceled. We will continue our weekly meeting from Jan 6th, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 5th Jan. 2. What we completed this week: ========================= * Nothing much in this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[2]. Open Reviews ----------------- * 4 open reviews for ongoing activities[3]. SIG i18n status check -------------------------- Ian (SIG chair) responded on ML thread and will look into the things after he is back from leave next month[4]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[5] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[6]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[7]. Skyline as official projects ------------------------------ We accepted the Skyline as an official project last week and next work on project renaming etc are also started. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[8]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [9] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Marry Chirsmas and Happy new year to everyone and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-yoga-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026441… [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] https://etherpad.opendev.org/p/zuul-config-error-openstack [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [9] https://review.opendev.org/c/openstack/governance/+/798540 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

3 years, 7 months

Re: FW: 2020 OSF Events & coronavirus

by Julia Kreger

Greetings, I think we need to consider teasing out the reasoning behind events a little more. When we look at summits, they are largely events to broadcast outward our work and provide vendors an avenue to express their new features and functionality, and generate sales leads. Where as the events likely need to be teased apart a little more. What we've traditionally referred to as a summit is largely rooted in broadcasting outward what we as a community are working on and the direction where we are going, while providing a time and space for vendors to to show off their solutions and offerings. To me, this largely seems like a coordinated outreach and marketing Blitz. And this is not one of JUST vendors, but of project teams as well for they need to convey what they have been working on and their focus as a community. If we look the PTG and Forum sorts of events that we have had, they provide more an avenue for collaboration and discussion. That could be as simple as a rough list of topics, and a few predefined "hallways" where random discussion can occur. In a sense, the hallway becomes the un-conference if we empower and enable it. Anyway, before we jump into ideas and implementation scenarios, we need to have a clear motivation behind each "event" that the community and it's partners can rally behind, and I suspect that will only come from the OSF events team as well as track chairs/organizers. -Julia On Tue, Mar 17, 2020 at 3:56 AM Sagi Shnaidman <sshnaidm(a)redhat.com> wrote: > > Hi, all > I think the Openstack community has more virtual collaboration experience than any other community and maybe it's a good chance for us to establish an efficient way to make a virtual summit. I'm not alone thinking virtual summits/webinars/whatever are much less efficient than in-person meetings and hanging out together. But in current circumstances, it doesn't seem like an option, so why not try brainstorm about how we still can do a virtual summit and get most of it? > > Main issues with virtual meetings that I can see are: > > - topics discussions in a big group of people, while virtual meetings often less convenient and sometimes are tough[1] > - the important things happen also *between* sessions, not during them > - what would replace booths (and swags of course)? > - PTG project rooms which are used both for internal discussions and collaboration between various projects > - informal mingling > > I'm not sure all of these and other issues can be easily replaced virtually, but who knows, maybe we can still make it work. Like maybe constant open video sessions which mimic rooms and booths, some of the discussions moved to dedicated IRC channels. > On the flip side, the offline summit had restrictions as well, so we can do things in a virtual summit we couldn't (or couldn't do so much) in offline ones. Maybe more presenters will have a chance to make sessions since we are not so limited in time online and all sessions can be recorded as well. And we don't need a projector in every PTG room now :) > I'd propose creating a page where people can put their ideas on how to make good things we have in the offline summit to be virtual or add something new, which couldn't be done in the offline summit. Since we created recently "Ideas for OpenStack" page[2], maybe it's a good candidate to hold these ideas in. > Just reminding that Openstack is not the only project that cancels offline meetings and efficient virtual collaboration is a very hot topic right now all over the world. I think the Openstack community has all the resources to contribute from its experience to many other projects and companies and be leading in this area. > WDYT? > > [1] https://www.youtube.com/watch?v=DYu_bGbZiiQ > [2] https://governance.openstack.org/ideas/index.html > > On Thu, Mar 12, 2020 at 4:13 PM <Arkady.Kanevsky(a)dell.com> wrote: >> >> Agree that going virtual makes most sense given current status >> >> >> >> From: Emilien Macchi <emilien(a)redhat.com> >> Sent: Wednesday, March 11, 2020 5:46 PM >> To: Mark Collier >> Cc: openstack-discuss; Jonathan Bryce >> Subject: Re: FW: 2020 OSF Events & coronavirus >> >> >> >> [EXTERNAL EMAIL] >> >> Hi Mark, >> >> >> >> Thanks for the transparency, as usual. I have a few thoughts, please read inline. >> >> >> >> On Fri, Mar 6, 2020 at 4:04 PM Mark Collier <mark(a)openstack.org> wrote: >> >> upcoming event in Vancouver is no exception. The OpenDev tracks >> > each morning will be programmed by volunteers from the community, and the project >> > teams will be organizing their own conversations as well each afternoon M-W, and >> > all day Thursday. >> > >> > But the larger question is here: should the show go on? >> > >> > The short answer is that as of now, the Vancouver and Berlin events are still >> > scheduled to happen in June (8-11) and October (19-23), respectively. >> > >> > However, we are willing to cancel or approach the events in a different way (i.e. >> > virtual) if the facts indicate that is the best path, and we know the facts are >> > changing rapidly. One of the most critical inputs we need is to hear from each of >> > you. We know that many of you rely on the twice-annual events to get together and >> > make rapid progress on the software, which is one reason we are not making any >> > decisions in haste. We also know that many of you may be unable or unwilling to >> > travel in June, and that is critical information to hear as we get closer to the >> > event so that we can make the most informed decision. >> >> >> I believe that we, as a community should show the example and our strengths by cancelling the Vancouver event and organize a virtual event like some other big events are doing. >> >> There is an opportunity for the OSF to show leadership in Software communities and acknowledge the risk of spread during that meeting; not only for the people attending it but for also those in contact with these people later. >> >> >> >> I'm not a doctor nor I know much about the virus; but I'm not interested to travel and take the risk to 1) catch the virus and 2) spread it at home and in my country; and as a community member, I feel like our responsibility is also to maintain ourselves healthy. >> >> >> >> In my opinion, the sooner we cancel, the better we can focus on organizing the virtual meetings, and also we can influence more communities to take that kind of decisions. >> >> >> >> Thanks Mark for starting that discussion, it's a perfect sign of how healthy is our community; and hopefully it will continue to be. >> >> -- >> >> Emilien Macchi > > > > -- > Best regards > Sagi Shnaidman

5 years, 4 months

[ironic] [ptg] PTG week schedule

by Dmitry Tantsur

Hi ironicers! The PTG is next week, and I'd like to share our plans for it. We don't have anything planned on Monday, and the weekly meeting is cancelled as well. 2-hour slots are reserved Tuesday to Friday 14:00 UTC - 16:00 UTC in the Liberty room. The up-to-date schedule and notes are available on https://etherpad.opendev.org/p/Ironic-VictoriaPTG-Planning, the current version is as follows: Tue, Jun 2nd: 14:00-15:00: Releases, perceptions and our place in the world: governance and perceptions 15:00-16:00: Releases, perceptions and our place in the world: standalone future Wed, Jun 3rd: 14:00-15:00: Deployment Efficency 15:00-16:00: Aborting non-waiting transient states Thu, Jun 4th: 14:00-15:00: Fishy future 15:00-16:00: IPAM integrations outside of Neutron Fri, Jun 5th: 14:00-15:00: Operator suggestions/feedback/painpoints 15:00-16:00: Ideas and brainstorming I would like to highlight the operators feedback slot on Friday at 14:00 UTC. We would like to hear more opinions from people running ironic! Please join us. Hear from you soon, Dmitry

5 years, 2 months

[all][tc] What's happening in Technical Committee: summary 2022 Nov 25: Reading: 5 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ *This week's meeting was cancelled. * Next TC weekly meeting will be on Nov 30 Wed at 16:00 UTC. Feel free to add the topic to the agenda[1] by Nov 29. 2. What we completed this week: ========================= * Nothing specific this week. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[2]. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. Technical Election changes (Extending Nomination and voting period) ---------------------------------------------------------------------------------- As discussed in TC PTG sessions, TC is extending the technical election (PTL as well as the TC election) nomination and voting period from 1 week to 2 weeks. The TC charter change[4] is up for review and the changes will be effective from the 2023.2 cycle technical elections. Renovate translation SIG i18 ---------------------------------- * As the next step, Brian is working on the weblate funding proposal and it will be discussed with the Foundation staff and Board members in Dec 6th board meeting. Adjutant situation (project is not active) ----------------------------------------------- The adjutant project is not active. The last changes merged was on Oct 26, 2021 (more than 1 year back), Gate is broken also. During July this year, TC was marking this project as inactive[5] but Dale smith volunteered as PTL to maintain it. But there is no improvement in the situation yet. TC will be discussing it in the next TC meeting and decide the next step. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[6] * Add the cinder-infinidat charm to Openstack charms[7] * Add the infinidat-tools subordinate charm to OpenStack charms[8] * Add the manila-infinidat charm to Openstack charms[9] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/865367 [5] https://review.opendev.org/c/openstack/governance/+/849153 [6] https://review.opendev.org/c/openstack/governance/+/863166 [7] https://review.opendev.org/c/openstack/governance/+/863958 [8] https://review.opendev.org/c/openstack/governance/+/864067 [9] https://review.opendev.org/c/openstack/governance/+/864068 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

2 years, 8 months

Re: [nova][ptg] PTG participation

by Balázs Gibizer

On Thu, Mar 12, 2020 at 15:45, Sylvain Bauza <sbauza(a)redhat.com> wrote: > > > On Wed, Mar 11, 2020 at 7:11 PM Sean Mooney <smooney(a)redhat.com> > wrote: >> On Wed, 2020-03-11 at 17:36 +0000, Sean Mooney wrote: >> > On Wed, 2020-03-11 at 18:17 +0100, Balázs Gibizer wrote: >> > > Hi, >> > > >> > > I've just got the news from my employer that due to COVID19 I >> cannot >> > > travel to Vancouver in June. >> Since then the in-person PTG in Vancuver has been canceled [1]. So we have to come up with a virtual PTG plan that works for most of the people and allows us to discuss nova and cross project related questions regarding the Victoria cycle. >> > >> > From a redhat perspective i dont think a decision has been made >> on if we should attend or not. >> ill clarify that slightly in that we do have guidence that "Red >> Hatters may not travel to attend external events or >> conferences with 1000+ attendees, even within their home country." >> >> in the past when the ptg and summit were combinined and we had the >> devsumit have ment that travel to the openstack even >> would not be allowed. At its current size its kind of in a gray >> zone where its is not banned as a public event but if it >> was an internal event the number of redhat employee that would be >> attending woudl be over the limit we have and the >> physical event would be canceled and converted to a virtual only >> event. >> >> so its tbd if i will be attending too although i have not heard a >> definitive No at this point but i also cant really >> book tickets and flight yet either however the guidance we have >> been given is to try and default to virtual attendance >> were possible. >> >> > last time i spoke to my manager we were still waiting to see how >> thing progress with the assumtion we would attend >> > but we might want to plan for a virtual PTG (via video >> conference, etherpad and email) in the event many cant travel >> > or >> > that things escalate to a point where the PTG event could be >> canceled. >> > >> > i dont think the foundation has indicated that that is likely to >> happen but im sure they are monitoring >> > things closely as our employers will be so having a plan b might >> now be a bad thing in either case. >> > if there isnt a diverse quoram physically at the ptg it would >> limit our ability to make desisions as happend to >> > some extent in china. it would be still good to get operator >> feedback but they may also be under similar travel >> > restrictions. >> > > > > > I personnally have concerns with virtual events that are large like > our PTG : > - which timezone should we use for the virtual PTG ? Anyway, Asia, > Europe or North America folks could have problems with one. > - some folks (like me) have bandwidth issues in their (home) > offices. They could be having problems when trying to discuss > - how can we be sure that all of us can discuss by a virtual meeting > ? Not saying it won't work, but discussions could take more time. I agree that his is a problem. I think we cannot make a 3 days, 8 hours long video meeting due to timezone, bandwidth and other restrictions. Here is what I propose: Until two weeks before the PTG: * Collect discussion topics on the etherpad [2] as usual * you also free to start reflecting on and discussing such topics that are already on the etherpad. Two weeks before the PTG (May 25 - May 29) * I will scan the etherpad and for each open topics I will start a mail thread to have focused discussion. * If the discussion is not finished on a given topic within this week then I will ask the proposer of the topic to organize a real-time meeting (chat, voice, video) either for the week before the PTG (Jun 1 - June 5) or for the week of the PTG (Jun 8 - Jun 12). I think based on the active participants of the mail (or etherpad) discussion the proposer will know who to involve to the real-time discussion. So not every nova devs needs to sit through every video meeting in obscure local times. I'm proposing this longish three weeks schedule to i) allow enough time for an ML discussion to conclude if the topic is straight forward ii) make it possible at the end of the first week to start organizing real time discussions and still have two weeks for those discussion to be scheduled. It might take time to find and agree on a common time slot and there will be popular time slots. So in both case more available days can help. What do you think? > > Anyway, I'm sad for you, gibi. I'm not -2 about a virtual PTG, I just > want to make sure we think about the above concerns before agreeing > with any virtual PTG. I agree. We need to figure out what could work. Cheers, gibi [1] https://www.openstack.org/events/opendev-ptg-2020/ [2] https://etherpad.openstack.org/p/nova-victoria-ptg

5 years, 4 months

[all][tc] What's happening in Technical Committee: summary Mar 25th, 21: Reading: 10 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Mar 24th. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-24-15.00.log.html * Due to OpenInfra episode and PTG, we have cancelled the next two meetings[1] and will be meeting on April 14th Thursday 15:00 UTC, feel free to add the topic on the agenda[2] by April 13th. 2. What we completed this week: ========================= * None for this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[3]. 4 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Five open reviews for ongoing activities[4]. Consistent and Secure Default RBAC -------------------------------------------- I sent the updates for Yoga timeline target on ML[5] and created the etherpad to track this goal for all the milestone[6]. The quick summary is, along with keystone, Nova has completed the work and neutron is in progress. Community-wide goals readiness checklist -------------------------------------------------- As we received the feedback in Yoga PTG TC+PTL interaction session, I have proposed the checklist which can help us to check if the goal is ready to start or not[7], please review and let us know if more items need to be added. Zed cycle Leaderless projects ---------------------------------- No updates on this. I am still waiting for Zaqar PTL +1 on the PTL appointment patch[8] and we will discuss Adjutant in PTG, hoping Braden will be ready with their company side permission[9]. PTG Preparation -------------------- Nothing much to share on this but please continue adding the topics in etherpad[10]. Dropping tags framework ------------------------------ Along with deprecation tag removal[11], we are removing the complete framework now[12]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[13]. Project updates ------------------- * None for this week. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027828.ht… [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027837.ht… [6] https://etherpad.opendev.org/p/rbac-goal-tracking [7] https://review.opendev.org/c/openstack/governance/+/835102 [8] https://review.opendev.org/c/openstack/governance/+/831123 [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] https://etherpad.opendev.org/p/tc-zed-ptg [11] https://review.opendev.org/c/openstack/governance/+/834327 [12] https://review.opendev.org/c/openstack/governance/+/834798/3 [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

3 years, 4 months

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-15)

by Goutham Pacha Ravi

Hello Stackers, We're 15 weeks away from the 2025.1 ("Epoxy") release date (2024-04-02) [1]. During the last week, the Technical Committee continued discussing the state of "unmaintained" code branches across OpenStack repositories and election officials proposed dates for the combined TC+PTL elections for the next release cycle [2]. We have decided to cancel the weekly meetings previously scheduled for 24th December and 31st December in lieu of the holidays. === Weekly Meeting === The OpenStack Technical Committee met over IRC on 2024-12-10 [3]. We revisited challenges with using CentOS 10 in the community CI system due to lack of AVX/AVX2 CPU flags on current cloud providers. Discussions revolved around finding providers with suitable hardware or reducing reliance on CentOS testing. We then revisited the state of "unmaintained" branches across OpenStack repositories. The oldest "unmaintained" branch tracks the "victoria" release (GA: 2020-10-14). The consensus amongst TC members was to enforce the policy to default old branches to EOL unless explicitly opted-in with required maintenance assurances. To do this, we need tooling to automate the transition, and a way to track and validate volunteer opt-ins for unmaintained branches. Volunteers stepped up to transition branches up until the 2023.1 ("Antelope") release to "end-of-life", beginning with the Victoria release branch [4]. If you're interested in keeping a particular branch open, for any repository, please express your interest directly on the gerrit change. All EOL transition patches will be merged after 1 month of community review. The next meeting of the OpenStack Technical Committee is on 2024-12-17 at 1800 UTC. This meeting will take place in the #openstack-tc channel on OFTC's IRC server. Please find the meeting agenda on the wiki [5]. Please remember that you can propose topics for upcoming TC meetings by directly editing the wiki. If you're unable to do so, please holler at me (IRC nick: gouthamr) or in the TC's IRC channel (#openstack-tc). === Governance Proposals === ==== Merged ==== - Retire Murano/Senlin/Sahara OpenStack-Ansible roles | https://review.opendev.org/c/openstack/governance/+/935677 ==== Open for Review ==== - Add ansible-role-httpd repo to OSA-owned projects | https://review.opendev.org/c/openstack/governance/+/935694 - Rework the initial goal proposal as suggested by people | https://review.opendev.org/c/openstack/governance/+/931254 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 - Propose to select the eventlet-removal community goal | https://review.opendev.org/c/openstack/governance/+/934936 - Allow more than 2 weeks for elections | https://review.opendev.org/c/openstack/governance/+/937741 === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - IRC: Ping us using the tc-members keyword on the #openstack-tc IRC channel on OFTC. - Weekly Meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [5]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.2/"F" elections proposal: https://review.opendev.org/c/openstack/election/+/937408 [3] TC Meeting IRC Log 2024-12-10: https://meetings.opendev.org/meetings/tc/2024/tc.2024-12-10-18.01.log.html [4] Transition unmaintained/victoria to EOL: https://review.opendev.org/c/openstack/releases/+/937515 [5] TC Meeting Agenda, 2024-12-17: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

7 months, 2 weeks

Re: [SDK][OSC] Meeting Times

by Kendall Nelson

Sorry I am so slow at replying here! 14:00 UTC works for me so long as its only once a month I need to wake up at 6AM lol. I proposed the patch here: https://review.opendev.org/762590 -Kendall (diablo_rojo) On Thu, Oct 29, 2020 at 1:25 AM Artem Goncharov <artem.goncharov(a)gmail.com> wrote: > Thanks Kendall for starting the discussion. > > Being located in CET (UTC+1/2) I am fine going one hour earlier (14:00 > UTC) to have it not so late for Akihiro and avoid clash with Manila, but am > also flexible making it 16:00 (cancelled API-SIG). > > Maybe a doodle will help to pick the most suitable? I hope to get a bit > more answers from other interested parties. > > Regards, > Artem > > > On 29. Oct 2020, at 02:48, Akihiro Motoki <amotoki(a)gmail.com> wrote: > > > > Thanks for starting the thread. > > I agree it is a good idea to have a regular meeting even though it is > > less frequent. > > > > Thursday 15UTC is okay with me. > > 16UTC is a bit late to me as it is 1am in my local time. One hour > > earlier (14UTC) also works for me. > > > > Thanks, > > Akihiro Motoki (amotoki) > > > > On Thu, Oct 29, 2020 at 7:49 AM Kendall Nelson <kennelson11(a)gmail.com> > wrote: > >> > >> Hello! > >> > >> In the PTG session today we talked about doing some sort of regular > meetings to kind of jump start things after the more recent lack of > activity. We discussed beginning with more frequent meetings (a couple > across the next few weeks) and then shifting to a more relaxed monthly > cadence. > >> > >> I propose 15:00 UTC on the third thursday of each month as our monthly > meeting time? If people agree, I will propose a patch :) > >> > >> As for the more frequent ones to keep the momentum from discussion from > this week/last week. We could use that time (15 UTC) and date (Thursdays) > and maybe just do them on Nov 12 and 19th to keep us moving? That gives us > next week to catch up/ take a breath from the last two weeks, but not > waiting till after the US Thanksgiving holiday. > >> > >> Let me know what you think! > >> > >> -Kendall Nelson (diablo_rojo) > >> > >> > >> > > > >

4 years, 8 months

[all][tc] What's happening in Technical Committee: summary April 1st, 21: Reading: 10 min

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We canceled this week meeting. * Next TC weekly meeting will be after PTG on April 14th Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by April 13th. 2. What we completed this week: ========================= * Removed the tags framework[2]. * Defined 2022 upstream investment opportunities[3]. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 6 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Consistent and Secure Default RBAC -------------------------------------------- I collected few of the RBAC related topic in RBAC PTG etherpad[6], also please add the questions or discussion point in that etherpad if you would like to discuss with TC on Thursday 14 UTC. Community-wide goals readiness checklist -------------------------------------------------- As we received the feedback in Yoga PTG TC+PTL interaction session, I have proposed the checklist which can help us to check if the goal is ready to start or not[7], please review and let us know if more items need to be added. Zed cycle Leaderless projects ---------------------------------- No updates on this. I am still waiting for Zaqar PTL +1 on the PTL appointment patch[8] and we will discuss Adjutant in PTG, hoping Braden will be ready with their company side permission[9]. PTG Preparation -------------------- I have prepared the schedule and updated in etherpad[10], please check and see you all next week. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Add Ganesha based Ceph NFS Charm[12] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/834798 [3] https://governance.openstack.org/tc/reference/upstream-investment-opportuni… [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/rbac-zed-ptg [7] https://review.opendev.org/c/openstack/governance/+/835102 [8] https://review.opendev.org/c/openstack/governance/+/831123 [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] https://etherpad.opendev.org/p/tc-zed-ptg [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/835429 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

3 years, 4 months

openstack-discuss search results for query "canceled meeting"