Maintenance Working Group Meeting (2024-08-15 08:59 GMT-4) – Transcript

Attendees

Awais Qureshi, Brian Smith, Feanil Patel, Feanil Patel's Presentation, Maksim Sokolskiy, Michelle Philbrick, Regis Behmo, Robert Raposa, Sarina Canelake, Syed Muhammad Dawoud Sheraz Ali

Transcript

Brian Smith: Hello. How's it going?

Feanil Patel: hey, Good. How are you doing?

Brian Smith: Doing Emily woke up and was like, I need to make sure that I have the links ready in now the post of my standard I can get the 9am till a little bit later to figure out what I need to have together for my first meeting of the day.

Regis Behmo: without

Brian Smith: Are you hard? meal

Brian Smith: I can't hear you for Neil.

Regis Behmo: This call is being recorded.

Sarina Canelake: Max where did everybody in raccoon game get such awesome backgrounds.

Maksim Sokolskiy: from our designers

Sarina Canelake: I've been really enjoying them.

Maksim Sokolskiy: Yeah. You have several different options to choose from.

Sarina Canelake: I've seen this one and the one with the two raccoons like working in an office.

Brian Smith: Yeah, but raccoons taking advantage of the opposable thumbs is a great touch.

Maksim Sokolskiy: Yeah. strategic decision

Sarina Canelake: I see feanil's not here.

Brian Smith: He was but all of a sudden he was having microphone issues and so we could no longer hear him. So I think he's trying to fix that, right?

Sarina Canelake: I'm wondering if we want to pull up the agenda and start going through it.

Robert Raposa: IT industry, right

Sarina Canelake: That's all it took was and…

Feanil Patel: things are still loading.

Sarina Canelake: We said that your name three times, I think.

Feanil Patel: But yeah, I think this should be better. Yeah, that looks right.

Brian Smith: Yeah.

Feanil Patel: Let me share the agenda.

Feanil Patel: Max I like that you have a version of you in your background. with the raccoon

Maksim Sokolskiy: exactly as a guy also raccoon

Feanil Patel: The guy and…

Maksim Sokolskiy: Okay.

Feanil Patel: the raccoon it's sometimes gets cut off.

Feanil Patel: But yeah raccoon is great.

Feanil Patel: All right. Let's see. Let's get going.

Feanil Patel: grab the previous to do is really quick.

00:05:00

Feanil Patel: And we talked about the Enterprise.

Feanil Patel: Okay, so I'll put that on the agenda the Enterprise maintenance and debtor.

Feanil Patel: and see what else we got, so

Feanil Patel: I think Igor and Glee have the checking on the cookie fallacy Banner enzyme replacement stuff, which is on their plate as far as I know and they're gonna try to take care of it the next couple weeks. Max I don't know if you have any updated data on that. but I got confirmation from them last week. So I think this is in progress, but we'll just have to check in on it. It's one of the last things left on the enzyme upgrade. So I want to just Get It Over The Line. It's like this and a couple of commerce repos, which I'm gonna have Adolfo and myself look through and finish up.

Feanil Patel: And then the front end related Decker tickets Jeremy. I don't think has a chance to create those yet. And I think children hasn't been around for a little while. So I don't know if this is still super relevant, but all slack him later and see if he's still going to be doing this.

Feanil Patel: And then Brian, I think you and Adolfo are in the process of writing these Dipper tickets. I feel like you've drafted this at this point. I don't know if it's public yet. the Dipper for the footer

Feanil Patel: Okay, awesome.

Feanil Patel: And that's all of All right. the next thing on here? Is would you deprecation which I realized last week is the thing we need to land for sumac.

Feanil Patel: so this is I think a

Feanil Patel: lot of our systems are currently testing on a bunch of 20 to 20.04 which I think will go out of support before we cut teak which is what makes it urgent pursue Mac. We could land it for sumac one or two, but I think aiming for assumack is probably the right answer given that is a large change. I've started taking that up. It looks like it's not everywhere as I was taking it up. I was also thinking about sort of our current goal around the six-month stepper for large changes to give operators who are running sort of near-master time to change and whether we should be doing a matrix for this or whether it makes sense just to start testing on the newer version.

