Search results for "canceled meeting" - openstack-discuss

[all][tc] What's happening in Technical Committee: summary 2022 Nov 18: Reading: 5 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 Nov 16. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html * Next week (Nov 23) TC weekly meeting is canceled[1]. 2. What we completed this week: ========================= * Defined process for the TC chair nomination & election[2] * Updated the 2023.1 cycle testing runtime[3] * Documented the upgrade patch testing in PTI[4] * Added zookeeper role under OpenStack-Ansible governance[5] * TC stopped using Storybooard. We were not using it for many cycles but TC officially decided [6] to clear all story and close the governance repo in Storyboard[7]. We will not use any other task tracking tool, etherpad or tracking things in meetings are working fine. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[8]. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the syncup call with Board members on Nov 16[10]. We discussed two topic in this call 1. "Less Diversity" and 2. i18 SIG. Most of the discussion was around first topic. There were multiple ideads were shared and discussed including: - Spreading and encouraging the contribution to wider audiance including large deployement, users, company manager. - Making contribution process more easy for part time contributorts. operators etc by helping them in testing requirement, process, half-baked patches to merge. - Reachout out to platinum members company and company executives to know the reason for not contributing in community and explain/encourage them to contribution. There was no concrete action or step to improve the Diversity but we all togehther need to put effort in all direction to improve it slowly. i18 SIG proposal by Brian about Weblate funding which is ~1500 Euro/year and this sounds reasonable to do from foundation but Brian need to write the foaml proposal to foundation before Board meeting on Dec 6th so that it can be discussed there is needed. Thanks Brian for working and following up on this. The next syncup call will be on Feb 2022-02-08 at 20:00 UTC. If anyone is interested, feel free to join it. Renovate translation SIG i18 ---------------------------------- * We discussed it in Board syncup call and Brian will take it forward to put the Weblate funding formal proposal to foundation. TC Video meeting discussion ---------------------------------- Based on the feedback JayF has abandoned the resolution patch[11]. Thanks JayF for proposal and discussion. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[12] * Add the cinder-infinidat charm to Openstack charms[13] * Add the infinidat-tools subordinate charm to OpenStack charms[14] * Add the manila-infinidat charm to Openstack charms[15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/tc/reference/tc-chair-elections.html [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03122… [4] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [5] https://review.opendev.org/c/openstack/governance/+/863161 [6] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html#… [7] https://review.opendev.org/c/openstack/project-config/+/864771 [8] https://etherpad.opendev.org/p/tc-2023.1-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2022-11-board-openstack-sync [11] https://review.opendev.org/c/openstack/governance/+/863685 [12] https://review.opendev.org/c/openstack/governance/+/863166 [13] https://review.opendev.org/c/openstack/governance/+/863958 [14] https://review.opendev.org/c/openstack/governance/+/864067 [15] https://review.opendev.org/c/openstack/governance/+/864068 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

2 years, 11 months

Re: openstack-discuss Digest, Vol 15, Issue 1

by Soniya Vyas

> Message: 4 > Date: Tue, 31 Dec 2019 19:03:22 -0600 > From: Ghanshyam Mann <gmann(a)ghanshyammann.com> > To: "openstack-discuss" <openstack-discuss(a)lists.openstack.org> > Subject: [qa] QA Office hour new timing for 2020 > Message-ID: > <16f5ea0ef6f.1010065b175496.3744470588375359656(a)ghanshyammann.com> > Content-Type: text/plain; charset="UTF-8" > > Hello Everyone, > > We have few members who actively started contribution to QA from India as well as from Europe TZ. > The current office hour time is more convenient for CT and JST only and very difficult for members from India > Europe to join. > > I would like to adjust office hour timing to include all four TZs. To do that someone has to wake up early or stay > late at night :). I gave preference to new members and selected Tuesday 13.30 UTC [1]. which will be an early morning > for me and late-night in Tokyo. > > let me know if any objection or better suggestion. Accordingly, I will make the new time effective from 7th Jan. > > Also cancelling the 1st Jan office hour and wish you all a very happy new year. > > [1] https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=… Thanks a lot to whole QA team and Ghanshyam Mann for considering our timing issues. Looking forward to join QA Office hours meeting. Regards, Soniya Vyas

5 years, 10 months

[election][cinder] PTL Candidacy for Yoga

by Brian Rosmaita

