edx-platform Maintenance  Sub-Group (2024-07-18 09:07 GMT-4) - Transcript

Attendees

Adolfo Brandes, Awais Qureshi, Feanil Patel, Feanil Patel's Presentation, Felipe Montoya, Jeremy Ristau, Large Conference Room, Maksim Sokolskiy, Michelle Philbrick, Robert Raposa, Sarina Canelake, Tim Krones

Transcript

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

Jeremy Ristau: right

Feanil Patel: Look at work. We summoned him by starting the recording.

Feanil Patel: All right, welcome to the next platform maintenance followed by the maintenance working group in 30 minutes or so. Probably more like 20 minutes now. First thing. Yeah, we're gonna swap these meeting times next week. I realize that we talked about it, but then we were radio silent for two weeks. I just wanted to give everybody a little bit of extra time. I given that Tim is the only one who showed up. I feel like that was the right move.

Jeremy Ristau: Mm-hmm

Feanil Patel: So next week maintenance working group will be at this time. And this meeting will be 30 minutes. Later. The only other thing that I wanted to talk about for edx platform stuff, which is small but big is reminder that there's the potential maintenance models spreadsheet, but the sort of thing that I want to talk about is what do we want to do in the meantime? Do we want to accelerate picking something so that we don't have a mean time. Do we want to pick up something in the meantime? Do we want to have just Let things go as they've been going currently that's sort of the conversation. I wanted to have today.

Robert Raposa: I can't remember exactly. I think I just do that

Feanil Patel: You're fine.

Robert Raposa: I'm getting out of there. I was just trying to click on the link and I feel like the last time we spoke about this. there wasn't action item or next steps that was going to happen to clarify something, but I don't remember so maybe if you could Summarize or if we could look through and…

Feanil Patel: Yeah.

Robert Raposa: find what was the summary of our last discussion?

Feanil Patel: Yeah, yeah, we can let's just go back to our previous meeting and take a look.

Feanil Patel: Looks like we didn't write down very much.

Robert Raposa: Didn't actually know them or anything.

Feanil Patel: Yeah, there's no action item or anything.

Robert Raposa: products or maybe running together that some point

Feanil Patel: He I think we talked about the thing. I do recalls that we had talked about. what are the different models that we want to have for the maintenance how we distribute maintainership which is I think one aspect of this and then sort of like how do we coordinate across all of those maintainers and Ensure that the top level targets are being met. rent, so

Robert Raposa: It's now I remember that the constraints sections at the top is what we were discussing. that's where So those are probably like the notes.

Feanil Patel: really, right Okay.

Feanil Patel: Yeah, yeah.

Robert Raposa: Of hey, what are we actually trying to solve for from this thing?

Robert Raposa: to answer just

Feanil Patel: right yeah, and some of these will feel like is what was the notion? I think is there something that's an owner that's different from maintainer Jeremy I think you would sort of started talking about this because there's this notion of To you internal owners, but those might not always be the maintenance. I don't know if there needs to be a community concept of an owner of independent of maintainer if that's just an internal to you notion.

Robert Raposa: both or whether there was could owner maintenance is there anyone would?

Feanil Patel: Right, right. That was the second question, which is like can someone be in code owners without being a maintainer and I think

Robert Raposa: yeah, and

Large Conference Room: negative second again access to this

Feanil Patel: I

Large Conference Room: Thank you.

Feanil Patel: yeah, I think code owners for notification is useful and then get it implies.

Feanil Patel: a different way of tracking the maintenance

Large Conference Room: I remember when to you and accent slip first had floated this idea of there being a difference between maintenance which is a open edx wide concept and operator owner, which is really the discretion of different people running a platform in that second thing is much more about handling incidents for that particular website and I could totally imagine that someone like to you would need. essentially assignments on call owners for everything whether or…

00:05:00

Feanil Patel: right

Large Conference Room: they maintain it and maybe the fix gets delegated to the community level maintenance. Once that they incident is the immediate incident as a result. I think that's what I was thinking back then. I don't know what your guys is thinking is now.

Robert Raposa: That I mean, I think what you said applies to what someone else's concerns, Their maintenance buttons to you originally about owner versus maintenance in this first question. I think these two questions I think I remembered document writing them that they were in my head,…

Feanil Patel: right