Feanil Patel: I think for a lot of our libraries and things that don't think it's super valuable which version of Ubuntu we're testing on because we're not actually making use of Ubuntu. So I think for a lot of the libraries my thought was we would just Update GitHub to use Ubuntu latest and as long as the right python version and libraries exist. That's probably the sufficient test. exceptions include code jail, which uses the underlying app armor setup on whatever machine the application is running on and so that we would want to test all of that works correctly on whatever version of it, but We want to support.

Feanil Patel: yeah, what do people think about? Not doing this excellent depper on most things but then perhaps doing it on. Edx platform I think is one place where we would want to do it because of the potential of app armor conflicts. But if there are no conflicts, maybe we don't do it there as well and just start testing on the new version if there's no major changes.

Feanil Patel: Looking for feedback.

Robert Raposa: Are the tests the only actual change?

Feanil Patel: What do you mean?

00:10:00

Robert Raposa: I guess it'll depend what we'd switched right and…

Feanil Patel: right

Robert Raposa: if we find things and things actually have to change whether or not it would be useful to have both versions running and I mean, I have experience being around when we've done these upgrades,…

Feanil Patel: gotta go.

Robert Raposa: but I've no experience with the actual upgrades and…

Feanil Patel: Yeah. Yeah.

Robert Raposa: what kind of problems Have not Arisen and whether or not so I don't know if it's like This is absolutely fine because we've never seen anything except for here or here.

Feanil Patel: The things we've seen are sort of more operational rather than in the code itself. So With some of the previous Ubuntu upgrades for example, the version of python that we are supporting is not the version of python that's available on that Ubuntu. So you have to make sure that whatever version of python you want is available. But that's like again. For example to you that would be in your build systems Robert not in something that we could change on this side.

Robert Raposa: Right, but I get the question is. and there will be no changes in the code that matter so it's really We think on our own time. making

Feanil Patel: Problem. Yeah.

Feanil Patel: Right, but I think the question is I think there won't be code changes except potentially in code jail.

Feanil Patel: That's the only library that I'm aware of that sort of makes use of. Underlying Ubuntu app armor essentially. And so that's the one where I could imagine if app are American figs have changed your app armor sort of set up has changed in some way that we may need to update. How code jail Get set up.

Feanil Patel: But other than that, I don't know if it's super valuable to be running on both versions of Ubuntu for our libraries and our services.

Robert Raposa: yeah, and All I mean I can Reach out. I can't add Anything in terms of potential problems. I don't see any because I don't know…

Feanil Patel: Yeah. Yeah.

Robert Raposa: what there would be and the code Jill issue. I'll bring up because I know we already have to do something for code jail.

Feanil Patel: Yeah, I think you guys still need the python 311 upgrade there.

Robert Raposa: That So that's possible. I don't know if it's possible or makes sense to combine the two or not.

Feanil Patel: Yeah, definitely. I mean, I would even say if you guys can consider going to three 12 directly and save yourself one more upgrade that we're going to need to do in the next six to 12 months.

Robert Raposa: Yep, reach out about that possibility.

Feanil Patel: Okay. Yeah.

Feanil Patel: Any other thoughts?

Regis Behmo: So this group is not concerned about the upgrade of the base images in tutor. The fact that we'll have to hold the base images in Twitter are most of them are based on Ubuntu 2004, but that doesn't fall under the umbrella of this work group, right?

Feanil Patel: Right. I mean part of the reason I think that we ask for you to be here as she says that that's totally a tutor decision but the testing and the place where we know what we're like we'll know about issues is in whatever version of Ubuntu where testing with so if there's thoughts about Tutor switching to other images we should definitely Figure out if we need to change either our testing strategy to match that or tutor is okay with taking on that risk of differentiation on the tutor side and tutor testing of the edx platform. So that sort of my big concern about bifurcation

