edx-platform Maintenance  Sub-Group (2024-05-30 09:06 GMT-4) - Transcript

Attendees

Adolfo Brandes, Awais Qureshi, Chintan Joshi, Feanil Patel, Feanil Patel's Presentation, Felipe Montoya, Jeremy Ristau, Kyle McCormick, Maksim Sokolskiy, Michelle Philbrick, Piotr Surowiec, Robert Raposa, Sarina Canelake

Transcript

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

Feanil Patel: just presentation times everyone.

Feanil Patel: one of the pet.

Feanil Patel: And like to bring up the maintenance board.

Feanil Patel: Because I wanted to bring this up most because I want to start talking about.

Feanil Patel: What other things need to be on here for visibility and so that we can prioritize against each other? Because then we can just start rearranging things here to make clear what the priority is in terms of Landing things on. master

Feanil Patel: and that way hopefully like to you in coordinate internally anything that it needs the other thing we do need to do before so the way I have it is I think that python 312 upgrade. is behind

Feanil Patel: is behind the node.js upgrade? to note 20

Feanil Patel: I'm sure that that's right.

Feanil Patel: All right is 18 ends and 11 months, which means it'll End before we cut teeth, which means we need to land it and sumac. Or anything that's in the release.

Feanil Patel: Annoyingly, they're schedules are a couple months off by ours, which means that we lose a little bit of time each time. They're doing a release.

Robert Raposa: if we shifted schedules at some point, would it just Because it problem on a different thing.

Feanil Patel: Yeah, I mean the schedule we've chosen is what is the right schedule for operators to do updates because it better aligns with most school calendars

Robert Raposa: you got make sense

Feanil Patel: so it just gives us a little bit more flexibility to backport if we need to but I think our primary goal should be to land. not 18 by sumac apologies

Robert Raposa: is that commented appropriately or do you want to add a comment there?

Feanil Patel: and comment and

Robert Raposa: or even update the description

Feanil Patel: yeah.

Kyle McCormick: people There is a deprecation ticket.

Feanil Patel: yeah.

Kyle McCormick: I think personally it's for Studio front end and it looks like we're to remove Studio front end before sumac which would remove work from the note upgrade. So you want me to add that difference? I did to the maintenance board or as a sub task to this note upgrade and hopes that we don't actually have to upgrade to the front of body.

Feanil Patel: Right, right. let's add it to the maintenance work because I assume that that will actually require some coordination For example for two you to be dropping that is that accurate?

Kyle McCormick: As far as I can tell They're using all the new stuff which basically issues to do it for an entirely.

Robert Raposa: The do you know,…

Feanil Patel: Okay.

Robert Raposa: this is just a question because we keep discovering places where Edge has not been updated do we know Is using the latest Studio.

00:05:00

Kyle McCormick: I could tell you maybe you're asking Jeremy not mean.

Feanil Patel: Yeah.

Robert Raposa: I'm asking anyone.

Feanil Patel: Yeah, I think having me and…

Jeremy Ristau: It is not.

Feanil Patel: Kyle have the least visibility on that.

Robert Raposa: Yeah.

Jeremy Ristau: It is not. That you're talking about the course authoring MFE pages right when you say new studio.

Feanil Patel: So we'll need to coordinate with…

Jeremy Ristau: No, it's still Legacy.

Feanil Patel: because we want to start archiving out. is that going to cause issues for you guys to make updates over there or is it okay to be running from an archive version of the studio presentation?

Kyle McCormick: I think it's a little different than that, because we would be receiving the pages for Medics platform.

Feanil Patel: I see also dropping the Alex platform pages, okay.

Kyle McCormick: And it'd be deprecated that whole Community too.

Robert Raposa: yeah.

Kyle McCormick: Edge as well as other deploys the affected.

Feanil Patel: Yeah. let's put it on the maintenance board as a primary item is it seemed and maybe that's just like a

Feanil Patel: nice to have for this but with depending on the timing we may need to end up doing both. So

Feanil Patel: let's figure that out.

Jeremy Ristau: I mean we can also just roll out the course authoring MFE pages to Edge. Yeah.

Robert Raposa: It's just about timing that and…

Feanil Patel: Yeah. Brett when Right,…

Robert Raposa: with all the other things.

Jeremy Ristau: Sorry, I guess.