Robert Raposa: but I didn't know what the answer was or what it meant.

Feanil Patel: Yeah.

Robert Raposa: I was just something that Jeremy might have said so Jeremy is there anything other than what's been said so far? That comes to your mind when you think about owner versus maintenance.

Jeremy Ristau: I mean those are certainly the ones that jump out in my head as the main use cases. There's internal instance owner and then there's code to maintainer. in the project

Feanil Patel: mmm

Jeremy Ristau: there's also stakeholder But That feels farther away from this problem. I mean

Feanil Patel: Yeah.

Robert Raposa: Yeah, so does inserting the operator or it either operational owner or having some other term for operational owners that a good way to

Robert Raposa: describe this

Robert Raposa: I meant I'm saying it because I all said it and it rung through with me exams sounds like they're useful. term

Large Conference Room: I think much like courses ambiguous at this point owners and videos at this point. And operator owner or…

Robert Raposa: Yeah.

Large Conference Room: operational owner has lived making it obvious what you're talking about.

Robert Raposa: Yes.

Feanil Patel: I think code owner in this case is same as maintainer.

Feanil Patel: All right, cool. Nobody disagrees. I must be right.

Jeremy Ristau: So if we take the socks Constraint as an example.

Feanil Patel: Yet.

Jeremy Ristau: Tnl would want to be notified whenever changes Happening in a specific file,…

Feanil Patel: right

Jeremy Ristau: but they would not want to be considered the maintenance of that.

Feanil Patel: Right, they are not blocking the changes to that file on their review or they're not maintaining the sort of architecture of that file. They just want to know when it changes so they would use the co-owners file to Be notified.

Jeremy Ristau: Yeah.

Feanil Patel: But they would not be listed as the owner for that I think that.

Jeremy Ristau: You got your last but implying a different way of tracking maintainers. We would use code owners.

Feanil Patel: red

Jeremy Ristau: as the current mechanism for notific

Feanil Patel: Right, right.

Jeremy Ristau: Yeah of monetary.

Robert Raposa: but not

Feanil Patel: yeah, and…

Large Conference Room: and that's

Feanil Patel: I think there's a question in my head about I think we can't have multiple sections, but I wonder if we can sort of be clear about Using comments and whatnot of this file is being monitored by this team. But also this whole folder is owned by this other team that might actually be difficult to do with code owners since it uses the GitHub ignore sort of syntax.

Jeremy Ristau: You can have more than one code owner for the same file slash directory. and they do not have to be in order. Correct. So could we have a maintenance section of code owners and then a non-maintainer section of code owners?

Feanil Patel: Yeah, the question is I thought that it essentially matched on first.

Large Conference Room: things that

Feanil Patel: Or whatever the final thing was the only thing it would match against. I don't know if it would combine somebody's watching this folder and somebody's watching this file. Do I notify both of them when? File this folder changed or not. So there's some outstanding questions about the implementation that I have.

00:10:00

Jeremy Ristau: right

Large Conference Room: I mean You're right. I also think we could get around this but I think most coat owner assignments are going to be maintenance and this sense of we just want to send a notification is going to be the exceptional case. So we could just have a comment whenever someone like you could have one line that says.

Jeremy Ristau: Yeah.

Large Conference Room: Student app maintainer hypothetically open graphs Notifier tnl and just have a common explaining that special case.

Jeremy Ristau: Yeah. If it got cluttered enough, you could in fact, yeah.

Feanil Patel: And then Kyle you said you weren't sure about this code universe is maintainer. You want to talk about that?

Large Conference Room: Yeah, because if we have the co-owners file that isn't always going to map to maintenance. I don't think we should call maintenance code Hunters. I think that's going to muddy the waters.

Feanil Patel: Yeah.

Jeremy Ristau: Code owners is a tool right that maintenance can Leverage.

Robert Raposa: agree, and also operational letters can Leverage

Jeremy Ristau: Yeah, right. Yeah.

Feanil Patel: remove your not sure about this since it's not accurate anymore, but I think that's

Large Conference Room: I don't know how much we want to drill to specifics we could use the code owners plus comments to be basically the catalog in photon yaml for edx platform maintenance. I think that'd be nice but not super opinion about that. It could all be a reputation.