Hello everyone, I'd like to announce my candidacy for Cinder PTL for the Yoga cycle. The primary challenge we face in the Cinder community continues to be that our reviewing bandwidth has declined at the same time third-party driver contributions have not decreased. As I see it, the problem is that many vendors who maintain third-party drivers do not appear to be clear on the concept of community participation. (For what it's worth, I think this is more a manager problem than a developer problem, but the effect on Cinder is the same, namely, lots of request for reviews and not much doing of reviews. The Cinder documentation has information about how to review, how you don't need to be a core to do valuable reviews, etc., but it's not clear that many people have actually read them.) The Cinder community has tried to address this participation deficit in Xena by providing more upstream activities for contributors (for example, the monthly Festival of XS reviews [0] and the weekly Bug Squad meetings [1]), and these have had decent participation. In Yoga, I'd like to explore having some kind of Review Squad meeting to give people a chance to get "live" feedback on features under development. Some people do use the weekly Cinder meeting for this, but not everyone takes advantage of that, plus weekly meeting time is limited. I hate to propose yet another team meeting, but on the other hand, the bug squad and festival of reviews meetings are extremely productive, so I don't mind proposing another *productive* meeting. (We'll simply cancel it if it turns out that people don't take advantage. Also, I'm open to other ideas ... the key issue is providing faster feedback and more visibility for people developing cinder features, and allowing cinder cores to use their review time productively. So two key issues.) On the positive side, we did add a new cinder core during Xena and there's another person right on the verge of being proposed as a core. So that will help address review bandwidth, though I want to stress that non-core reviews are extremely important to the project as well. Our core reviewers also develop features and fix bugs--they are not full-time code reviewers. And the way to become a cinder core is to review widely in the project and demonstrate a good breadth of knowledge of the software. (As always, anyone currently working on cinder project who's interested becoming a cinder core, please contact me (or any of the current cores) to discuss what the expectations are.) Also on the good side is that we've done quite a bit of work on the Cinder CI this cycle. (I'm not going to tempt fate by saying anything more about that.) With respect to the details of Cinder development in Yoga, I expect those to emerge from our virtual PTG discussions in October. You can help set the agenda here: https://etherpad.opendev.org/p/yoga-ptg-cinder-planning To summarize, I would like to continue working on improving the review throughput of the Cinder team and find additional ways to get people more thoroughly involved in the project. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita) [0] http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews [1] http://eavesdrop.openstack.org/#Cinder_Bug_Squad_Meeting

4 years, 2 months

Re: [nova][ptg][ops] Nova at the vPTG (+ skipping next weekly meeting)

by Sofia Enriquez

Hi Sylvain, I hope you're doing well. Apologies for the delay in responding to your previous message. I wanted to suggest a cross-project topic with Cinder that involves adding support for NFS encryption. To complement the work on Cinder[3], I've proposed two patches [1][2] and would appreciate any feedback you may have. I believe it would be beneficial to discuss my approach during the PTG, but I'm open to discussing it during a weekly meeting as well. I've looked at the etherpad and am considering the first slot on Wednesday or the last slot on Thursday or Friday. Please let me know your thoughts. Thank you, Sofia [1] https://review.opendev.org/c/openstack/nova/+/854030 [2] https://review.opendev.org/c/openstack/nova/+/870012 [3] https://review.opendev.org/q/topic:bp%252Fnfs-volume-encryption On Wed, Mar 22, 2023 at 9:46 AM Sylvain Bauza <sbauza(a)redhat.com> wrote: > Hey folks, > > As a reminder, the Nova community will discuss at the vPTG. You can see > the topics we'll talk in https://etherpad.opendev.org/p/nova-bobcat-ptg > > Our agenda will be from Tuesday to Friday, everyday between 1300UTC and > 1700UTC. Connection details are in the etherpad above, but you can also use > PTGbot website : https://ptg.opendev.org/ptg.html (we'll use the diablo > room for all the discussions) > > You can't stick around for 4 hours x 4 days ? Heh, no worries ! > If you (as an operator or a developer) want to engage with us (and we'd > love this honestly), you have two possibilities : > - either you prefer to listen (and talk) to some topics you've seen in > the agenda, and then add your IRC nick (details how to use IRC are > explained by [1]) on the topics you want. Once we start to discuss about > those topics, I'll ping the courtesy ping list of each topic on > #openstack-nova. Just make sure you're around in the IRC channel. > - or you prefer to engage with us about some pain points or some feature > requests, and then the right time is the Nova Operator Hour that will be on > *Tuesday 1500UTC*. We have a specific etherpad for this session : > https://etherpad.opendev.org/p/march2023-ptg-operator-hour-nova where you > can preemptively add your thoughts or concerns. > > Anyway, we are eager to meet you all ! > > Oh, last point, given we will be at the vPTG, next week's weekly meeting > on Tuesday is CANCELLED. But I guess you'll see it either way if you lurk > the #openstack-nova channel ;-) > > See you next week ! > -Sylvain > > [1] > https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032853.h… > > > -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

2 years, 7 months

Re: FW: 2020 OSF Events & coronavirus

by Sean Mooney

On Tue, 2020-03-17 at 08:18 -0700, Julia Kreger wrote: > 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. of the two types of events i think the second e.g. PTG/Forum is the one that we as a comunity would be most impacted by if it was not to go ahead either physically or virtually. the summit/marketplace may impact sales to a degree but for those of us that work at a company/vendor that makes money form openstack we have large sales and marketing teams anyway so the sales lead perspective while valid is not really that critical to the same degree as losing the opportunity to collaborate and cross pollinate ideas between different aspect of the comunity. it is very true that a lot of conversation happen in the hallway but those conversatoin can happen on irc or video calls too but the barrier to entry is obviously higher to start them. > > 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, 7 months

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

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Nov 11th Thursday. * 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-11-11-15.00.log.html * Next week's meeting is canceled due to OpenInfra Keynotes and we will continue weekly meeting on 25th Nov, Thursday 15:00 UTC, feel free the topic on agenda[1] by Nov 24th. 2. What we completed this week: ========================= * Changes in stable core team process[2] * Decouple the community-wide goals from cycle release[3] (I will write up summary on this once we have RBAC goal merged as an example) * Merged 'Technical Writing' SIG into TC[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. Open Reviews ----------------- * 12 open reviews for ongoing activities[6]. Review volunteer required for Openstack CI Log Processing project -------------------------------------------------------------------------------- dpawlik sent the email on openstack-discuss[7] about seeking help to review on new Openstack CI Log Processing project. Please respond there if you can help at some extent even not as full time. Remove office hours in favor of weekly meetings ----------------------------------------------------------- We decided to remove the TC in-active office hours[8] in favor of weekly meetings which are serving the purpose of office hours. RBAC discussion: continuing from PTG ---------------------------------------------- We had a discussion on Wed 10th too and agreed on what all we can target for Yoga cycle. Complete notes are in this etherpad[9]. Please review the goal rework[10]. Discussion on open items will be continued in policy popup team meeting[11] Community-wide goal updates ------------------------------------ * With the continuing the discussion on RBAC, we are re-working on the RBAC goal, please wait until we finalize the implementation[8] * There is one more goal proposal for 'FIPS compatibility and compliance'[12]. Adjutant need maintainers and PTLs ------------------------------------------- No volunteer to lead/maintain the Adjutant project, I have sent another reminder to the email[13]. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG and there are few open points about python packaging, repos, and plugins plan which we are discussion on ML. * Still waiting from skyline team to work on the above points[14]. Updating the Yoga testing runtime ---------------------------------------- * As centos stream 9 is released, I have updated the Yoga testing runtime[15] with: 1. Add Debian 11 as tested distro 2. Change centos stream 8 -> centos stream 9 3. Bump lowest python version to test to 3.8 and highest to python 3.9 TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[16]. Project updates ------------------- * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’[17] * Retire training-labs repo[18] * Retire puppet-senlin[19] * Add ProxySQL repository for OpenStack-Ansible[20] * Retire js-openstack-lib [21] 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[22]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [23] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025741… [3] https://review.opendev.org/c/openstack/governance/+/816387 [4] https://review.opendev.org/c/openstack/governance/+/815869 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025758… [8] https://review.opendev.org/c/openstack/governance/+/817493 [9] https://etherpad.opendev.org/p/policy-popup-yoga-ptg [10] https://review.opendev.org/c/openstack/governance/+/815158 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025760… [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] https://review.opendev.org/c/openstack/governance/+/815851 [16] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [17] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [18] https://review.opendev.org/c/openstack/governance/+/817511 [19] https://review.opendev.org/c/openstack/governance/+/817329 [20] https://review.opendev.org/c/openstack/governance/+/817245 [21] https://review.opendev.org/c/openstack/governance/+/807163 [22] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [23] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

4 years

Re: [SDK][OSC] Meeting Times

by Kendall Nelson

Looks like we are a go for this week! If you want to join us, add your nick to the ping list at the top of the etherpad! If you have topics you'd like to discuss, add them to the agenda as well :) https://etherpad.opendev.org/p/openstacksdk-meeting-agenda -Kendall (diablo_rojo) On Thu, Nov 12, 2020 at 2:31 PM Kendall Nelson <kennelson11(a)gmail.com> wrote: > I also created this etherpad to hold our meeting agendas: > https://etherpad.opendev.org/p/openstacksdk-meeting-agenda > > -Kendall (diablo_rojo) > > > On Thu, Nov 12, 2020 at 2:29 PM Kendall Nelson <kennelson11(a)gmail.com> > wrote: > >> 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) >>> >> >>> >> >>> >> >>> > >>> >>>

5 years

[all][tc] What's happening in Technical Committee: summary 03 June 2022: Reading: 5 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 02 June. Most of the topics I am summarizing in this email. This was a video call and recordings are available @ https://www.youtube.com/watch?v=nHG2WJNceMs And logs summary are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-06-02-15.02.log.html * We are cancelling next week's meeting. The next TC weekly meeting will be on 16 June Thursday at 15:00 UTC, feel free to add the topic to the agenda[1] by 15 June. 2. What we completed this week: ========================= * TC resolution[2] and documentation[3] for OpenStack release identification schema. This clarify what place we need to use the release number and name. * Security SIG chair rotation from Gage to Jeremy[4] * Removed security-analysis repo from Security SIG[5] * Added a repository for the Large Scale SIG[6] * Added project stats check tool[7] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[8], many items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[10]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[11]. New ELK service dashboard: e-r service ----------------------------------------------- dpawlik working on ansible playbooks to deploy e-r and functional tests. TripleO team and dpawlik are working on the e-r repo merge. Consistent and Secure Default RBAC ------------------------------------------- We had a call yesterday and discussed about presenting this to the ops meetup in berlin and getting feedback, especially on the 'scope' concept. knikolla plan to moderate this topic in the ops meetup but unfortunately he will not be to make it to the summit. I have added a few notes and what questions we need to ask the operator in etherpad[12]. Please note that operator feedback is very important for us to proceed on 'scope' in SRBAC. If you are operator or know anyone around you, we request you to provide feedback. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15][16]. Project updates ------------------- * Add a repository for the Large Scale SIG[17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 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/+/843214 [3] https://review.opendev.org/c/openstack/governance/+/841800 [4] https://review.opendev.org/c/openstack/governance-sigs/+/844446 [5] https://review.opendev.org/c/openstack/governance/+/844463 [6] https://review.opendev.org/c/openstack/governance/+/843535 [7] https://review.opendev.org/c/openstack/governance/+/810037 [8] https://etherpad.opendev.org/p/tc-zed-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [11] https://review.opendev.org/c/openstack/governance/+/839880 [12] https://etherpad.opendev.org/p/ops-meetup-berlin-2022-planning#L53 [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [17] https://review.opendev.org/c/openstack/project-config/+/843534 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

3 years, 5 months

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

by Ghanshyam Mann

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Oct 14th Thursday. * 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-10-14-15.00.log.html * Next week's meeting is cancelled as we are meeting in PTG. We will have the next IRC meeting on Oct 28th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Oct 27th. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ * TC is using the etherpad[2] for Xena cycle working item. We will be checking it in PTG * Current status is: 9 completed, 3 to-be-discussed in PTG, 1 in-progress Open Reviews ----------------- * Six open reviews for ongoing activities[3]. New project 'Skyline' proposal ------------------------------------ * You might be aware of this new dashboard proposal in the previous month's discussion. * A new project 'Skyline: an OpenStack dashboard optimized by UI and UE' is now proposed in governance to be an official OpenStack project[4]. * Skyline team is planning to meet in PTG on Tue, Wed and Thu at 5UTC, please ask your queries or have feedback/discussion with the team next week. Place to maintain the external hosted ELK, E-R, O-H services ------------------------------------------------------------------------- * We had a final discussion or I will say just a status update on this which was mentioned in last week's email summary[5]. * Now onwards, discussion and migration work will be done in TACT SIG (#openstack-infra IRC channel). Add project health check tool ----------------------------------- * No updates on this, we will continue discussing it in PTG for the next steps on this and what to do with TC liaison things. * Meanwhile, we are reviewing Rico proposal on collecting stats tools [6]. Stable Core team process change --------------------------------------- * Current proposal is under review[7]. Feel free to provide early feedback if you have any. Call for 'Technical Writing' SIG Chair/Maintainers ---------------------------------------------------------- * As agreed in last week's TC meeting, we will be moving this SIG work towards TC. * TC members have been added to the core members list in the SIG repos. * We will be discussing where to move the training repos/work in PTG. TC tags analysis ------------------- * Operator feedback is asked on open infra newsletter too, and we will continue the discussion in PTG and will take the final decision based on feedback we receive, if any[9]. Complete the policy pop up team ---------------------------------------- * Policy pop team has served its purpose and we have new RBAC as one of the the community-wide goal for the Yoga cycle. * We are marking this popup team as completed[10]. Project updates ------------------- * Retiring js-openstack-lib [11] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [12]. * Current status: "Secure RBAC" is selected for Yoga cycle[13]. PTG planning ---------------- * We will be meeting in PTG next week, please check the details in this etherpad [14] * Do not forget to join the TC+community leaders sessions on Monday, Oct 18 15 UTC - 17 UTC. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[15], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [18] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-xena-tracke [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/814037 [5]http://lists.openstack.org/pipermail/openstack-discuss/2021-October/02525… [6] https://review.opendev.org/c/openstack/governance/+/810037 [7] https://review.opendev.org/c/openstack/governance/+/810721 [9] https://governance.openstack.org/tc/reference/tags/index.html [10] https://review.opendev.org/c/openstack/governance/+/814186 [11] https://review.opendev.org/c/openstack/governance/+/798540 [12] https://review.opendev.org/c/openstack/governance/+/807163 [13] https://etherpad.opendev.org/p/y-series-goals [14] https://etherpad.opendev.org/p/tc-yoga-ptg [15] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [18] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

4 years, 1 month

Re: [ironic] Mid-cycle call times

by Dmitry Tantsur

Thanks Julia! I guess we're canceling the weekly meeting because of the overlap? On 1/18/19 12:49 PM, Julia Kreger wrote: > Greetings everyone! > > I've created a fairly simple schedule: > > January 21st 2:00 - 4:00 UTC > > 2:00 PM UTC - Discuss current status > 2:30 PM UTC - Revising current plans and reprioritizing as necessary > 3:30 PM UTC - Making Ironic more container friendly. 3:30pm - until the last person gets too tired to argue :D > > January 22nd 2:00 - 4:00 UTC > > 2:00 PM UTC - Boot Management for in-band inspection > 2:30 PM UTC - SmartNIC configuration support > 3:00 PM UTC - Disucss any other items that arose during the earlier discussions. > 3:30 PM UTC - Bug and RFE Triaging > > If there are no objections, we can use my bluejeans[1] account to discuss. > Please see our planning/discussion etherpad[2]. > > Thanks! I look forward to chatting with everyone soon. > > -Julia > > [1]: https://bluejeans.com/u/jkreger > [2]: https://etherpad.openstack.org/p/ironic-stein-midcycle > > On Tue, Jan 15, 2019 at 12:00 PM Julia Kreger > <juliaashleykreger(a)gmail.com> wrote: >> >> Greetings everyone, >> >> It seems the most popular times are January 21st and 22nd between 2 PM >> and 6 PM UTC. >> >> Please add any topics for discussion to the etherpad[1] as soon as >> possible. I will propose a schedule and agenda in the next day or two. >> >> -Julia >> >> [1]: https://etherpad.openstack.org/p/ironic-stein-midcycle >> >> On Tue, Jan 8, 2019 at 9:10 AM Julia Kreger <juliaashleykreger(a)gmail.com> wrote: >>> >>> Greetings everyone! >>> >>> It seems we have coalesced around January 21st and 22nd. I have posted >>> a poll[1] with time windows in two hour blocks so we can reach a >>> consensus on when we should meet. >>> >>> Please vote for your available time windows so we can find the best >>> overlap for everyone. Additionally, if there are any topics or items >>> that you feel would be a good use of the time, please feel free to add >>> them to the planning etherpad[2]. >> [trim] >

6 years, 9 months

openstack-discuss search results for query "canceled meeting"