Feanil Patel: it would be extremely awesome to do that.

Feanil Patel: But can you do that?

Jeremy Ristau: Maybe what I mean to be very very straightforward not all of the studio pages are migrated to course authoring so it isn't like a new studio and…

Jeremy Ristau: old Studio. 90% of studio is in corther course author and…

Feanil Patel: right

Jeremy Ristau: kind of thing, but I think we just didn't turn them on edge.

Kyle McCormick: right

Jeremy Ristau: So we could do that in June. I don't see that being.

Kyle McCormick: and what Chris and I figured is That 90% of Studio covers everything used by the surface.

Jeremy Ristau: Covers everything used by what sorry, I miss that.

Kyle McCormick: Studio project It's like a weird extra react Repository.

Jeremy Ristau: yeah, it's just like the accessibility page and the checklist page all of that stuff has already been ported to course authoring and…

Kyle McCormick: position s

Jeremy Ristau: Yeah, I think. Three pages maybe in studio front end so we could…

Kyle McCormick: just also the old HTML editor

Jeremy Ristau: if that's the only thing you want we could definitely roll those out.

Kyle McCormick: I don't know. statement

Jeremy Ristau: I actually don't know about the editors and Edge. Let me check those real quick.

Jeremy Ristau: At least for the HTML block. It uses the new editor, but if you're talking about the tiny. Wysiwig editor that's definitely used in other places, course updates and stuff. So

Jeremy Ristau: yeah, We'll work to roll everything on an edge this month.

Feanil Patel: But is that a ticket that Jeremy you and Robert will have on your side to sort of verify that because it sounds like that'll be a prerequisite to cleaning up the old UI and related

Feanil Patel: Studio front end repo

Jeremy Ristau: Yeah, I mean what I'll do is I'll put a ticket into the T&L backlog. Obviously Brad the product manager needs to decide that that is the correct thing to prioritize…

Feanil Patel: Yeah.

Jeremy Ristau: but I'll make sure it gets into the month of June.

Feanil Patel: Awesome, that'd be great.

Jeremy Ristau: Yeah.

Feanil Patel: Yeah, and how did you add it to the maintenance board yet?

Feanil Patel: And then Jeremy, I think the Arabic bomb team was working on the just 26 to 29 upgrade. Is that still in progress?

Jeremy Ristau: I believe that is blocked on the edx to open edx namespace move and it's not blocked by a bomb team as PRS pending for other teams to review.

Feanil Patel: other than

Jeremy Ristau: And so that's what it's blocked behind. So. yeah, it's

Feanil Patel: Are those listed in? How do I have…

Jeremy Ristau: cat hurting

00:10:00

Feanil Patel: how can I get that list at the yards? Did they be listed in this repo or in this ticket?

Jeremy Ristau: Yeah, I mean we can list them in that ticket I am.

Feanil Patel: Send it to you.

Jeremy Ristau: of course for the next Few weeks. The team is focused on data dog migration. So yeah.

Feanil Patel: Jeremy

Feanil Patel: Yeah, because if it's blocking front-end work another repos we can have Community folks review and then some of those. In the meantime, so if we get that list sooner we can probably unblock it while you guys are working on the data dot stuff.

Jeremy Ristau: yeah, I'll talk to the team and

Jeremy Ristau: it's likely that the few PRS that are from teams that want to review them and can't so it's a little bit of again a cat hurt in conversation.

Feanil Patel: Yeah.

Jeremy Ristau: So I'll ping people and see what their preferences.

Feanil Patel: Yeah, I'd love to get the list because if there are CC's on those repos, then they should be able to review them and if there's a concern with that I want to surface that sooner rather than later.

Jeremy Ristau: Yeah, I think it's mostly about the deployment not the review. So yeah.

Feanil Patel: but

Feanil Patel: Okay, so it sounds like actually the focus for the next little bit we want is frontend cleanup and not actually the pthon recall Which may mean the python 312 upgrade gets push past sumac and into teak.

Feanil Patel: Because there's I think enough front-end lean up and rejecting that is sort of work in process that I'd love to land or at least linearize so that we can have that stuff be less. I don't want to live in things in progress. And I don't think you do either.

Jeremy Ristau: Yeah, and I know that David Joyce doing a lot of talking about potentially consolidating some repos and…

Feanil Patel: 