Feanil Patel: and it also gives The ability you gives us extra benefits if we use it that way because if you're looking at a file and GitHub, there's a little icon at the top that lets you see who the code owners of that file going from back to code owners is really easy, which is a really nice feature.

Feanil Patel: So yeah, I'd be Pro that as the mechanism. it's nice because the mechanism is now pretty agnostic of how we split up the platform.

Feanil Patel: 

Robert Raposa: Do we need to test the notification? just how it works. in terms of multiple listings

Feanil Patel: I mean, I think as Kyle said we can just work around it with comments for now…

Robert Raposa: Comments like on a single.

Feanil Patel: if we need to.

Feanil Patel: above the line where it's like a lot of people are getting notified about this. This person is the owner. These other people are just interested operational parties.

Robert Raposa: Yeah.

Feanil Patel: And that's nice because that is sort of to you agnostic as well. Because if other operators want to know we did learn finally confirmed that MIT does run an edx platform that is not act Master but a couple weeks delayed. Was that right Kyle?

Large Conference Room: Yeah, yeah there and they're three instances the mitx online instance, which is meant to be similar to http://edx.org it lags somewhere between two weeks and I'm off behind on any time and Peter pinch basically goes through recent changes every couple weeks and…

Feanil Patel: Yeah.

Large Conference Room: merges them in to their Master Branch. So yeah, they're like Master adjacent.

Feanil Patel: so we have now two examples of near-master that we need to that. We should sort of build into our operating room.

Robert Raposa: Is this accurate? Okay.

Robert Raposa: 

Feanil Patel: Yeah, they feel that good.

Large Conference Room: are we going to use code owners to block review or is it going to send a notification and then we just kind of use Community guidelines that encourage people to get the proper reviews.

Feanil Patel: I lean towards notification rather than blocking because that allows cc's to jump in on reviews as well.

00:15:00

Large Conference Room: The point yeah.

Jeremy Ristau: Yeah for the socks case Sarina actually told us we're not allowed to be blockers. So if we used code owners for that, we wouldn't like right now. It's set up as notification or it auto adds us as a reviewer,…

Feanil Patel: Right as a review.

Jeremy Ristau: but Yeah.

Feanil Patel: yeah, and I think we've sort of been pushing people away from Go to owners for blocking reviews like we changed that A couple of other repositories that had it because it prevented CC's from merging changes.

Feanil Patel: So it's sort of circumvented. the whole reason that program exists

Robert Raposa: Okay.

Feanil Patel: So I think another question I have is The other concern is this tragedy of the commons with many maintenance and many task issues directories. and that feels like a place where we might just need to do some extra up front work to make it clear

Feanil Patel: Is this a situation where we're going to need a sub ticket or subtask for each owner so that they can Do those things? because I'm thinking for example We have a bunch of Django five warnings right now right in the platform. And a thing that I could imagine us as the maintenance doing is taking that list and producing a series of tickets. for all of the Django 5 related warnings that we need to fix before we can upgrade to Django 5 2 And that could be done today because the five zero and five one warnings are happening right now. We could collect them. We could produce tickets out of them and that work can be farmed out to both to the whole Community today. At some point I'd like to be able to say something as the maintainer of this section you need to. Make sure this gets done by this date.

Feanil Patel: So that we can complete this upgrade.

Robert Raposa: Okay.

Robert Raposa: Question I have is I mean just with this degree. I mean, maybe it's fine, but just have all the tickets no matter what but I don't know will our baby bum.

Robert Raposa: doing certain types of work across a bunch on behalf of other maintenance, this is a question to Jeremy and is that list of thing that could be knowable and that helps the maintenance working group not or is it like whatever? the maintenance working group should ignore that we'll just do exactly what Neil said create a bunch of tickets and then If we want to consolidate on our side, we'll just do that. However, we wish.

Jeremy Ristau: I can. Say what? I think my perspective is I don't know if it's what is happening or should happen.

Jeremy Ristau: But I think what I see as the future way of working for this is

Jeremy Ristau: we've allocated As much RB bomb time as is needed to help enable these kinds of things for the community. and I think what I would say is In the future if we turn that around instead of saying hey to you, what do you gonna be doing? It's more. Hey open edx Community what needs to be done? And the open edx Community uses the depress us now and uses all of the mechanisms that we've been talking about to let everyone know what needs to be done. And then can say this seems to be the set of things that aren't moving as fast as we want them to move can The two you allocated time help augment and progress that stuff forward.

