2024-10-17 Meeting notes

All public Working Group meetings follow the Recording Policy for Open edX Meetings

 Date

Oct 17, 2024

 Participants

  • @Feanil Patel

Previous TODOs

 Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

Teak Maintenance Agenda

@Feanil Patel

  • Recap

    • Focus on the Django Upgrade for the next two release.

    • Looking a coordinator for that work.

Access for teams that maintain many repos across the org

@Feanil Patel

[inform] [idea] Old ticket was closed with idea to add Celery to Support Windows. See #maintenance-wg Slack thread for details.

@Robert Raposa

  • Suggestion celery upgrades be tracked on the support windows spreadsheet.

Flaky test process. Flaky Test Process was updated to use Github instead of Jira. We need feat: add flaky-test label by robrap · Pull Request #566 · openedx/repo-tools to land. There are 21 Jira tickets that could migrate or be lost. Ideas for migrating?

@Robert Raposa

Inform, we’re migrating the old tickets and the label will exist soon.

 

There is be a new global label.

Message by eden, is this in line with the maintenance-wg?

@Felipe Montoya

  • If you are already maintaining repos, that’s fine, the target is to have all companies in the provider program support maintenance and recruiting support from those who have not done so yet.

Status of Upgrades

 

  • Ubuntu

    • Complete everywhere except for the codejail repo.

    • We did roll back from latest to 22.04 for edx-platform

    • Doubt about dependency on Ubuntu

      •  

  • Node 20

    • All MFEs support 18 and 20

    • Adolfo has switched tutor-nightly for MFEs to Node 20

      • Smoke testing seems to show no issues

  • Jest

    • Upgrade is complete.

  • Enzyme

    • Still need to update edx-platform then this is done.

edx-platform meeting

ubuntu-22.04 vs ubuntu-latest

 

Revert out updates and pins many of the jobs to Ubuntu 22.04 by dianakhuang · Pull Request #35635 · openedx/edx-platform

  • an issue with the lxml dep tree, not the OS version?

  • we need info on test failures

Related: feat: use jammy repositories to install mongo for testing and unpin lxml and xmlsec. by dianakhuang · Pull Request #35634 · openedx/edx-platform

Sumac Cut Concerns?

 

 Action items

@Feanil Patel Update elasticsearch support windows now that it’s viable again.
@Kyle McCormick Ensure that Tutor openedx image uses 22.04 for Sumac (“microservices” could use 22.04 or 24.04)
Next-edx-platform: Do we have enough info to do a mini-rca on the ubuntu-latest vs ubuntu-<version> GH Actions worker?
Next-edx-platform: Do we have a timeline with links from Diana yet?

Recording and Transcript

Recording: https://drive.google.com/file/d/1E_XuqpuFJkyiY0o20-7QYGfupdKxum4Q/view?usp=sharing

Maintenance Working Group Meeting – 2024/10/17 08:59 EDT – Transcript

Attendees

Adolfo Brandes, Andrés González, Feanil Patel, Feanil Patel's Presentation, Felipe Montoya, Jeremy Ristau, Kyle McCormick, Robert Raposa, Sarina Canelake

Transcript

Felipe Montoya: Hello. That's good.

Feanil Patel: That's probably been.

Feanil Patel: Yeah.

Felipe Montoya: I'm not see you.

Feanil Patel: Yeah. Your weather looks like a lot better than my weather.

Felipe Montoya: Yeah. At this hour I get this on right from the side. so,

Feanil Patel: But it's getting warmer for you now. Yeah, although it's never that cold for you.

Felipe Montoya: Yeah. in Columbia, It goes and comes with the wind. this week might be sunny and…

Feanil Patel: Yeah.

Felipe Montoya: And next one, it's raining and sad.

Feanil Patel: Just didn't.

Feanil Patel: Scream.

Feanil Patel: A lot of discussion topics from previously.

Feanil Patel: Ed it.

Andrés González: Hello.

Feanil Patel: And yes.

Feanil Patel: Stuff. You should all be able to Edit here and you help taking notes appreciated.

Feanil Patel: Should. That large enough. Everybody can read that, okay?

Feanil Patel: Other people can hear me. I think so, Robert. It might be on your side.

Adolfo Brandes: Yeah, I can hear you.

Feanil Patel: you can hear that.

Feanil Patel: And then you take going come back. one of these are discussions, we need to have not done this. that probably is not only there, so, Let's start.

Feanil Patel: We spoke a little bit last week about the teeth maintenance agenda. But Let's just review real quick and then we'll move to the next step.