Jeremy Ristau: things which hopefully makes some of these front-end efforts slightly less. Large scope.

Feanil Patel: yeah.

Jeremy Ristau: So I don't know if that kind of thing is on this roadmap either or if it can't go on here until there's a more clear path of what's gonna happen with Federated modules and stuff, but

Feanil Patel: right I think that stuff is still early enough that most of that discussion is happening in sort of adrs and ellips, but I know David is gonna put up a new ADR on the Federal Federation stuff or Rejiggering the front end platform repos and the headers and footer and moving that all consolidating a bunch of that. So hopefully Yeah.

Jeremy Ristau: Yeah, so I mean it would be great if we didn't have to do all the node and all that work on repos that are gonna disappear right after but you…

Feanil Patel: Yeah.

Jeremy Ristau: it's timing is what it is. So Yeah.

Feanil Patel: I think part of it is that any updates we do now makes those transitions easier and simpler because they will have to do those upgrades before they happen in a bunch of those cases. So anything where we can bring repos up to sort of latest standards means that there's less complexity when we are trying to do a complex thing of merging them and reorganizing them. So I don't think it'll be lost effort for the most part.

Feanil Patel: Yeah, in that case I think if you can get the blockages for Jess would be good. But I think I'm gonna focus on the upgrading of node 18 to 20 and identifying all of the repos that need that and thickening that up. so

Feanil Patel: but in terms of Platform honestly might be easier to do now because Brian and I have been making a bunch about dates there and this probably worth. and FY to you guys, which is a bunch of Kyle the edx platform and PM packaging was being done was wrong. In a couple of our sub packages and so as we're finding those were fixing them. And that's unblocking a lot of upgrades in edx platform dependencies that were three or four major versions behind or transitive dependencies are now getting upgraded for the most part. I don't expect that to be an issue because it's like the Eventing thing inside of the dev environment of one of our dependencies finally can get upgraded so that it doesn't vulnerability in it, but

00:15:00

Feanil Patel: if there are I can tag people on those PRS when they're going out. I know there's one that'll probably go out today. If you want to keep more of a manual eye on it, or if you want to just be aware in case you get reports of those because those are sort of like lots of bumps in independencies.

Feanil Patel: And let's add that here.

Jeremy Ristau: And when you make those changes, are they going to get announced in the CC front end Channel or…

Feanil Patel: Yeah, CC edx platform.

Jeremy Ristau: something or maintenance?

Feanil Patel: I'll announce that I'm merging this PR. It's updating a bunch of no dependencies. I'll do it in X minutes kind of more the standard way just…

Jeremy Ristau: Okay.

Feanil Patel: because it's such a larger set of changes.

Jeremy Ristau: And you see it Landing all at once.

Feanil Patel: a lot of them are interdependent. So it's hard to extract them into smaller bits. There's not really a mechanism makeup grade where we can Target a couple of libraries at a time on the notes side.

Jeremy Ristau: I mean honestly for this kind of change, I'm more comfortable with it being slightly Atomic and…

Feanil Patel: Yeah, yeah.

Jeremy Ristau: that's like going to track down 50 different changes and 50 different places. So I think that works for me.

Feanil Patel: I just fixed a thing in the proctoring library that allowed for 40 packages to the upgraded or something.

Jeremy Ristau: Yeah, okay. Fantastic.

Jeremy Ristau: Man, 2024 is cleaning out the closet, Yeah.

Feanil Patel: Just dappering and dropping old crap less than right.

Jeremy Ristau: as a pretty full closet so

Feanil Patel: Yeah. it's a walk-in with a full bath in the back and

Jeremy Ristau: When you open the door stuff falls out on you.

Feanil Patel: Mm- Yeah, exactly. It's like but yeah, I think as long as we can coordinate it. I'm happy to sort of stack in order how we're doing this.

Robert Raposa: two potential topics one so you can let me know when that one's related to…

Feanil Patel: Yeah good.

Robert Raposa: what you just mentioned which is so I shared that one ticket that basically just listed some of the dippers that I thought were related to us, but I don't know if we have tickets on this board to represent whatever work that we need to do this board being the maintenance board and what we should have on there for those so

Feanil Patel: Yeah.