Jeremy Ristau: So more of an available set of resources that you can leverage when you need and you are not leveraging them. We leverage them for what we need or want to accomplish and they are available for injectable work like whatever you need with some small period of heads up and as much of it as is roadmapable or planable as possible is great no 20 is coming and that's something that the team is very familiar with can we push node 24 forward on all of the edx repos and then look to the open edx repos? Yes, absolutely and so I think right now it's more of a

00:20:00

Jeremy Ristau: Collaborative. Where are we going to land? what's actions a resource going to do our going to do what's the community resource going to do and in the future we'll essentially just Harden that model more.

Feanil Patel: Yeah. Yeah anything.

Large Conference Room: like that

Feanil Patel: Sorry good.

Large Conference Room: Down on that resonance with me. I think that also.

Feanil Patel: Yeah.

Large Conference Room: sounds like a good model for core contributors to the edx platform in general as a community working group, we decide what are the maintenance priorities for X platform and everyone who was right access to edx platform. Has this pool of personal resources are coming resources. They can commit and they work together to Make that happen.

Feanil Patel: right

Jeremy Ristau: exactly

Feanil Patel: Yeah, and if we look at I think the python upgrade as an example of this one of the things I did early on was create a ticket for every repo that I was like, these are all the ones that actually are in the release neuro priority. If you're gonna work on it assign it to yourself and start work on it. I don't need to decide what you work on as long as you're working on something in this list. This is the important list.

Robert Raposa: so From the edx platform side I have ever created. to get for every app or…

Feanil Patel: Not yet. No this new on that side.

Robert Raposa: not right,…

Feanil Patel: So I think

Robert Raposa: so I think

Feanil Patel: as easy

Large Conference Room: Go ahead everybody.

Robert Raposa: I was just gonna say it sounds like two options for doing that kind of ticketing would be literally a ticket for every app and every section that we want to do something for and see how that goes. And another one is to once we get the maintenance. and in the code on our file to do a ticket for maintainer with everything that they make games so that there's fewer tickets and then can Parts it up more. it's

Large Conference Room: so Before we get too deep into that. I want to push back on the idea that we should break up these sort of EX platform on things. if there's a bunch of Django five warnings. I don't think it actually accelerates anything to have 12 to routines do them. I think it actually makes a lot of sense for a single CC RV Bond could be another excellent cc to take that for the entire platform because it's going to be a really repetitive change and then we only break up the things that take Focus work. To the sub apps. It's

Feanil Patel: Yeah, I think that makes sense. I think a reasonable sort of demarcation might be. On warning type I think that's what you're suggesting Kyle. or

Large Conference Room: I think it's more about depth of change superficial Things that can be automated or done in bulk really shouldn't break in a broken up. That's just Maybe more work for everybody but things that are like there are bugs. s about that makes sense delegates that the maintenance

Feanil Patel: Yeah. Yeah, we might have to try this out before we come to a conclusion about what we want to do. But honestly during the Django five might be a good test case because I think we already get Django five warnings in the platform and we already have a bunch of other warnings in the platform that we could sort of use this as an operating model to try out.

Feanil Patel: It's cool. Just make that note there. And then we'll get started with. so I think there's more to talk about there, but let's talk about more of that next week because I think that there's still sort of more iterations of that that we want to do. But let's move to the full maintenance working group meeting. Hi everybody. Welcome back. And reminder first and foremost that this meeting is going to be 30 minutes earlier starting next week.

Feanil Patel: It should be updated on the working group calendar. So if you're following that you should just be able to see the new times on there, but we're gonna swap the two meetings here so that the edx platform one follows instead of proceeds this meeting mostly for the sanity of my brain where I think it's helpful to have the bigger conversation and the smaller one, but hopefully that doesn't mess up people's ability to come to the meetings at all. If they do, please let me know.

00:25:00

Feanil Patel: cool Back first big thing is frontend app learning is Seeking a new maintenance. This is the MFE for what the learner sees inside a course so slightly important for the open of X platform.

Feanil Patel: There's a post here. If you are interested in becoming the maintenance of this application, please post a response there. thank you and we'll do action item review just so I can also.