Feanil Patel: And this is from last time Andreas. Do we need to talk more about the releases stuff? I think that's going to go to ETR.

Andrés González: This goes to Dtr.

Feanil Patel: Yeah. I'm gonna check that off.

Andrés González: Yes, I already did. Yes.

Feanil Patel: Brother had a topic, but

Feanil Patel: if anybody has other topics, feel free to add them.

Feanil Patel: Okay.

00:05:00

Feanil Patel: That sounds good. So real quick. Yeah, for A recap. Okay, there's nothing that is urgently required of our major upgrades Python. No, Django.

Feanil Patel: Grf, etc. So I think it makes sense for us to focus on the next major upgrade. That's gonna be required. Is we're gonna need to land Django by you release. So, I think last week we were talking about how we need to focus on the Django upgrade,

Feanil Patel: And that we're seeking a. Coordinating person.

Feanil Patel: For that work. Ideally, most of the work is actually Done by maintenance. But that we need coordinators somebody to coordinate that work, like I've been doing for the Python upgrade, and the Ubuntu upgrade. And the way that Brian Smith has been doing for the node upgrade. So I'd love for somebody else to take that on with some support.

Feanil Patel: The event. And I'll add on

Feanil Patel: The time we'll talk about the status of the upgrade real quick, but the info should be up to date in their tickets. Also, So I think that's it, unless anybody else wants to say anything, we are still looking for somebody to coordinate that work. If you're not sure what that entails, mostly it is sort of looking through and making a plan and telling repo maintenance, like ticketing it up in the repo so that repo maintenance know what to do. You need help with that. I'm a resource. so,

Feanil Patel: access for teens that maintain repos sarina is the discussion. Date deadline for that. I believe has passed now. Is that right?

Sarina Canelake: Yeah, we were talking about this in the comments. I didn't get any comments on it and I think I was expecting we do for core contributor voting people to comment saying, Yes, I agree with this or No, I have these concerns and…

Feanil Patel: Okay.

Sarina Canelake: I guess Robert pointed out that people had heart emoji. The post to me that's a very ambiguous thing,…

Feanil Patel: Yeah. Yeah.

Sarina Canelake: it's not a plus one button, it could kind of mean anything. but, I mean I guess by default if nobody really says anything it passes I'm not really sure what we want to do here.

Feanil Patel: I think we can move with lazy ascent on this one. I think it sounds like maybe it wasn't clear. That you should vote like that, a vote is required. And so I think we default generally to, lazy Accenture, that sort of thing. So I just gave my thumb on it, just for extra clarity.

Sarina Canelake: yeah, I guess I don't get notifications for thumbs so to me it's like not

Feanil Patel: but I think given that

Feanil Patel: I posted a new post on it.

Sarina Canelake: thank you.

Feanil Patel: Okay, but I think you can go ahead and accept it. Given that the common period is complete, and there have been no concerns about it.

Felipe Montoya: You have two.

Jeremy Ristau: Yeah, I used that.

Feanil Patel: Okay.

Jeremy Ristau: I used that button as a plus one button. Since it was the only available one. But in the future, I can Use words instead of that button.

Sarina Canelake: Yeah, so one of the reasons it's helpful to use words is that it kind of rebumps the thread up so it kind of gets people to see it if they're browsing. But yeah, I'll be more clear for future things that I want people to. Say something.

Feanil Patel: Yeah. That sounds good.

Feanil Patel: Robert. are you back into audiovisual range for us? All…

Robert Raposa: Audio. Yes.

Feanil Patel: Do you want to talk about this next idea?

Robert Raposa: Yeah, and it's pretty brief if basically there's a ticket from Jeremy, Bowman, I guess. At the time, celery upgrades were

00:10:00

Robert Raposa: problematic and throughout this idea that maybe they should actually be tracked on the support windows. And that ticket never got picked up. I'm not clear, but it doesn't look like we have an active next.

Robert Raposa: Window or next to upgrade, But it's just an idea and I'm closing out all tickets and ideas. So I'm just passing along to this group but I don't know feel if it's going to close.

Feanil Patel: Yeah.

Robert Raposa: Even with this group, but Just pressing it all.

Feanil Patel: Yeah, I'm curious to see if that information is usually available that seller yet periods.

Feanil Patel: I think one of the issues is that celery upgrades Don't publish their release timelines. And so tracking them on.

Robert Raposa: Yeah.

Feanil Patel: That spreadsheet isn't super useful Until the new version comes out.

Feanil Patel: It's not super. Yeah, I think that that is probably the reason why they haven't been tracked. Okay. Yeah.