Feanil Patel: Yeah, I mean this board I opted from essentially Jeremy Bowman when he left right and I know Aruba bomb is using it for a bunch of stuff. There's theoretically like tagging for different owners and their internal things that they need to do.

Robert Raposa: yeah.

Jeremy Ristau: the death element will tagging and…

Feanil Patel: but Yeah,…

Jeremy Ristau: everything so

Feanil Patel: I mean that's all like that stuff. I'm not doing currently and so these other tabs I think are sort of historic and I'm like I will clean up but I didn't want to do it until we got better sense of how we're gonna operate. the thing I've been trying to do is on this main board just at least capture all of the things that we're aware of…

Robert Raposa: Yeah.

Feanil Patel: because we were able to very quickly be if we need the note upgrade and we need the npm ownership update before the just update. All of that means that python 312 makes sense down here rather than up at the top. Right? I want to be able to do more of that.

Feanil Patel: And so honestly, I'm just gonna move this python 312 back into to do's

Feanil Patel: interesting the right just saw things that I think I did yesterday so I might be able to close up. an issue that somebody else open

Feanil Patel: Yeah, I think I'm happy to sort of start adding more. Structure to this board that would be helpful to you guys or when they're landing on Master versus when they're cleanup is landing on master.

00:20:00

Feanil Patel: and we can coordinate that with internal priorities you guys might have

Robert Raposa: I'm wondering if we should put dates on some of these and expose them on the board.

Robert Raposa: So it's not that happen. The second that I thought for changes for this board.

Feanil Patel: yeah. Yeah that a Target release. date

Robert Raposa: He yeah, so it could be that as long as there's an actual calendar date with the really

Feanil Patel: Yeah, I would do like sumac October 2024.

Robert Raposa: exactly

Jeremy Ristau: Yeah, a month would be great.

Feanil Patel: Yeah. Yeah.

Jeremy Ristau: I think that would probably be fantastic. Yeah.

Robert Raposa: Yeah.

Feanil Patel: That's what I'm thinking is like.

Feanil Patel: The tag could be sumac October 2024 but I think having both the name which some people associate and then the calendar time, which is more useful to everybody else.

Robert Raposa: Yeah.

Jeremy Ristau: Is your example included a named release and the month in which we freeze said named release it would also be something like sumac July 2024.

Feanil Patel: Yeah.

Feanil Patel: I say I see so aim for

Jeremy Ristau: Course number 2024 when you plan on it.

Jeremy Ristau: That way we can say this is good for this. Yeah.

Feanil Patel: by myself I like that, It's like we want to Target sumac but we want it to be done by end of July so that we like, okay.

Feanil Patel: Yeah. Yeah, that makes sense to me.

Feanil Patel: that

Feanil Patel: I'm using the label is good enough for that or didn't

Robert Raposa: A lay. it depends it.

Feanil Patel: we can do yeah.

Robert Raposa: I guess you can add lots of things. But if you want it to be July or every month you need lots of labels if it's going to be a label versus

Feanil Patel: That's true. Maybe it's just a field on this board. All…

Robert Raposa: Yeah. Yeah.

Feanil Patel: I'll figure that out.

Feanil Patel: Yeah, feel probably is the right move in that way. We don't have to apply the level of cross all of the rainbows where we might have tickets.

Robert Raposa: right

Feanil Patel: 

Robert Raposa: Then do so in terms of that. Listing of Deborah tickets.

Feanil Patel: Yeah.

Robert Raposa: Do we want?

Kyle McCormick: Yeah, I was gonna mention with it. so what's also is that it's not of free platform has been done. So. I mean, could I see you guys Redoing the entirety of Studio internet data, that's amazing. Could I ask that? Or whatever front ends you were driving the rep platform or of people who are driving your platforming for could you have to make a different ticket for the Legacy thing? I know some of them exists like Studio front end and Legacy text. But I don't think there are different tickets for advanced settings for the older dashboard.

Robert Raposa: Yeah, I think that's come up in Denver many times. I don't even know if we have a diaper for profile, which we just noticed is not out in Edge, And stuff like that. So yeah, so

Feanil Patel: then

Kyle McCormick: I mean as much as I love. Upgrading old friends that we don't use to note 20.

Robert Raposa: exactly