Feanil Patel: But yeah, this is kind of the big important thing I know open craft was previously interested. And I know that there's a bunch of open craft pull requests on that repo. So if you guys want to take over maintainership and just hit the merge button a thousand times, this is your chance.

Tim Krones: Yeah, I talked to a brain about it briefly considering that he is going to be getting a cc access to or believe all the front end repos, but it…

Feanil Patel: Yeah, I think he has it now.

Tim Krones: What's that? Okay. Yeah, but it wasn't conclusive he wasn't legally sure he had room to take that on but I can double check with the team.

Feanil Patel: And if you have partial capacity and it would be helpful to have sort of a second person from a different group or different organization. if you have a 50% over there and you need some more post about that on that thread as well because maybe we can get sort of a shared team to manage it if it would be too big for any one person.

Feanil Patel: Yeah, awesome. Thank you.

Feanil Patel: But yeah.

Feanil Patel: It'll be maintained better. If somebody does step up because Adolfo already spends a lot of his time doing reviews across the whole platform.

Feanil Patel: All right. Let's go the to-doos.

Feanil Patel: Robert I saw that you had already updated a bunch of repos. Because they just had been using the wrong suffix for the catalog file. It sounded like

Robert Raposa: I think it was the wrong suffix and it was the old version that didn't actually have the ownership in there yet. So basically I did my Outreach only a couple of days ago, but I did do the July 31 deadline so well.

Feanil Patel: he

Robert Raposa: so I did the Outreach and we'll follow up and hopefully We'll see things in there by the end of the month and it Will decide whether You Yank It ownership or our maintenance ever.

Feanil Patel: That sounds good. Yeah, it looked like five four or five of them had already updated. So I updated the list here and there's only six left now. and you …

Robert Raposa: That's good.

Feanil Patel: So thank you for that Jeremy. I think you have already done this follow-up purchase to document maintainership transfer. I got a message from Chris Pappas that he wanted some clarification, but he's gonna get around to making those posts when he's back from vacation, I think.

Jeremy Ristau: That sounds true. But yep. I'm aligned with that.

Feanil Patel: Cool, and then to you Aurora want and that's happening. We just talked about that. I think you can check those two off.

Jeremy Ristau: Go.

Feanil Patel: A legacy code exists in front on mfes. So Robert, I think we were doing this as a part of the Decker work and it's kind of progress. This is to sort of find all of the old duplicate front ends. And I know Diana posted on a couple of Deckers already that you has moved off of some that they were blocked on previously for Edge.

Robert Raposa: yeah, I'm trying to remember what this is and whether

Robert Raposa: The right person to have on this action item unless I mean it depends What am I supposed to be doing on this side?

Feanil Patel: I think this is completing that wiki page we started last month around and let me see if I can find it around the existing mfe's and their legacy code. So it is further work on this page as a part of the deprecation working. Yeah, not this page. Let's see try copying.

00:30:00

Feanil Patel: There we go that further work on this page

Feanil Patel: making sure that if there are things that have Replacements that we have Deckers for them. I think all the studio stuff Jeremy is there gonna be a single Decker for all of that stuff or So once that's posted we can just update this sheet, but I think there's a lot of old LMS replacements. That some of them have Deckers and some of them don't. So just finding out if the rest of these either need a debt or created or if they already have one Robert is the work and I think we can do that as a part of the Decker meeting. next week

Robert Raposa: Yeah. it's this month. So that's first step for us. And then maybe having maintenance of each of these areas actually fill out the rest of

Feanil Patel: Yeah. Yeah, I think we're just sort of like helping bootstrap this process because it's a little bit of ancient history and Archeology and we're trying to get enough information so that the modern maintenance can make good decisions about it.

Robert Raposa: okay.

Robert Raposa: and is that I guess there's always crossover between this group and Deborah wondering if this should Simply Be not an action and discussed here, but actually item discussed in the Dipper where we're actually going to do.

Feanil Patel: Yeah, I think it was previously and I think it continues to be.

Robert Raposa: work done

Feanil Patel: Right, and then we just talked about this which is Jeremy is gonna make sure there's that part tickets for the front end replacement bits at some point.

Feanil Patel: isn't here. Kyle has the big Ideas Google Document issues work going

Robert Raposa: I feel the Wiki page that you gave where can you just put a link?