Regis Behmo: Yeah, I hadn't realized that there might be a difference between the testing environment and the broad environment. I mean, I know that I mentioned the past that it would make sense to migrate the discovery service to a different base image. But it's a whole different ballpark for any platform. so I think it would make sense to keep

Feanil Patel: Yeah, yeah for sure.

Regis Behmo: but you went to base image.

Regis Behmo: Yeah, though this is what it would be discussed on slack. And do you have different opinion on this?

00:15:00

Feanil Patel: But And my thought is for edx platform and other things to try. It looks like GitHub now has a 2404 image. So I was thinking we would try to just jump directly to the 2404 image for the major services in testing at least.

Feanil Patel: That will hopefully sort of save us some future maintenance woes. It was a little bit longer Runway to plan some of these things.

Robert Raposa: I'm sorry, is that what the Matrix? Proposal was to update for testing.

Feanil Patel: yeah, yeah, so all the ticketing that I've done so far is Actually, just open that up. is on the suggestion of let's move to 2404.

Feanil Patel: And so this is fresh. I just made these yesterday which is here's the prioritize release proposed. I'm trying a different thing where instead of having many layers of tickets. I just have one top level ticket with lots of grouped task lists for different Things right now. It's just that release the major services that are in the release are at the top here. So we know what the state of those is and everything else that has an Ubuntu 2004 test is down here. Looking at the full list part of the thing that I noticed is that a lot of these things are things like the publishing step…

Robert Raposa: Good.

Feanil Patel: which we can't really do in two images. we shouldn't publish twice. it'll fail on one of them. Anyway, so I think there's gonna be a lot of just switching from and also the publishing set doesn't require us to be on the correct version of the day. That's not relevant. so the way that I wrote a lot of these tickets

Feanil Patel: is with guidance if it doesn't make sense to switch to a named image and named version. Then consider switching to Ubuntu latest instead and let GitHub manage the upgrades of those. So if you're in a library where it doesn't what's that Robert?

Robert Raposa: I didn't actually say anything and I will go on you it just

Feanil Patel: All Yeah, and this is hopefully to sort of reduce our future maintenance Burton for things like publishing things like blending where it doesn't necessarily matter which version of the underlying system or on we just stick to latest and let GitHub do the upgrades of those latest. I think right now is Ubuntu 2204 for the GitHub images, but I imagine that today is when the point one release of Ubuntu 2404 comes out. So I suspect that in the next couple of months. They'll be starting their migration from 2204 to 2404.

Feanil Patel: for their latest

Feanil Patel: so that sort of the recommendation in the ticketing.

Feanil Patel: so as if you're maintainer of something I'm gonna post this on the forms as well to ask maintenance to sort of pick up the ones for repos that they're maintaining and get these landed before.

Feanil Patel: Before the sumat cut off, which I think we still don't have an official date for but it's looking like sometime mid-october.

Robert Raposa: and actually just sorry that the part that you're just talking about in terms of uber to latest you said sometimes is that at a repo level decision that you're talking about uses of it within this

Feanil Patel: at a workflow level Yeah, yeah, publishing is a good example linting is a good example. There's often other workflows that exist that are using 2004 just…

Robert Raposa: second

Feanil Patel: because that's where we started and I think switching to latest rather than trying to keep them up do this maintenance over and…

Robert Raposa: yeah, hey,…

Feanil Patel: over again, we'll reduce our maintenance certain. So I'm just asking whoever's taking on those tickets to Think about it.

Robert Raposa: I didn't get through the full text of that last note, so I didn't know what if

Feanil Patel: And here let me I'll post it in the chat too.

Robert Raposa: but he didn't have the Latin.

Feanil Patel: So you can access it.

00:20:00

Feanil Patel: Yeah, and I link them to the maintenance of if you're not sure. Come ask and we'll provide guidance.

Feanil Patel: Okay. this

Robert Raposa: so the best one last question I know in the past, our rebound Has pushed out changes across. Many rivers using automation is that the kind of thing that might make sense for certain types of workflows or…