Feanil Patel: yeah, it would be great to identify those and then If you guys can identify them we can work to although it sounds like some of the blockers might be internal to you if edges and running. Or of the mfbs that would replace the old front ends. But if we can get Dippers for everything we can at least start sequencing them because right now they're kind of in this unknown state. where it'll catch…

Robert Raposa: right

Feanil Patel: it'll catch you by surprise when there's an MFE for this we should delete this and then you're like

Robert Raposa: yeah, when I wonder if the front end group can manage because someone has to actually look at the ends figure all the detail I mean exactly

Feanil Patel: we said front end three times, so don't think

00:25:00

Kyle McCormick: But the ones that were just free platforms. It'd be awesome if we could have a team that let's free platform and make the debtor sets. How we want things to work anyway?

Robert Raposa: Yeah, and that definitely makes sense. I'm happy about those are.

Feanil Patel: Then I think for all the studio related ones that just landed you're talking about right Kyle. Yeah, so can get all the and…

Kyle McCormick: standard

Feanil Patel: then cut and then Robert's answer your question. Let's get those diapers on this board because if there are related coordinations and for removal that we have to do let's make sure that that's The maintenance like that, we can say sequence that for maintenance as much as possible.

Robert Raposa: yeah, let's

Robert Raposa: I just find that to get and

Feanil Patel: If you want to add that top level ticket here for now, that's fine.

Robert Raposa: yeah, I'm

Feanil Patel: Hey everybody. Welcome.

Robert Raposa: Yeah.

Feanil Patel: what you guys are looking at is the maintenance board which is where I slowly been trying to collect all of the sort of known maintenance work that we have to do Barbara bomb used to use this board for other stuff. And we are now sort of trying to track. all of the maintenance that maintainers might need to do

Feanil Patel: onto this board so that we can prioritize it against each other and hopefully have a clear answer when maintenance what should I focus on is it the python upgrade or the node upgrade or just upgrade or the react upgrade or what have you?

Feanil Patel: I think The current prioritization is in progress. Home is my thought which is I think that The next Focus based on when node 18 goes end of life is that we need to land. No 20 before sumac.

Feanil Patel: Node 18 goes end of life in April which will be before we cut teak so. Unless we want to backport a node 18 upgrade. I think we got a Target sumac for the 8 Note 20 upgrade.

Feanil Patel: Does anybody have any sort of? concerns or known issues with that

Robert Raposa: so I was just gonna say I put in the chat my ticket…

Feanil Patel: Okay, the other guy Robert.

Robert Raposa: what I don't know is do you plan on do you just want each of those steppers on this board?

Feanil Patel: I think I want those individuals, but I put your ticket on the board here for now so that I wouldn't lose a Yeah.

Robert Raposa: Okay. I miss it. Thanks.

Feanil Patel: All right.

Feanil Patel: Yeah,

Feanil Patel: but until I'm gonna pick on you for the new 20 upgrade. I think the first step is identifying sort of all of the Kyle pointed out that one of the things we may benefit from with the node 20 upgrade is that there is a bunch of front end that we just replaced with new fancier front end in the studio area. And so identifying all of the old frontend and deleting it before we upgrade. It. Seems like a valuable effort.

Adolfo Brandes: Yeah, ideally.

Feanil Patel: so I think Robert is going to sort of. Try to work with the team that did the implementation to.

Feanil Patel: Identify all of the old frontend that should be deprecated and make relevant Dipper tickets or get them to make relevant effort tickets. You have that, right? Robert

Robert Raposa: Someone I didn't know it was me, but it might be Jeremy because it might be more tnl related. I mean Yeah.

Feanil Patel: is it Jeremy? All right. Jeremy is going to

Adolfo Brandes: So when you say old front ends stop being the stuff and that explains platform

Feanil Patel: I think any front end either in edx platform or in studio frontend that now has a replacement in the new pages

Kyle McCormick: Adolfoot we talked about earlier is that we think Studio front end,…

Adolfo Brandes: okay got

Kyle McCormick: we can remove entirely by and then there's some others in Epic platform that we can probably clean up to outside of Studio front. And it's Studio brand the repo for anyone listening now, literally the studio front end.

Feanil Patel: And What's the new mfv called? Is it also called course offering?

00:30:00

Jeremy Ristau: Of course. And yeah,…

Feanil Patel: Thank you.