Feanil Patel: Yeah, I'll put a link in this stock.

Robert Raposa: Thank you.

Feanil Patel: All right. and then Adolfo, I think There's some Dapper tickets. We need to drop right for dropping the way we do Footers right now where they get forked.

Adolfo Brandes: 

Adolfo Brandes: Yeah. That's related to the plugin.

Feanil Patel: Yeah.

Adolfo Brandes: conversion, right

Feanil Patel: Yeah, so that we give people enough time before we sort of drop the old way of allowing Footers to be inserted.

Adolfo Brandes: Yeah. it might be that it's

Robert Raposa: Thanks.

Adolfo Brandes: Time to also do that for the header. because we have every intention of changing that for sumac too.

Feanil Patel: Yeah.

Adolfo Brandes: So really pay

Feanil Patel: Yeah, okay.

Felipe Montoya: Yeah, I was gonna say we talked a lot doing the conference days about standardizing on the names. So if we are going to do that, and we're going to diaper the old way and tell them to install the photos and hairs. we might want to do the naming conventions first so that we don't have to tell them again. But feel I don't know half a release later.

Feanil Patel: Yeah.

Felipe Montoya: Okay, you need to change again because now we have a standard.

Adolfo Brandes: So we're gonna be talking about modifying or improving the front-end plugin API in the front and working group meeting and about an hour or so an hour and a half. I think Felipe if you could make that meeting it would be great so we can talk about some of this too. Go ahead and you?

Feanil Patel: Felipe just to clarify you're talking about the naming convention for naming the slots that are going to be replacing the old inserting headers and…

Adolfo Brandes: Yeah.

Feanil Patel: Footers. Yeah, right because we have talked about sort of following a similar convention to the hooks and extensions framework at the conference and making sure we just align on

00:35:00

Feanil Patel: Yeah, sounds good.

Adolfo Brandes: There was General consensus at the conference. At least from the people that were there. We now need to get. It publicized wider.

Feanil Patel: Yeah.

Feanil Patel: If you guys have any links to anything that you can put there in that section. Feel free to drop them when you have them.

Adolfo Brandes: Okay, I don't think there's anything now but there might be after the friends and working with me.

Feanil Patel: which is also usually recorded So watching this recording they can jump to that recording.

Adolfo Brandes: Yeah, Yeah, that's probably one of the links that's gonna be there.

Feanil Patel: yeah. All right. That's it. So then This quick how- for python 311 through 12. I still need to do that. I'm not sure how necessary this is anymore. People have started moving forward sort of on their own here, but I might write a general one for how our libraries are upgraded later. and then

Feanil Patel: Jeremy to make sure that internal audit of ownership that you will end up with an update to code owners.

Adolfo Brandes: Okay.

Feanil Patel: I think this can be close.

Jeremy Ristau: Yeah. Yeah, I think so as well.

Feanil Patel: Especially now that Robert is sort of given them the sort of final.

Jeremy Ristau: Yeah.

Feanil Patel: ultimatum on that Great.

Feanil Patel: Yeah, That's totally fine. I think that is a misnomer and we meant to say sort of code ownership or maintainership with updated. So

Feanil Patel: okay. next

Feanil Patel: node 20 updates last check in Adolfo. Do you have any updates on there? I know you've been super busy. So

Adolfo Brandes: No, nothing. Just yeah except to say that I have not forgotten about it. It's on my plate to get that going as soon as possible sumac is Just three months. We don't have a lot of time.

Feanil Patel: yeah.

Feanil Patel: Yeah, I mean, I think one sort of related piece of good news is we have a third front end all maintainer who can help with this stuff, which is Braden. it's in front end all so that will hopefully help make the coordination and…

Adolfo Brandes: Yes, exactly.

Adolfo Brandes: Yeah.

Feanil Patel: and do the work easier and…

Adolfo Brandes: also Go ahead.

Feanil Patel: at I

Adolfo Brandes: I was gonna say there's a very related conversation about synchronizing. All that or the most important dependencies across all mfes are related to all of 65 which David Joy is working on. and hajis from edley who's also on the TOC is putting on some pressure pressure for us to do this specific thing. which is

Adolfo Brandes: Making it easier for maintenance and operators to keep all dependencies and sink. So We're probably not going to wait for 65 to be complete to start working on something that we can get sooner.