Feanil Patel: Mmm Yeah

Robert Raposa: is it? So it's a question.

Feanil Patel: Yeah, that's a great question. Maybe I think I need to go look at that automation to see if we can make pull requests for some of these things and just update all publish workflows to use latest instead of whatever it's using right now. For example.

Feanil Patel: I think that. there are enough other workflows the CI workflows that need updates that You're gonna already be in there and these are small changes to make there and having a separate PR might not be as useful as just making the change in one PR that tracks the one ticket.

Feanil Patel: but if I think part of it is like I'm not sure what that automation looks like for this next thing. I know that we have a bunch of stuff and repo tools and then dot GitHub to run PR generation so I can take a look at that. But if other people know and want to help with that, please let me know.

Feanil Patel: yeah, if Somebody wants to look at just generating pairs across the whole board. That would be interesting and useful. I just haven't like this is yesterday into there the first time I've gotten to spend on it, so it's still early days.

Feanil Patel: But I wanted to at least get the tickets out there. So that maintenance can be aware that this needs to happen. And if they want to, get their repos Done ahead of other things that would be useful. I know that we're at about a third of our repos or maintained right now.

Feanil Patel: And so for the other two-thirds automation is probably useful and I'll probably start looking into that at some point.

Feanil Patel: But I haven't had. What's that?

Feanil Patel: What? Yeah, that'd be awesome. All right. Any other a bunch of related thoughts?

Feanil Patel: Brian you wanna fill us in on what's going on with the nude upgrade?

Brian Smith: Yeah, absolutely. If you click on that link, I think that'll actually be helpful.

Brian Smith: So yeah, if you scroll down to the tutor supported mfe's part,…

Feanil Patel: Okay.

Brian Smith: you'll see that Adolfo has done a great job of going three through and making issues on all of these mfe's for what needs to happen for the node 20 upgrade and those are just issues saying follow the upgrade process that is described earlier in this issue. So if you scroll up you'll see that the first thing is add note 20 to the test Matrix so that way we're testing 18 and…

Feanil Patel: Yeah. Yeah, so just do this.

Brian Smith: 20 side by side and then fix any failures and then update to node 20. And so

00:25:00

Brian Smith: yeah, that's kind of the path forward for doing all of this. It's kind of a three PR thing. you can see in the front end template application. One that's down. In other mfe's Adolfo is already gone through and done that for front end template application. So we've got that as great examples of what each one of those are so there's add node 20 upgrade to note 20 and then remove support for note 18. Those are kind of the three steps. yeah, so I'm

Feanil Patel: Cool, and those PRS are there notes?

Brian Smith: I'm hoping that this isn't something that I'm going to do all of these PRS on my own. So if anyone wants to dive in the first thing that would be super helpful is just getting some of these add note 20 to the CI Matrix PRS out those should be pretty straightforward and then I am more than happy to make sure that I can help everything along but if helping everything along doesn't mean doing all of the coding and pring and everything all on my own I would be very happy. So yeah.

Feanil Patel: Yeah, I want to make notes on the removing 18 support is that that's the thing that should go through the sixth month deprive process. Yeah.

Brian Smith: Yeah, So those PRS I still want them to be out but just like her PRS could just be sitting there and then be based on or…

Feanil Patel: yeah, but Yeah.

Brian Smith: ready to do it. Yeah.

Feanil Patel: That sounds great.

Feanil Patel: Yeah, I think it's probably worth updating point for here to sort of be clear that don't merge this until you might want to step in between three and four here, which is create the Creator update the Decker ticket.

Brian Smith: Okay, cool.

Feanil Patel: on this

Feanil Patel: because I think if you make one Decor ticket, which is tutor supported mfes are dropping note 18. We can put that in draft and then have each of these services update that with when they're ready. And then once all of the services are done we can Announce that and start this six month timer at that point.

Brian Smith: Cool, I have updated and added a step for there. It is. Bare Bones, but it's there.

Feanil Patel: Cool awesome.