Jeremy Ristau: and so all the studio front end like widgets components in there. I have all been ported to course authoring and so we just need to roll out the new pages to our Edge environment, which we haven't done yet and then at least http://edx.org isn't dependent on Studio front end at all. So That wasn't our plan.

Feanil Patel: Let's then it.

Jeremy Ristau: Of course authoring MFE was to deprecate Studio front end. So We should make that happen for sumac.

Feanil Patel: Yeah, and then chintan asks a good question, which is the login registration and all of those which we are. Yeah, we want to get to those. Also. I think those are the ones Robert you were concerned. You didn't have enough context or Jeremy that these were historically removed things that you guys might not contact on.

Feanil Patel: is that right And so you need the front end working group to potentially make those tickets. For any frontends that were replaced.

Robert Raposa: I mean Yeah, I mean I could easily probably list all of the mfe's for each MFE. I have no idea if They all have we removed Legacy for them or…

Feanil Patel: right

Robert Raposa: should we assume that we haven't removed Legacy for any front ends and that we just need to see is there an effort ticket already and if not created.

Feanil Patel: yeah, I think that second thing which is that we should assume it's all still there because my understanding of that initial tranche of work was that we were very busy making the new thing and very not busy for moving the old thing because we promised we would do it later. but I'm here to collect.

Robert Raposa: Yeah.

Jeremy Ristau: So I mean I think if I understood your question earlier finial we replaced pages that are used on with new course authoring pages, right if there are pages that exist in edx platform that are rendered in studio that are not one .

Feanil Patel: right

Jeremy Ristau: We likely did not replace them. But as I understand the scope of this conversation, it is things that are in these Studio in repo not every page that is in edx platform. We're only talking about depering Studio front end. So if those widgets are used in Legacy Pages, they obviously need to be updated, but we're not talking about removing the edx platform pages. right

Feanil Patel: I mean, yeah, so if there exists replacement pages in the new course authoring world, we should remove the if they platform pages that exist in those platform are still the default version that is getting used by the world and it is using components of Studio front end. We would not remove those pages. We would just update those pages to hopefully use something else.

Feanil Patel: yeah, we just need to identify it and so that we can Get help for it.

Feanil Patel: Okay.

Feanil Patel: Yeah, if we can get those then maybe we can get some support from front NC season that it's platform to clean that out.

Robert Raposa: except for the Legacy ones that Again, it's easy to get a list. It's easy to probably. Try to find out if there's already Deborah and if not create the shell of the Dapper. What I think is trickier is going to be if we still have people on old profile and we have new profile not only even what functionality of the old profile never made it, that and…

Feanil Patel: Yeah.

Robert Raposa: I don't know who's going to be doing that. more that's

Feanil Patel: I mean, I think

Feanil Patel: On my guess is that unfortunately because of how those updates happened and how we did not do this sort of comparison. We will probably have to rely on the community to sort of help identify. I'm on the old profile page because I X and X is not available in the new profile. So I've been downgrading myself this whole time. So we may need longer runways to help identify some of these things…

Robert Raposa: Yeah.

Feanil Patel: where I think the new mfps are the default in tutor for most of these cases.

Feanil Patel: But I think We would just do some communication around that.

Robert Raposa: again Okay, I mean, I wonder if we should just do that in a different minute the debit.

00:35:00

Feanil Patel: Yeah, yeah.

Feanil Patel: I mean that could be done as just working that meeting or work from that group. I'm gonna add it here. For you and me or Robert.

Feanil Patel: So that we don't forget to bring it up in that meeting.

Robert Raposa: Yeah. that's good.

Feanil Patel: Right, so I think identifying what deprecations we can sort of execute on so that we can reduce our upgrade burden Is work we should do sooner rather than later. So I think once Jeremy gets us the list from his stuff. Perhaps you and I can go through the list of mfps and create the rest of that list and then we can figure out how much that is feasible to do. With the capacity we have in the community.

Robert Raposa: And I think getting the other Deborah tickets. On the board may help too because it might be that something that you wanted to land sooner. You're like, we should push that out because did not have to upgrade this Legacy good so Okay.

Feanil Patel: right

Feanil Patel: Yeah, exactly.

Feanil Patel: All That's the note 20 upgrade and I think that'll be sort of the focus. Over the next so I think the book is over the next couple bits for maintenance will be like if you have deprecations in your repos try to get those done. If you're not sure how to get them done come talk to us and I'll do a review of what deprecations exists with Robert for the front end up and based on the input from Jeremy will create all the tempers that we could get. We could apply pretty soon Mac for cleanup.