Feanil Patel: 

Adolfo Brandes: Around that but it's still on the conversation phase and on a R comment space and it's no twenties. Of course just one of those dependencies. Anyway, just a heads up that these conversations are going to start happening now.

Feanil Patel: Yeah.

Feanil Patel: Yeah, I think there is this the thread that they're on right now.

Adolfo Brandes: that's related.

Feanil Patel: Yeah, yeah.

Adolfo Brandes: Yeah, there's also An oep 65 related ADR where there's some conversation happening and let me link to it in the chat also here.

00:40:00

Feanil Patel: Yeah, that'd be great.

Adolfo Brandes: and also in the page

Feanil Patel: I can add it.

Adolfo Brandes: Okay.

Feanil Patel: Yeah, so In terms of Maintenance coming down the line. That's probably a future thing that will want to coordinate on I think an open question I have is sort…

Adolfo Brandes: exactly

Feanil Patel: how do we This is one of those things that's really easy to do once but really hard to sort of Ensure stays true over a period of time. So I'd be curious about What mechanisms will employ to help make it? consistent

Adolfo Brandes: exactly

Adolfo Brandes: Yeah, so we were considering waiting for David's work or I'll have 65 to see where that landed if it would help. But if I figure there's things we can do off the bat they even…

Feanil Patel: mmm

Adolfo Brandes: if it's just an ADR. To remember to keep dependencies always up to date synchronize across all mfes and something like that. But yeah, it's still just brainstorm stage. There's probably going to be more meetings just about this going forward or threads. There's no plan yet as to…

Feanil Patel: Okay. Yeah,…

Adolfo Brandes: how we're going to do it.

Feanil Patel: I'd love to be included on those conversations when you're having them.

Adolfo Brandes: yes, if I mean, this is more a topic for this group than just the front end working group,…

Feanil Patel: Yeah, we might need a crossover meeting.

Adolfo Brandes: I guess.

Adolfo Brandes: But I mean, I have a meeting with David Joy right after this one where we're going to talk just about this. Some ideas are probably going to come out of that and…

Feanil Patel: Yeah.

Adolfo Brandes: I'll bring they bring them back here. in some form

Feanil Patel: Okay, sounds good. Yeah. Yeah, if you post them somewhere and then just post in WGME.

Adolfo Brandes: exactly Yeah.

Feanil Patel: Yeah, that's totally fine. cool anybody else have?

Feanil Patel: Put these in the wrong spot and great any of the questions.

Feanil Patel: Okay, just check in. Jeremy this is I think a question for you because I don't have a lot of visibility. I know Arby's mostly heading on what I did do is take their spreadsheet of PRS and convert it to a GitHub issue with all of the pr. So it's easy to see which ones are done and not done automatically rather than them manually having to update that I didn't know who to share that on that side because I keep screwing up who it is that I should be talking to.

Jeremy Ristau: So ban is the person hanging out. Yeah.

Feanil Patel: Okay.

Feanil Patel: I'll just

Jeremy Ristau: Yeah, I think that one kind of got paused with the typescript and the alpha release blocker for a while. And once that got cleared up I think. distractions had already come up, so

Feanil Patel: yeah, and mostly I think this is in PR review phase. So any front-end people can be reviewing that have merge access can be reviewing this so Adolfo. I don't know this might be worth bringing up at front and working group that the just work is Probably mostly ready to land. And needs reviewers. and mergers

Adolfo Brandes: All right.

Feanil Patel: Yeah, because that was I think sort of the upshot of my conversations with sobond previously was that a lot of it About ready or they think is ready and I'd love to sort of figure out where that Gap is between it being ready and it being done.

Feanil Patel: right right

Feanil Patel: Yeah, that's what I noticed in a bunch of the ones. I spot checked. So I'm hoping that if WG front end can unblock them. that would be useful.

Adolfo Brandes: yeah, I'll shop it around and I'm sure I can look at a couple of those myself to

Feanil Patel: Yeah, I think especially where it's being blocked on sort of to you internal teams. If as frontend all people you and Brian and Brayden can look at those that would speed things up.

Adolfo Brandes: yeah. Yeah.

Feanil Patel: so I think that's sort of looking at sort of Maintenance work. Right. It's a little bigger for people.