Brian Smith: Yeah. exactly

Feanil Patel: Yeah, you can fill it. And cool Yeah, I think that makes sense in that way. Yeah, the 18s PRS will hopefully all exist and we can drop them. Whenever in January or something.

Feanil Patel: Okay.

Feanil Patel: 're at just about time on this. The last thing I did want to chat about from last time was the Enterprise maintenance Endeavor, which is I know we've gotten some. conversation

Feanil Patel: Around deprecating Enterprise. and I'm sort of looking for more feedback on what people think about this because I know there are people who are using Enterprise and maybe I know the people who are using Enterprise are mostly not here. So maybe I'll just put this back on the discussion forum for people to talk about because I think that is more useful.

Feanil Patel: All yeah, so I'll put an announcement.

Feanil Patel: on the discussion forums instead because yeah, my current thought is that there's interest but not enough interest to sort of sustain the amount of repositories and maintenance that is necessary to do in the Enterprise space and most people are using in the very small subset of what's there. So Perhaps we should. Deprecate this and just start working on the thing at people actually want.

Feanil Patel: Which might be useful for the first to you as well because then that's like a thing. They don't have to figure out.

Feanil Patel: All right any other? Things. Otherwise, we'll move into edx platform specific discussions.

Feanil Patel: Thanks, everybody. Super helpful. Yeah, if you are maintenance or no Maintenance, please have them take a look at both the node and a bunch of upgrades. We need them both landed also. Brian and realizing you didn't have the backend services Node on that list could we add a list of the services that need the note upgrade as well? edex platform already did it but other services like Discovery and credentials? I think also have npm.

00:30:00

Brian Smith: Yeah, I think that shows up in this issue which has the Django Services then released mfes than the release JS libraries and tutor MFE.

Feanil Patel: I got.

Brian Smith: I'm specifically looking for help on the MFE side of things right now.

Feanil Patel: Gotta okay.

Brian Smith: So we do have a larger tracking issue for all of that.

Feanil Patel: Got it.

Brian Smith: But from a here, this is Well defined we already know what we need to do for every MFE and we have a good example for it.

Feanil Patel: Yeah.

Brian Smith: So it's something that's easy for people to pick up and dive into that's what I was hoping to bring to the group today.

Feanil Patel: right Got The MF fees are easy for other people and you that's what people should pick up first. And there's also a more complicated part that you're looking into. Got okay,…

Brian Smith: Yeah, exactly.

Feanil Patel: awesome All right. Thanks everybody. If you want to talk about a platform stick around. Otherwise, have a good rest of your day or night.

Feanil Patel: expect Yeah.

Feanil Patel: That'll be just us chickens.

Feanil Patel: is there anything specific you want to discuss Robert? Otherwise, we can actually just call it here.

Robert Raposa: Yeah, maybe calling it. I can't remember if we had any topics that we didn't get to.

Feanil Patel: Yeah, there's last week. We talked about the front-end stuff, which I think. We're sort of in the process of and we started doing some more work last week at Deborah.

Robert Raposa: And I think I wanted to dig into the resilient City topic a little bit more,…

Feanil Patel: Yeah,…

Robert Raposa: but my Kyle's here.

Feanil Patel: we can wait till next week. Yeah.

Robert Raposa: Maybe we could just add in no resiliency topic postponed against so we can see that. Or you can have an action.

Feanil Patel: Yeah, I'm just gonna

Feanil Patel: do this.

Feanil Patel: And This seems like it works pretty well for remembering next time perspective. I'm gonna check off.

Robert Raposa: Yeah.

Feanil Patel: This one, so just move that to a discussion. Okay.

Feanil Patel: Okay.

Robert Raposa: That's good.

Feanil Patel: Okay, All right, and then we can just call it there today and we'll just continue next week and pick it up then. All…

Robert Raposa: That's it. Thank you.

Feanil Patel: Thank you.

Feanil Patel: but

Meeting ended after 00:33:43 👋

This editable transcript was computer generated and might contain errors. People can also change the text after it was created.