Feanil Patel: Adolfo I would love your help on the identifying things where We probably want to keep for sumac because I guess in Redwood. We have a bunch of MFS that are default but where you can fall back to the old stuff, is that right?

Adolfo Brandes: 

Adolfo Brandes: Yeah. But not very intentionally. It's mostly just because we haven't removed anything that people can do that. But the water is working groups not.

Feanil Patel: Got it.

Adolfo Brandes: We're not even concerning ourselves the Legacy stuff. It's as if it doesn't exist already, So yeah.

Feanil Patel: Okay, Got it.

Feanil Patel: So it sounds like you.

Adolfo Brandes: of the exception being the new studio course offering Pages which

Feanil Patel: You're very quiet.

Adolfo Brandes: Yeah, sorry, this is Simona had said that. ideal

Feanil Patel: Okay.

Feanil Patel: Got So yeah, it sounds like we know about sort of the detailed version for the studio front end course authoring stuff, but for everything else it's just implicitly been there and we just need to make sure that those explicit Communications happen, which I think we can do is part of pepper Robert. Does that sound right to you?

Robert Raposa: That sounds like I was unfortunately reading something for a moment. apology

Feanil Patel: It no worries I was saying. For all of the old front ends. They've been there so implicitly people could fall back to them if we're going to remove them in sumac we want to do a lot of comms ahead of that identify those and so we may be in this position where we don't actually remove them for sumac but do all of the warning and labeling to inform people. That student act might be the last release that has them. Which puts us in the awkward position of having to upgrade them.

00:40:00

Feanil Patel: So I think the sooner we identified. Yeah.

Kyle McCormick: We have precedent of sometimes gives that warning and sometimes not. I propose that we Only feel like we need to give that warning…

Feanil Patel: Okay.

Kyle McCormick: if we're actually removing. features able to do if it's a full replacement, I don't know…

Feanil Patel: Yeah.

Kyle McCormick: why we need to slow the project down. on that

Feanil Patel: That's a good call. If there's a features missing it makes sense to give that warning and if there's not featured missing if it's efficient feature parody, then we don't need to give that warning.

Robert Raposa: by give that warning meaning Bump it out of release announcing.

Feanil Patel: Bump it out early release. Yeah.

Robert Raposa: Okay something got it. Yeah.

Feanil Patel: That's a good call. Kyle like that.

Robert Raposa: Yeah, and hopefully the Dapper tickets themselves will. give enough feedback around hey, as you said maybe there was one that we don't want to upgrade that we're going to because we learned something.

Robert Raposa: I guess the thing we would learn That there is a future Gap. And not just like I don't want to do it.

Feanil Patel: Right, we would understand why instead of just people are stubborn and hate us.

Robert Raposa: It's good.

Feanil Patel: right right Yeah, so operators who are here. I'd love to hear from you. If we'll try to announce this again here when all the tickets exist, but we'll definitely need a review in case there are old views that you guys are using where MLB exist.

Feanil Patel: Get them.

Chintan Joshi: yeah, so for most of our projects we are using old views so even with the new releases I do this stuff manually that I'll be disabling the mfps and making sure that the old use with this Old Mac or HTML Pages or so so that's where we are at but slowly in all of those projects. I am trying to move to MSP step by step. So that process is going on.

Feanil Patel: Okay, if you identify a particular gaps, please let us know and we'll hopefully document them and we can potentially delay. Deleting code if it makes sense and if there are many operators sort of in that space.

Chintan Joshi: Okay. Yep.

Feanil Patel: Believe it.

Feanil Patel: before food

Feanil Patel: Okay.

Felipe Montoya: so I don't see…

Feanil Patel: let's

Felipe Montoya: why we should be still.

Feanil Patel: Awesome, so it sounds like we'll have enough answers for beaming and in the New World. by sumac

Felipe Montoya: I hope

Feanil Patel: and look at that we can push things out if it makes sense. So we just need people who are like, I don't run sadly and edx and open edx website anymore. So I don't know what People need and don't need as easily as I used to. So I rely on everybody else to tell me what the critical bits are for them.

Feanil Patel: All right.