Robert Raposa: Yeah, which makes sense although it's also reminding me that I don't know if that elastic searches on there and I don't know if this spreadsheet was ever. Updated post. Reopen sourcing or not.

Feanil Patel: I think yeah, we haven't added a new version. So seven. Eight, nine are on there yet, so that's probably worth doing.

Feanil Patel: It sounds like there's currently still work happening to. Provide millier searches and alternative to Elasticsearch course search. Which is I think one of the biggest core features that

Feanil Patel: Still uses elastic search.

Feanil Patel: but,

Feanil Patel: And then I think the next one is yours as well. You want to talk through that.

Robert Raposa: Yeah, it's mostly just an informed that I updated the flaky test process. We're in the middle Creating a new label item. I haven't seen status but there will be a new label and then the only other update from this is the migration of some of our old gear tickets to Github is In progress.

Feanil Patel: Yeah.

Robert Raposa: So some maybe one or…

Feanil Patel: Cool, awesome.

Robert Raposa: have been migrated, but the rest will get migrated and hopefully we'll have The label. Available.

Feanil Patel: I see Are you guys merged this? But nobody has ran. I think I just ran this one. I think that label should exist now. You merge, this.

Feanil Patel: I think for things like adding these labels, did you've got to get a request already, also, I'll make sure that it's done. All right.

Robert Raposa: I think there was a ticket that I think Kyle said David picked up, I haven't actually

Feanil Patel: Yeah, I think I ran this while I was adding a different label. So I think this is done now.

Robert Raposa: Yeah, it I object is there? So, that's

Feanil Patel: So in that case and there's A

Feanil Patel: it doesn't have to worry about that.

Feanil Patel: The next is Felipe.

Felipe Montoya: Yeah, that's not critical but we received the message from Eden saying that r that is in the providers program, we were going to be assigned some Repository to maintain,…

00:15:00

Feanil Patel: All right.

Felipe Montoya: and I think this was targeted towards maintenance that are not currently maintaining anything, but I just wanted to check that we're online because We're going to be contacted by the openerx leadership, to your science and repos and…

Feanil Patel: Yeah. Yeah.

Felipe Montoya: whatnot. And I was like wherever you're doing this. So I answered her saying this is how everything that we're maintaining if this was in alignment with

Feanil Patel: that's great. Yeah, I think if you're already maintaining a large set of repos like you guys are we won't be a sign like assigning new ones. This is for people in the providers program who are otherwise participating in the community right now and so we're looking to help them. take on some Maintainership, as a part of their sort of like, Being in that program.

Felipe Montoya: All right, that's good. The last thing it's mentioned a reporting and accountability. I don't know, section of the message. That was that we're supposed to submit an annual report, detailing the Number of hours that we have contributed and Reposit originally supported. I don't know what the expectation is there, but I'm trying. Okay, I see why. This would be interesting to have from the contributors from their providers. Sort of saying,…

Feanil Patel: Yeah.

Felipe Montoya: you are actually contributing to the community. But I'm trying to figure out a way to make that task not be like a super annoying thing to track. Every time that you're doing something and…

Feanil Patel: Yeah.

Felipe Montoya: I don't know what the expectation is for that report. And if it needs to its program you are or something that we can get from github or for cows.

Feanil Patel: I mean, I think what I would say is that I think you've understood the desire and if you suggest an alternative way to track that achieves that goal. then I think we would be very amenable to changing that to sort of But, I think maybe through some variation of, pull requests and reviews or some other data might be a useful way to do it. And if you think that that's sufficient then if you talk about it, but even sort of is in charge of that program and it's stuff, but we do want to align it to the maintenance stuff. So I'm happy to provide her input. That makes your lives easier so that we can spend maintaining less time writing reports.

Felipe Montoya: all right, makes sense I don't have yet, I get concrete proposal that I said this is how I want to report…

Feanil Patel: There.

Felipe Montoya: but done knowing that We're opening on the receiving end. I'll see what I can calculate that. It's not to to keep their accounting from I said, and I'll propose that in.

Andrés González: When we receive the same message and it was curious that it came from marketing. And there was wondering who is actually leading because, okay, we said, yes, we can maintenance a lot of repos and we are kind of expecting who is assigning the repose to the engineers. Yeah, who is really leading This process it's even

Feanil Patel: We're working on it together. I'm helping on the technical side and she is leading sort of the communications and process part of it. So I would say since she sort of hat maintains that program, she is making sure that that program is aware of the change to sort of help them, support maintenance more and the What repos and who. And how do we work that How do we get them?

Andrés González: okay.

Feanil Patel: Yeah, the goal is to even