| *** tosky_ is now known as tosky | 00:25 | |
| opendevreview | James Page proposed openstack/governance master: Retire all single charm repositories https://review.opendev.org/c/openstack/governance/+/903490 | 11:23 |
|---|---|---|
| opendevreview | Dr. Jens Harbott proposed openstack/openstack-manuals master: Fix release links for numeric series https://review.opendev.org/c/openstack/openstack-manuals/+/903498 | 12:43 |
| opendevreview | Dr. Jens Harbott proposed openstack/openstack-manuals master: Fix release links for numeric series https://review.opendev.org/c/openstack/openstack-manuals/+/903498 | 12:57 |
| fungi | SvenKieske: ^ | 13:26 |
| frickler | I wanted to check the build results before pinging, but this does lgtm now. tc-members: ^^ | 13:32 |
| fungi | yep | 13:34 |
| SvenKieske | ty | 14:03 |
| opendevreview | Dr. Jens Harbott proposed openstack/openstack-manuals master: Enable kolla and openstack-ansible for 2023.2 https://review.opendev.org/c/openstack/openstack-manuals/+/903512 | 15:04 |
| frickler | noonedeadpunk: fyi ^^ took the liberty to also include osa in this | 15:04 |
| noonedeadpunk | frickler: thanks a ton! | 15:06 |
| noonedeadpunk | our releases patch just got merged today so I didn't have a chance to update it yet | 15:07 |
| noonedeadpunk | Btw. I beleive that TripleO is still not dropped, is it? | 15:07 |
| noonedeadpunk | https://review.opendev.org/c/openstack/openstack-manuals/+/885052 | 15:07 |
| noonedeadpunk | Probably it needs more work now though | 15:08 |
| noonedeadpunk | ah, there was another one | 15:09 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-manuals master: Drop hardcoded TripleO links https://review.opendev.org/c/openstack/openstack-manuals/+/885052 | 15:09 |
| fungi | noonedeadpunk: i thought the tc got word from tripleo delegates that proceeding with retirement and/or dispersing of remaining deliverables was okay to comply with the new "unmaintained" branch policies | 15:20 |
| frickler | fungi: I haven't heard about that, but it sure would be good to clean some things up | 15:23 |
| fungi | i'll see if i can find a reference, but it was in response to tc concerns that tripleo's plan to take care of unmaintained/wallaby without any volunteers for newer branches would run counter to the approved process | 15:28 |
| fungi | it sounded like they were okay with the idea of continuing to just care for the old stable/wallaby branch downstream inside red hat rather than within openstack | 15:29 |
| frickler | oh, there was something some months ago, yes. iirc they said eoling things by end of october should turn out to be fine, but I haven't seen any confirmation of that after that date nor any action being taken | 15:31 |
| opendevreview | Merged openstack/openstack-manuals master: Drop hardcoded TripleO links https://review.opendev.org/c/openstack/openstack-manuals/+/885052 | 15:38 |
| noonedeadpunk | fungi: frankly speaking - I was not following very closely tripleo discussions lately as have quite some internal battles to fight right now :( | 15:43 |
| fungi | understandable | 15:48 |
| opendevreview | Dr. Jens Harbott proposed openstack/openstack-manuals master: Enable kolla and openstack-ansible for 2023.2 https://review.opendev.org/c/openstack/openstack-manuals/+/903512 | 15:56 |
| frickler | ERROR has_deployment_guide set for openstack-ansible but https://docs.openstack.org/project-deploy-guide/openstack-ansible/2023.2/index.html does not exist (404) | 16:26 |
| frickler | noonedeadpunk: I think that may still need a patch merged after the release in order to trigger publishing? do you have one in the pipeline or shall we set it to false for now? | 16:28 |
| fungi | yeah, looks like nothing's been published for it yet based on what i see at https://static.openstack.org/docs/project-deploy-guide/openstack-ansible/ | 16:30 |
| fungi | https://zuul.opendev.org/t/openstack/builds?job_name=promote-openstack-tox-docs&project=openstack/openstack-ansible says it ran in the last minute | 16:32 |
| fungi | next afs vos release should happen in a couple of minutes | 16:33 |
| fungi | oh, maybe the deploy guide uses a different job | 16:36 |
| frickler | yes, https://docs.openstack.org/openstack-ansible/2023.2/ is fine | 16:36 |
| fungi | agreed, the file list in https://zuul.opendev.org/t/openstack/build/3f31d10d2ad4457da6951347b0a59f49/console#1/0/28/localhost doesn't cover it | 16:37 |
| frickler | we need https://zuul.opendev.org/t/openstack/builds?job_name=build-openstack-deploy-guide&project=openstack/openstack-ansible | 16:38 |
| fungi | https://zuul.opendev.org/t/openstack/builds?job_name=promote-deploy-guide&project=openstack%2Fopenstack-ansible&pipeline=promote&skip=0&limit=50 | 16:40 |
| fungi | yeah, looks like it will only happen when there are changes to the deploy guide content | 16:40 |
| fungi | https://opendev.org/openstack/openstack-ansible/src/branch/master/zuul.d/project-templates.yaml#L295-L317 | 16:41 |
| jrosser | i'm not sure what we are supposed to do other than make some kind of noop patch to the 2023.2 deploy guide | 16:46 |
| fungi | or amend the file filter to include something that naturally gets patched immediately after branch creation (.gitreview?) | 16:47 |
| jrosser | good idea, for this release thats already merged though https://review.opendev.org/c/openstack/openstack-ansible/+/903496 | 16:48 |
| fungi | yeah, so some other sort of no-op change this time around | 16:48 |
| jrosser | ok those changes are proposed, lets see what happens | 17:01 |
| JayF | tc-members: meeting in 56 minutes | 17:04 |
| * frickler wonders how people act upon this long warning, for me it is just a distraction. something between 5-15 mins could be useful instead IMO | 17:37 | |
| JayF | frickler: it's not something I ever found useful, but some TC members asked me to continue it as chair. I use meeting reminders and calendars extensively personally to not miss stuff :D | 17:38 |
| frickler | so you have a calendar entry to send this reminder? isn't there a bot can do this? ;) | 17:40 |
| JayF | frickler: many people would be concerned to see the number of 2-5 minute "reminder/time cutout to do X" meetings on my calendar ;) | 17:42 |
| JayF | I am extremely unreliable by nature, and make up for it with meticulous planning, documentation, and remindering. | 17:43 |
| JayF | Part of why I'm such a stickler for documentation. If I forget to write something down; I might literally just forget it altogether | 17:43 |
| JayF | #startmeeting tc | 18:00 |
| opendevmeet | Meeting started Tue Dec 12 18:00:07 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| opendevmeet | The meeting name has been set to 'tc' | 18:00 |
| knikolla | o/ | 18:00 |
| JayF | Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 18:00 |
| JayF | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee. | 18:00 |
| JayF | #topic Roll Call | 18:00 |
| gmann | o/ | 18:00 |
| JayF | o/ | 18:00 |
| frickler | \o | 18:00 |
| spotz[m] | o/ | 18:00 |
| rosmaita | o/ | 18:00 |
| JayF | #info dansmith the only noted absense in the agenda | 18:00 |
| jamespage | o/ | 18:00 |
| spotz[m] | I'll be out after this week I'll update the agenda | 18:00 |
| jamespage | ditto | 18:01 |
| JayF | Thanks spotz[m] and jamespage! Enjoy the holiday! | 18:01 |
| JayF | We have quorum, will give a couple more minutes for late arrivals. | 18:02 |
| slaweq | o/ | 18:03 |
| slaweq | sorry for being late | 18:03 |
| JayF | No problem :) everyone gets overlapping meetings/TZ issues/etc | 18:03 |
| JayF | #topic Follow up on tracked action items | 18:03 |
| JayF | All of these are about the OIF Bylaws change. | 18:03 |
| JayF | #info There is no strict deadline for approval of OIF bylaws related governance changes. | 18:04 |
| JayF | That takes care of mine. | 18:04 |
| gmann | yeah, I pushed the changes for TC tracker #link https://review.opendev.org/c/openstack/governance/+/903236 | 18:04 |
| JayF | gmann you signed up to create teh two changes, I believe you did | 18:04 |
| gmann | and this is resolution to vote on the bylaw changes #link https://review.opendev.org/c/openstack/governance/+/903239 | 18:04 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/903236 | 18:04 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/903239 | 18:04 |
| JayF | Thank you for that, I'll dedicate time to review them immediately after the meeting and I suggest all tc-members do the same. | 18:05 |
| JayF | Any questions about the TC charter/OIF bylaws change since we don't have a dedicated agenda item? | 18:05 |
| gmann | I would request all tc-members to check those, as JayF mentioned there is no hard deadline but we should finish this work as soon as we can so that foundation will finish the bylaw change process | 18:05 |
| gmann | yeah, we can discuss here if any question | 18:05 |
| gmann | *here also | 18:06 |
| JayF | Please add to the pre-holiday list at a minimum :D | 18:06 |
| JayF | #topic Gate Health Check | 18:06 |
| gmann | ++ | 18:06 |
| JayF | How is the gate looking? | 18:06 |
| knikolla | thanks gmann, will review today :) | 18:06 |
| gmann | thanks | 18:06 |
| JayF | Ironic had a couple days breakage this week, landing a big chain of patches to the ironic<>nova driver, and the middle state is apparently broken. We've temporarily disabled the broken job and have had the fix in the nova gate since yesterday morning. | 18:06 |
| slaweq | I think gate looks pretty good, at least from what I can say | 18:07 |
| gmann | on gate side, there have been some failure on nova side and melwitt continuously proposing some ideas/fixes which are helpful . | 18:07 |
| gmann | other than that I have not observed any frequent failure in general tempest jobs | 18:07 |
| JayF | Thanks for the efforts folks are putting forward to keep the gate running. Moving on. | 18:07 |
| JayF | #topic Leaderless projects | 18:08 |
| JayF | #link https://etherpad.opendev.org/p/2024.1-leaderless | 18:08 |
| gmann | one update here: there is PTL proposal for ec2api also #link https://review.opendev.org/c/openstack/governance/+/903163 | 18:08 |
| gmann | i think we have 3 open proposal now, please review those | 18:08 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/903163 New proposal for ec2api ptl | 18:08 |
| fungi | the foundation staff have been informed that the opensearch donation from amazon is being restructured to a monthly allocation instead of yearly. some costs have spiked over the past two months and we're in danger of getting charged an overage | 18:09 |
| fungi | i've started talking to dpawlik to see if we can figure out what's triggered that and how we can scale it back | 18:09 |
| JayF | I'll note that melwitt's work on Nova's gate, recently mentioned, is using opensearch extensively | 18:09 |
| JayF | and has been evangelized around the list/nova devs/etc | 18:09 |
| JayF | and may be the entire explanation... | 18:09 |
| fungi | sorry, meant to type that before the topic changed | 18:10 |
| JayF | Not a problem :) | 18:10 |
| gmann | yeah opensearch was replacement of ELK thing which are needed for our day to day activities | 18:10 |
| fungi | an alternative might be to seek a donor to help cover the additional cost (amazon is only willing to chip in us$50k/yr) | 18:11 |
| gmann | I think fungi has good point of being in danger and we should discuss it on priority | 18:12 |
| JayF | fungi: would it be possible to have you raise this concern to the openstack-discuss mailing list? | 18:12 |
| gmann | it was 45K last year rufht? | 18:12 |
| gmann | right | 18:12 |
| fungi | JayF: i definitely can | 18:12 |
| gmann | more than openstack-discuss I think this is board or foundation staff level discussion we should have | 18:12 |
| fungi | i'm getting most of this info second-hand and am sort of playing middle-man between parties | 18:12 |
| JayF | gmann: awareness at every level provides value imo :) | 18:13 |
| gmann | no harm in asking other volunteer in openstack-discuss though but that should not be enough i think | 18:13 |
| gmann | JayF: sure | 18:13 |
| gmann | I can re-start the thread between board and TC we had last time on this so that we know the background and can restart the discussion | 18:14 |
| JayF | Thanks for that. | 18:14 |
| gmann | I mean board informal strategic discussion we had last time on this | 18:14 |
| gmann | I can include the interested tc-members in that ML, ping me. will include JayF for sure | 18:15 |
| * frickler wonders what interest aws has in sponsoring this. they don't seem interested in openstack otherwise, are they? | 18:15 | |
| spotz[m] | me please | 18:15 |
| gmann | ack | 18:15 |
| * frickler too | 18:15 | |
| rosmaita | frickler: you can use s3 as a backend for cinder/glance | 18:16 |
| gmann | frickler: Allison Randal helped to get this sponsoring so she might have more background/aws relational | 18:16 |
| gmann | but as it was yearly help, we kind of expected this could have next year or later. | 18:17 |
| frickler | so people actually use AWS S3 instead of radosgw? (but I agree that this is getting offtopic now) | 18:18 |
| JayF | Yeah, I'm going to move on to the next topic :) | 18:19 |
| JayF | #topic Implementation of Unmaintained Branch Statuses | 18:19 |
| JayF | It looks like this is starting to make some motion, which is exciting! Is there any specific update for this week, rosmaita? | 18:19 |
| rosmaita | nothing from me, i will take an action item to check in with the release team on Friday and report back next week | 18:20 |
| rosmaita | (we left it that they will ping the TC if they need help) | 18:20 |
| JayF | Do you want that in the minutes or just, you'll have an update at this topic next week? | 18:20 |
| * JayF assumes you'll just update us on the topic next week and avoids double-booking the topic | 18:20 | |
| JayF | #topic 2024.1 TC Tracker | 18:21 |
| rosmaita | ok | 18:21 |
| JayF | #link https://etherpad.opendev.org/p/tc-2024.1-tracker | 18:21 |
| JayF | Any updates on TC tracker-tracked items? | 18:21 |
| JayF | Moving on to next topic. | 18:22 |
| JayF | #topic Open Discussion and Reviews | 18:22 |
| JayF | #link https://review.opendev.org/q/status:open+repo:openstack/governance | 18:22 |
| JayF | Please have a look at open governance reviews; I'll make a pass this afternoon as usual to merge eligible changes. | 18:23 |
| JayF | Any topics for open discussion this week? | 18:23 |
| frickler | I was hoping we'd also handle inactive projects under the leaderless topic, but so I'll mention these here for visibility | 18:23 |
| JayF | ++ please do, lets link those changes into the agenda | 18:23 |
| gmann | ++ | 18:23 |
| gmann | I will review those today | 18:23 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/902623 | 18:23 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/902624 | 18:24 |
| frickler | those patches are stacked on top of each other because otherwise they'd conflict, let me know if I should change the ordering | 18:24 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/902625 | 18:24 |
| JayF | #link https://review.opendev.org/c/openstack/governance/+/902626 | 18:24 |
| JayF | Is there anything further to discuss on that or other topics for open discussion? | 18:25 |
| fungi | sorry, juggling multiple meetings in this timeslot, but the indication from amazon was that their interest in donating opensearch resources was to raise the profile of opensearch recognizing it as a legitimate open source project and also of their managed opensearch service offering | 18:25 |
| frickler | so marketing, ok ;) | 18:26 |
| frickler | repeating my comment from last week: testing fungi's affiliation patch 876738 I see that 4 members do no specify an affiliation in their profile, maybe everyone can check and fix that? | 18:26 |
| fungi | (remember that amazon forked opensearch when elastic changed the license on elasticsearch, so have been trying to get out from under that shadow) | 18:26 |
| gmann | ++ | 18:26 |
| JayF | frickler: can we be specific about where that affiliation is set? | 18:26 |
| JayF | frickler: wondering if we need to #action the tc-members who need to set affiliations to do a change to do so | 18:27 |
| frickler | JayF: in your profile on the oif page | 18:27 |
| gmann | #link https://openinfra.dev/a/profile | 18:27 |
| gmann | I think openstack.org is synced up automatically or it is otherway around ? | 18:27 |
| gmann | or we need to update both | 18:27 |
| frickler | iiuc oif is the source of truth nowadays | 18:28 |
| jamespage | fixing mine now | 18:28 |
| gmann | most of time (not recently) updated openstack.org and it got synced up in openinfra.dev also but doing directly on openinfra is good | 18:28 |
| JayF | Ack; thanks for that callout frickler. We should resolve that issue before we, say, pass resolutions that change our charter to depend on that information :D | 18:29 |
| frickler | there's also the question whether e.g. "Red Hat Inc." is different from "Red Hat" or "Red Hat $country" and how to handle that | 18:29 |
| knikolla | ugh, i thought i had one. will update mine. | 18:29 |
| frickler | or "Canonical $somewhere" for that matter | 18:29 |
| gmann | I think 'Affiliation' definition in bylaws consider them all single org right? but its tooling we need to take care of that | 18:30 |
| frickler | finally there's also the question whether we should also ask PTLs and other leader positions to provide this information | 18:30 |
| gmann | not sure if IBM and Red Hat is considered same? | 18:30 |
| * slaweq just fixed own profile | 18:30 | |
| slaweq | gmann: I don't think it should | 18:31 |
| knikolla | i fixed mine too. | 18:31 |
| JayF | I think it's valuable to have the information; but unless we have specific requirements in bylaws for affiliation diversity around PTLs, I don't think we should require them. | 18:31 |
| spotz[m] | Red Hat and IBM not the same | 18:31 |
| JayF | But that being said -- the info is useful for non-leaders too. It's useful generally. | 18:31 |
| spotz[m] | Red Hat, Red Hat Inc. are the same, we have to clean them up in the speakers list every Summit:) | 18:31 |
| gmann | yeah, info is good. agree with frickler to ask PTL also but just a nice to have info in profile | 18:32 |
| gmann | and mandatory for election things | 18:32 |
| fungi | i was doing affiliation analysis recently and found contributors spelling "red hat" 28 (no joke) different ways | 18:33 |
| frickler | PTLs are also elected, so we could decide to make this mandatory information to provide? but asking nicely is fine for me for now | 18:33 |
| knikolla | fungi: that's impressive | 18:33 |
| gmann | :) | 18:34 |
| knikolla | my partner has two first names and two last names and it's fun to see all the different ways software systems fail to cope with that. | 18:34 |
| spotz[m] | And don't forget RedHat | 18:34 |
| slaweq | LOL | 18:35 |
| fungi | technically we do at least need accurate affiliation data for tc candidates in order to avoid violating the current charter limits on affiliation | 18:35 |
| JayF | ++ | 18:35 |
| gmann | yeah | 18:35 |
| spotz[m] | I agree though I think we're good at noting Red Hat and Red Hat Inc are the same on a manual level:) | 18:35 |
| gmann | should we have that info in this page too? #link https://governance.openstack.org/tc/ | 18:36 |
| spotz[m] | It's when we try to do things programmatically it takes more effort | 18:36 |
| gmann | this table #link https://governance.openstack.org/tc/#current-members | 18:36 |
| JayF | It'd be nice from a documentation standpoint; but not at the cost of having that affiliation have two sources of truth | 18:36 |
| spotz[m] | Maybe as most of us seem to use personal emails for Open Source work | 18:36 |
| JayF | if we could pull it from opendev profile into that page; awesome; if not, I'd worry about drift | 18:37 |
| spotz[m] | I guess we can't just pull it in? | 18:37 |
| frickler | some variant of fungi's script could do that | 18:37 |
| frickler | maybe not live, but via some check job? | 18:37 |
| fungi | that script is still mostly a poc but happy to make improvements and polish it | 18:37 |
| gmann | i think check during election time or any change in TC members is enough | 18:38 |
| JayF | ++ | 18:38 |
| frickler | ok I have another thing I mentioned earlier, but failed to link to the actual page :-/ https://docs.openstack.org/install-guide/openstack-services.html | 18:38 |
| JayF | We trust CI for more important things than this, such as if the software we govern actually does anything :D | 18:38 |
| spotz[m] | I would say the stackalytics file but you don't need to add yourself there unless you change companies for some reason | 18:38 |
| gmann | +1 | 18:38 |
| frickler | this mentions yoga and earlier, no wonder ppl keep installing old releases | 18:38 |
| JayF | spotz[m]: that file is not updated anymore, stackalytics is not maintained, patches to that file have been open months and months | 18:39 |
| JayF | spotz[m]: we really need to not direct people there/treat the website as gone :( | 18:39 |
| gmann | frickler: nice catch | 18:39 |
| spotz[m] | If I get time over the holidays I'll work on the install guides, no promises | 18:40 |
| frickler | so do we want to drop EOL releases there? and how can we keep this up to date? | 18:40 |
| fungi | openstack.biterg.io is trying to pull affiliation data from openinfraid (foundation) profiles, but we have very spotty coverage owing to people not having much incentive to keep their affiliations/date ranges accurate there | 18:40 |
| JayF | Does someone want to take an action to dig into this? There is no docs team. | 18:40 |
| gmann | good point, and with unmaintained status, do we want to keep those also there? | 18:40 |
| JayF | I don't think the TC meeting is the best place to go point by point, but we can get a few interested folks together who want to fix things up | 18:41 |
| gmann | or maybe have those all there even people install EOL release also | 18:41 |
| gmann | at least they find doc somewhere | 18:41 |
| gmann | good to add this i tracker and ask for volunteer | 18:41 |
| gmann | *in | 18:41 |
| gmann | there are many doc issues still | 18:42 |
| frickler | +1 | 18:42 |
| spotz[m] | Ok I think I can up date the links on that page, it gets a little wonky where we go from name to numbers.... | 18:43 |
| JayF | spotz[m]: can I put you down for an action to follow up post-holidays, even if it's not done, just like, status update/let folks know where it lies? | 18:43 |
| spotz[m] | I'll take the action item to update that page as much as possible | 18:43 |
| JayF | #action spotz[m] to look into updating https://docs.openstack.org/install-guide/openstack-services.html and report back to TC post-holidays | 18:44 |
| JayF | Any other topics for Open Discussion? | 18:44 |
| gmann | remember we still have releasenotes link error for release name vs number. added in tracker too | 18:44 |
| gmann | and frickler has pushed some changes for that. | 18:44 |
| gmann | mentioning here as that is also known broken doc link | 18:44 |
| spotz[m] | Someone just remind me how far back we need to keep there:) | 18:44 |
| JayF | https://releases.openstack.org is the canonical source | 18:45 |
| JayF | which says back to stein right now, until a month goes by, when hopefully it'll say "Victoria -> unmaintained" | 18:45 |
| JayF | as the last one :) | 18:45 |
| spotz[m] | Stein thanks:) | 18:45 |
| frickler | spotz[m]: train and ussuri are just up for being EOLed globally | 18:45 |
| JayF | just noting that it'll be victoria perhaps by the time you get done :D | 18:45 |
| gmann | spotz[m]: maybe we can add all EOL under new section 'EOL releases' insead of removing them | 18:46 |
| frickler | hmm, I thought stein was eol already, will check with release team | 18:46 |
| gmann | or just keep them all and adda notes to check the release page about each release lifecycle | 18:46 |
| spotz[m] | The Minimal deployment sections would over run the page but we could divide the install guide part | 18:47 |
| rosmaita | btw, i just noticed that i missed an item for the Unmaintained branch implementation status | 18:47 |
| rosmaita | https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UJ7Y76LRWTZQSSDAGMPWCCVVGGIX3TOG/ | 18:47 |
| rosmaita | ussuri and train EOL | 18:48 |
| rosmaita | (to clear them out before moving v through y to umaintained/ | 18:48 |
| JayF | Thanks! | 18:49 |
| knikolla | i have to drop off early today. If I don't see you next week in the TC meeting, happy holidays! o/ | 18:49 |
| JayF | \o | 18:49 |
| JayF | Anything else for Open Discussion, or can we all join knikolla in dropping the meeting? :D | 18:49 |
| slaweq | happy holidays knikolla | 18:50 |
| jamespage | me too - need to ship a child somewhere for 10 minutes time - have a nice break folks! | 18:50 |
| spotz[m] | Happy Holidays Kristi | 18:50 |
| JayF | that sounds like consensus :) | 18:50 |
| JayF | have a good holiday o/ | 18:50 |
| JayF | #endmeeting tc | 18:50 |
| opendevmeet | Meeting ended Tue Dec 12 18:50:24 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:50 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-12-18.00.html | 18:50 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-12-18.00.txt | 18:50 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-12-18.00.log.html | 18:50 |
| spotz[m] | I'm good, I'll get some kind of draft together for tht page | 18:50 |
| slaweq | o/ | 18:50 |
| knikolla | \o/ caused a mass walkout, yay | 18:50 |
| gmann | jamespage: me too :) | 18:50 |
| gmann | happy holidays! | 18:50 |
| JayF | knikolla: I've been waiting for someone to do it for 15 minutes ;) | 18:50 |
| knikolla | you're welcome :) | 18:51 |
| spotz[m] | hehe | 18:51 |
| JayF | agenda is cleared for those who needed to add absenses :) | 18:52 |
| TheJulia | knikolla: Well done! :) | 18:54 |
| spotz[m] | Ok I'm ripping out anything older then Stein that I come across on pages inside the install guide | 18:57 |
| spotz[m] | Oddly enough on the environment page there was nothing between Stein and Yoga, I'm just adding in since Yoga | 18:59 |
| *** JayF_IRCCTest is now known as JayF | 19:04 | |
| frickler | fyi regarding stein eol, it was proposed 3 months ago, but isn't completely finished yet https://review.opendev.org/q/topic:stein-eol+status:open | 20:40 |
| frickler | but even in the current state it should make sense to remove it from the install guide already | 20:41 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!