Feanil Patel: I think there's anybody else have anything else to cover because otherwise, I think we can call that a meeting.

00:45:00

Feanil Patel: the other thing I did want to bring up.

Feanil Patel: was sort of our top

Feanil Patel: things that don't have maintenance or grading I believe at Spirit is going to try to spend some time on.

Feanil Patel: I know. Open craft and brightness adjusted that they're interested in Paragon. I haven't seen any movement on that. So.

Feanil Patel: Peter this is maybe for you send back to open craft and see if Braden or anybody else are planning on taking over for this. It's also maybe a Question for Adolfo. I don't know if you or Brian Smith should be maintainer. That's a conversation that we should have and just decide on.

Adolfo Brandes: I think particular Brian.

Piotr Surowiec: Yes.

Adolfo Brandes: Is already maintaining paragon? so it won't be a question of Having full maintenance,…

Feanil Patel: Okay.

Adolfo Brandes: which is great. I have no objections to that.

Feanil Patel: Believe it.

Felipe Montoya: last a Jeremy nomination for someone computer cool that wanted to ecore Committee of paragon, so with candidate

Feanil Patel: So it sounds like we have a lot of people who can help maintain Paragon and we just need to pick whoever is the person that I go yell at when they haven't been doing enough of it. And if we can figure out who that is.

Feanil Patel: You can. Get somebody official written down here.

Feanil Patel: follow up on that and then yeah, there's Rest API client there's in Canada. frontend learner dashboard is one Jeremy wanted to check in on it with there's a interest up to you aperture, but I didn't see it as Confirmation from you like I've seen on a bunch of the other repos that I know to you is going to be maintaining. So I wasn't sure if that was sort of open for others to take over or that was in fact that you aperture. Is already helping to maintain that question.

Jeremy Ristau: I think that there was someone from the community and aperture who wanted to maintain it and so that was like a conversation that needed to happen, but As I understand it it should be aperture.

Adolfo Brandes: That's in effect. What I've been treating aperture as maintenance of learned after whenever I need to deal with something or notify somebody or some changes or whatever.

Feanil Patel: that's That sounds good. and then

Feanil Patel: yeah, I think there's a bunch of other. stuff here where proctoring is enough before next

Maksim Sokolskiy: I just want to say that I've commented on some of repose recently.

Maksim Sokolskiy: Could you maybe review my comments or we also interesting and known to the s*? I just commented on ownership interest in column.

Feanil Patel: okay.

Feanil Patel: In the interest column, okay. Yeah.

Maksim Sokolskiy: yeah.

Feanil Patel: I can take a look at that.

Maksim Sokolskiy: Yeah, I just added to reposit where we can concern…

Feanil Patel: Okay.

Maksim Sokolskiy: what we can go for. permanent dealership or…

Feanil Patel: Okay. Yeah,…

Maksim Sokolskiy: at least Talk about it.

Feanil Patel: that sounds good. Yeah, I'll cross check those and I'll comment on your comments to be like go for it or hold on this one for all that.

Maksim Sokolskiy: Yeah, just waiting to presentation.

Feanil Patel: Okay, awesome.

Feanil Patel: Okay, I will take a look at those. Probably early next week.

Maksim Sokolskiy: Yeah.

Feanil Patel: Awesome. I think that's everything.

00:50:00

Feanil Patel: Go Fortune.

Chintan Joshi: Hey, so how created the PRS for adding catalog info? Yml file in the Repose which I think they don't have any interest or there aren't any maintenance for it. Should I also go ahead with priority two and three reports

Feanil Patel: Yeah, I think if definitely moved down to the two and three chintan's for those who don't know chintan's been doing an awesome helpful job for anything where nobody is interested at least updating them with doing the basic intro maintenance work for those so that they're kind of a little bit more up to Snuff and stay up to date even without a maintainer. I figured that kind of work is really helpful to sort of keep everything. Afloat, and moving forward if there are other people at your various organizations, that would have capacity for work like that. that would be really useful just even if you're not going to maintain them forever just doing the initial maintenance on a thing and making sure it's got the automatic update PRS are happening and the catalog info is there and the readme is fairly up to date those would be useful things to do.

Feanil Patel: Thanks everybody. See you next week.

Maksim Sokolskiy: Yeah, thank you.

Meeting ended after 00:51:48 👋