00:45:00

Feanil Patel: That's kind of the big stuff. We're trying to land for sumac is those things? and one of the things that I'm gonna be looking at personally over the next little bit is getting deprecations out for repositories that I think are not relevant to the open edx, generally.

Feanil Patel: I don't have a lot of details on that yet, but I just did want to mention it because if look there's in the release. repos and maintenance priorities spreadsheet there's this column to deprecate which is Somebody at some point said is that a thing we really need and say I said, I don't know. I will put a checkbox next to it and then I will come back and look at This is me going back to look at anything that is potentially marked for deprecation and Talking with product potentially talking with engineering and looking at the history of it and figuring out if it's a necessary part of the platform or if it's a thing that we can deprecate and drop from the platform. So if you're curious about sort of what that Target list is going to be it's anything with the checkbox here. if you have thoughts or feedback, please send them my way.

Feanil Patel: Some of these are just because it has a checkbox doesn't mean I'm going to sort of rip it out and throw it away a really good example of this is I think the config models repo is a thing that I think a lot of people want gone, but we really don't have an alternative so I don't plan on replacing it anytime soon, but it is marked as a thing that marking desire and sort of Direction.

Feanil Patel: Front end support tools is a controversial one because I think mostly internal to you at this point, but could be useful to others and somebody needs to go make that decision.

Adolfo Brandes: I would that publish her to the same category.

Feanil Patel: Yeah, yeah publisher and I mean in my mind, of course Discovery, but that's a more complex question that requires some prerequisites be fulfilled around having a standard course model, which is a conversation. We had at the conference that I think needs I'm gonna follow up on the previous ADR and edx platform around that but yeah just didn't General heads up that gonna be looking more at deprecating some of the larger pieces of the platform that perhaps no longer makes sense for the community and maintain commerce is on that list also.

Feanil Patel: I think we had some good conversations around alternatives for many people at different scales. And we're talking about more improvements to the woocommerce plugin for those people who want to use that and there's a heztec so has a web hooks plugin that people are using to be able to do purchasing. so

Feanil Patel: yeah, if you have thoughts on any of these things concerns, there will be Dipper. So this is just early warning. There will be proper depress for anything that we want to get rid of and conversations can be done there. But if there's early concern and you're like that checkbox next to a thing. I want to keep that in the platform and I will help maintain it, a lot of these are not maintained. So if you want to become the maintainer of any of them makes it a better case for keeping them in the community.

Feanil Patel: That's all I got.

Feanil Patel: Maybe that's a good question. they're sort of like higher priority things in my mind that need maintenance then config models. if we can just keep config models a works with Python X and Django X It's good enough. It doesn't need a lot of architectural support and I'd much rather a lot of that energy. It's spent on front-end app learning or other sort of major pieces of the core edx platform.

Robert Raposa: Yeah, that's just doing with. Django upgrades another maintenance

Feanil Patel: Yeah, yeah. yeah, and I think we'll have this situation where there's a lot of stuff that we're going to have to keep upgrading until we either get rid of it or figure out a different plan for how to keep it.

Feanil Patel: because at the rate we're not going to find a maintainer for everything which means there's gonna be a large group of repositories that we as a community are just gonna have to sort of Pull our sleeves up and just get to work on whenever we need to get them upgraded for a thing.

00:50:00

Robert Raposa: presentation

Large Conference Room: As we discussed Endeavor working group. I don't think we should be marking repositories deprecated that we don't have actual path and Volunteer to make that happen,…

Feanil Patel: Yet. Yeah.

Large Conference Room: so I don't think that's what you're gonna do for now sounds like you're gonna file those tickets for ones that you're actually willing to push forward.

Feanil Patel: Yeah, exactly. The next phase is sort of the research to determine the answer to the question. is there a path to get rid of this and if there isn't then Maybe I will uncheck Market but those are all the ones that I'm going to look at to start with and review all of our sort of. information to date and figure out what next steps might be

Robert Raposa: Thanks.

Feanil Patel: right And that is two minutes you guys get back to yourselves. So, thank you everybody.

Robert Raposa: Thanks, everyone.

Jeremy Ristau: Good.

Feanil Patel: Have a good one. See you next week 30 minutes earlier.

Meeting ended after 00:51:34 👋