edx-platform Maintenance  Sub-Group (2024-03-28 09:06 GMT-4) - Transcript

Attendees

Awais Qureshi, Chintan Joshi, Feanil Patel, Feanil Patel's Presentation, Jeremy Ristau, Kelly Buchanan, Kyle McCormick, Michelle Philbrick, Nihad Rahim, Piotr Surowiec, Robert Raposa, Tim Krones

Transcript

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

Feanil Patel: Okay, Yeah, so the meaning notes are here also share my screen.

Feanil Patel: Not a lot to talk about today, I think. but let's just quickly go over what there is.

Feanil Patel: The biggest thing is since I spoke last time about python 311 testing for certain libraries, but not others all of the libraries that need python 311 testing are now being tracked on this edx platform test on python 311 ticket, which is a sub ticket of all the maintenance tickets, but underneath that there's one ticket in each repo that needs 311 testing passing so it should be easy to track.

Robert Raposa: is that in the notes did you just

Feanil Patel: Yeah, I just dropped that link in the notes. So that's here.

Robert Raposa: Okay, great.

Feanil Patel: So for everything else we'll be aiming for three twelve.

Robert Raposa: Great.

Feanil Patel: But for these we'll be aiming for three 11 as well. So there's an issue in that repo if you're not sure if this repo needs 311 and 312 and I'll be closing them as I verify that things have both running.

Feanil Patel: Ideally both but in some cases with the calc package and other packages possible to run three 12 yet. So 311 is the target. It's just if you're running if you can run 312 you should run through 12.

Feanil Patel: Actually, yeah.

Feanil Patel: I'm realizing that for some of these packages. We probably will want to run both 311 and 312 because there were running in other ideas like the Django utils and release utils.

Feanil Patel: Those are also run in the other services, right?

Feanil Patel: So I'll update. Those Robert do you happen to know off the top of your head What are the libraries that are installed in multiple ideas?

Feanil Patel: your music

Robert Raposa: I am Sorry, so I said I might be able to know a couple off the top of my head, but I'm just looking through there to quickly, but someone not. gonna be

Feanil Patel: yeah, we might discover some of those I can try to dig into some of the other ones. But hey Jeremy. Hey, Kyle. Welcome.

Robert Raposa: Config models. I'm not sure where that.

Feanil Patel: Yeah, yeah.

Robert Raposa: where that is but

Feanil Patel: I think Alex Django utils and edx Django released utils for sure. So I'm just up.

Robert Raposa: and Dr. Tensions

Feanil Patel: And drf extensions. Yeah.

Robert Raposa: and extra rest API client

Feanil Patel: Okay.

Robert Raposa: And edits so yeah, how do you want me to mark these?

Feanil Patel: So I'm just updating that three 11 tickets to just say 311 and 312. Here's an example in the messages.

Robert Raposa: Yeah.

Feanil Patel: So if you update them and then in the checklist, there was an optional run with 312 when we're moving the optional and I'm just saying it has to pass with 312 because it's going to be running with services that are going to run through 12.

00:05:00

Robert Raposa: All right. How far did you get at exfangeroodles?

Feanil Patel: I did site extensions release utils and Django utils.

Robert Raposa: Okay. Good.

Feanil Patel: So I think it's just like drf extensions and

Robert Raposa: Yeah, toggles. I'm several so. take

Feanil Patel: toggle Yeah. Yeah, okay. I'll leave it to you from here. thank you.

Robert Raposa: okay.

Feanil Patel: Yeah, so Jeremy. Hi Kyle, we're just talking about. The ticket that's linked here, which is the edx platform running on 311 ticket. Underneath there. I added issues for every library that edx platform depends on that will also need to run 311 just so we can track that. These are all things that we need to run on 311 as well as 312. And then the thing we realize as we were talking was that some of them are run in multiple services. So we want them to support both 311 and 312.

Kyle McCormick: Yep.

Feanil Patel: but in all of these there's already an optional note that if you can get it passing on 312 now while you're working on it you should

Kyle McCormick: Yeah. Sounds like we're aiming for a fairly fast follow python 312 upgrade on the next platform.

Feanil Patel: But I'm hoping that we can land the 312 in sumac but much earlier. on master

Kyle McCormick: cool three

Feanil Patel: because we could theoretically do it for a point release of We can theoretically do it for a point release Redwood but that feels like a big Point release change, so Yeah,…

Kyle McCormick: it would be yeah.

Feanil Patel: so I think we'll aim for three twelve because we only need three eleven so that we can go to 312. It just needs to be deployed once…

Kyle McCormick: Yeah.

Feanil Patel: but because of our time Windows that's just how it's going to work out. So

Feanil Patel: Yeah. That's in the fact that I think chintan and a couple people from Arkansas to the only ones I've seen sort of actively working on a need three 12 related stuff is the sort of biggest concern I have with Landing this in time. For a redwood cut a month and a half from now.

Kyle McCormick: Yeah.

Feanil Patel: Go fortunate.

Chintan Joshi: hey, so I have five to six days of holiday coming up and like me and my team so if we get some directions on which all repositories we could take up because as of now, I only taken up a repositories that don't have any interest or Any user in the catalog info? So if I can get more of those Repose me and my team we can work on that because we have long weekend coming up.

Feanil Patel: Yeah, I think the list that's in the ticket linked here is probably a great place to start but I can cross reference that with. Owners and get you a list of things that don't even have claim donors.

Feanil Patel: I'll put that as an action item.

Kyle McCormick: the nail Do you think that some of these tickets for some of the smaller repos are like?

Feanil Patel: Yeah.

Kyle McCormick: first-time contributor level tickets

Feanil Patel: Yes, I think if we could give them an example. Because we don't have the things we need to update. There's a checklist of them and I feel like if we could give them And I think this is the thing that I think I bet it'd be a lot easier for you. If we had that list of here the seven places to update and then here's how you should test it sort of a doc. So I think that doc might be really useful to compile sooner rather than later even for non new people.

Chintan Joshi: Yeah.

Feanil Patel: I think not everybody remembers that there's both talks and classifiers and whether to run the makeup great using the old version of python or the new version of python Etc.

Kyle McCormick: cool, so maybe not good first contribution level, but at least we could slap a help wanted label on it and Yeah.

00:10:00

Feanil Patel: Yeah, yeah, we could do help wanted label, but I think now that I'm saying it I feel like this doc needs to come into existence.

Kyle McCormick: Yeah, if you guys can make that I am happy to put the labels on and send to a blasts to a call for help for dick to repos or the small repost.

Robert Raposa: yeah, I just said it in that there's one ticket that I opened so far that I couldn't actually edit.

Feanil Patel: event much it is

Kyle McCormick: It's probably because it's outside to you edx Legacy team.

Feanil Patel: yeah. It makes sense.

Feanil Patel: I thought triage doesn't let you edit things that you didn't create, right?

Kyle McCormick: Yeah.

Feanil Patel: knowing

Robert Raposa: But it's the most this is both annoying and…

Feanil Patel: it's a good reason to keep them. What's that?

Robert Raposa: somewhat reasonable. I mean

Feanil Patel: Yeah. We're still learning all of the ways in…

Kyle McCormick: Yeah.

Feanil Patel: which the things GitHub promises us are not quite the things that we want.

Robert Raposa: Yeah. We were super trash.

Feanil Patel: Yeah. We want trash to be able to triage other people's tickets also.

Kyle McCormick: I just have broad faith that people aren't going to miss you mess with issues in an annoying way, but maybe you'll find it.

Feanil Patel: Yeah.

Feanil Patel: I think especially people who you're giving access to at a level other than read, But I bet it's more to do with their permission model than their.

Kyle McCormick: Yeah.

Feanil Patel: a desire

Kyle McCormick: Yeah.

Feanil Patel: because I think if we sort of narrow the scope to a python Library within the open edx ecosystem. I can like that's a pretty easy thing to write up and I can probably write something up for that and chintan. Maybe I can give it to you to review and try out. And your team can try it out.

Chintan Joshi: Here that would help massive.

Feanil Patel: Yeah, I'll try to get that today or tomorrow and send that to you.

Robert Raposa: whether you have an example for each or not, you might want to just ensure that there's a note to double check whether it's 312 optional or three 12 required

Feanil Patel: Yeah, I'll be check. I don't know yet. I think that's the thing. I'll be able to do more easily than them like I have.

Robert Raposa: 

Feanil Patel: I've been slowly setting up all the infrastructure to look up dependencies across. all of our repos that Ned builds a while back, so I'm just gonna yeah.

Robert Raposa: right but Even if checking is just pay close attention to the acceptance criteria,

Feanil Patel: Yeah. Yeah, that's a good point. Yeah, yeah,…

Feanil Patel: 

Robert Raposa: Her ticket,…

Robert Raposa: .

Feanil Patel: that's a good point.

Chintan Joshi: I think that three ripples.

Feanil Patel: Yeah, I see what you're saying. Yeah.

Feanil Patel: What did you say chintan?

Chintan Joshi: I was thinking that the three repos that I picked up was openly the Excel open edxcam and user util it contains all of these scenarios in one. user util as 312 and…

Feanil Patel: Yeah.

Chintan Joshi: 311 and 3/8 and came and calc they don't have

Feanil Patel: right Yeah for Kevin and Kyle we can't have three twelve because of the Sci-Fi nump bits, so I'm gonna remove that optional 312 from those tickets real quick while I

Chintan Joshi: Yeah.

Feanil Patel: and I don't know if you know this chintan, but for any of the issues as the only comment it will automatically assign the ticket to you.

Chintan Joshi: Okay.

Feanil Patel: and that would be useful if you want to claim the ones that you guys are working on. Then I can follow up with you more easily. And I know that somebody is working on them.

Chintan Joshi: Shooting then on those three issues. I'll take it up. Let me just send you the links of the pr that or…

Feanil Patel: Yeah.

Chintan Joshi: rather. I'll just link it in the issues.

Feanil Patel: Yeah, link it in the issues. That's perfect.

Feanil Patel: Okay, cool. I think that's most of what I have which is working on the 311 upgrade. I haven't had time to look into the Cal or the sandbox python setup yet, but that's kind of the Feel like the doc is more important because then we can scale out some of the work and then I'm gonna go back into looking at the sandbox and figure out how to deal with that.

00:15:00

Kyle McCormick: You need support anything else. I've put the content libraries work on pause until redwoods before this.

Feanil Patel: yeah. Okay. yeah, if you have time maybe you could take a look at the sandbox related stuff and I can finish up this dock because I think I have enough context to write up this upgrade dock but

Feanil Patel: So exactly. I think whether or not we can move it to code jail includes there's How we upgrade that? I think most of it is looking at that make file to figure out whether or not we need to just essentially lock the current requirements file and then make a new one, which I suspect is what we need to do.

Kyle McCormick: Yep.

Feanil Patel: But confirming that and then telling us what the plan should be is the output we need.

Kyle McCormick: Sweet I can do that. I'm talking I'll say that the lipsest stuff is on track to be complete.

Feanil Patel: awesome

Kyle McCormick: So there's that big switch to the npm scripts that I put in the channel.

Feanil Patel: Okay. Yeah and…

Kyle McCormick: that

Feanil Patel: You might have messaged me back, but that was ready for review now. Okay, yeah.

Kyle McCormick: It is ready for review. So there's that one and…

Feanil Patel: I can.

Kyle McCormick: then that unblocks this next VR. Which actually is what we need?

Feanil Patel: Right, okay.

Kyle McCormick: Which we still use lipsest Python, but essentially we skirt around the actual python code in it. We just go directly to the C Bindings that exposes. we're good for three twelve.

Feanil Patel: That's awesome. And then we can maybe pursue Mac. We could try to see if we can carve out some time to further clean up the static asset Pipeline and more

Kyle McCormick: Definitely. Yeah, If you look at the Dipper ticket, there's a bunch of items that can be done. And it says that basically in Redwood we're leaving the paver interface there just as this skeleton around the new stuff and…

Feanil Patel: Good. Yeah.

Kyle McCormick: then right after Redwood we can start removing the favor. Skeleton.

Feanil Patel: awesome And that's probably relevant for you to you folks because that paper skeleton is in your automation. So post-ridewood is a month and a half from now. So you should plan for having usage of the new stuff fairly soon after.

Kyle McCormick: I love Jeremy in and their ticket and he gave an eck. But happy to answer any questions…

Feanil Patel: cool

Kyle McCormick: if you have them Jeremy.

Feanil Patel: and cool. Let's see a thumbs up. Jeremy's as happy as it can be

Feanil Patel: Jeremy actually the question have for you is I think the last we had chatted the arbab team was working on the react upgrade or a couple of the other front end upgrades. Is there an update on any of that work?

Jeremy Ristau: so that has been pretty much blocked by the webpack and the selenium dependency and…

Feanil Patel: Okay.

Jeremy Ristau: last that I understood Brian Smith was working on that so

Feanil Patel: Yes, he's really close to having that be done. So he's close to Landing the note 18 upgrade…

Jeremy Ristau: Okay.

Feanil Patel: which will unblock a lot of that. we discussed one of his blockers yesterday and he has a path around it is working through so that should be moving pretty quickly and…

Jeremy Ristau: Yeah.

Feanil Patel: then is everyone gonna take up some of the edx platform Library upgrades? Are they contributing to that work? And what's the plan there?

Jeremy Ristau: Yep, I think they're just waiting. Currently, yeah.

Feanil Patel: All So I'm gonna try to get that doc out today or tomorrow and then maybe I can send that to you. Although I think those guys. have done this enough times that they could just start taking up any of the issues underneath this platform one, I think are fair game because most of them don't have owners. So what I would ask is the same thing as chintan, which assign them to themselves so that they can start working on them and then land them.

Jeremy Ristau: Yep.

00:20:00

Jeremy Ristau: That's a python ticket.

Feanil Patel: yeah, that's what I was asking about is will they be able to help with the python upgrade…

Jeremy Ristau: Sorry.

Feanil Patel: if they are not working on the react stuff, but

Jeremy Ristau: I thought you were asking if they were working on the react work and I'm saying they're waiting work on the react work blocked by Brian.

Feanil Patel: I said got it.

Jeremy Ristau: Yeah, I mean I can ping them and see how much they can put toward python as well. I mean the expectation was that they would help with edx platform. So

Feanil Patel: Yeah, I think the python work is higher priority than the react stuff because I think the react version. still is not out of support. Whereas the python version will be before. and we get to see Mike so

Jeremy Ristau: Yep.

Feanil Patel: That yeah, so I'd like to prioritize that. I think that's all I have is everybody else have anything that is platform related.

Jeremy Ristau: I think there was a question that was brought up regarding. the osprs in edx platform and sort of just the general escalation path for them now.

Feanil Patel: Yeah.

Jeremy Ristau: I think that escalation path has evolved pretty quickly since the last time it was talked about which was to have Michelle escalate edx platform Ospreys Through a spreadsheet and I believe now that it's much more like escalate them to core contributors. So, I think it's probably just formalizing that and some fashion

Feanil Patel: Sounds good.

Feanil Patel: And should probably be here for this next bit of the meeting so we can just confirm that with her concierge.

Jeremy Ristau: Dead ex platform specific.

Kyle McCormick: that

Jeremy Ristau: But yeah.

Feanil Patel: Yeah.

Feanil Patel: Cool, And I think that's mostly been working as far as I can tell.

Feanil Patel: In terms of getting things reviewed and landed.

Feanil Patel: And I actually seen very many Roberts come through so.

Feanil Patel: yeah.

Feanil Patel: In that case, I think we're at meeting time.

Feanil Patel: Trying to decide whether I should stop and start the recording or just leave it one day recording. I'm Gonna Leave it one big recording and

Jeremy Ristau: It was very well timed today. Let's go.

Robert Raposa: That answer is almost.

Feanil Patel: yeah.

Kyle McCormick: Doing you want to shrink this meeting down to 15 minutes since that's about how long we spent.

Feanil Patel: Maybe

Kyle McCormick: cool

Feanil Patel: and let's leave it at 30 for now because I think The next couple we might want a little bit more coordination, but then I think in general it'll be shorter.

Kyle McCormick: That's good. I'm going to take a minute to make some coffee. I'll be listening.

Feanil Patel: Welcome welcome.

Feanil Patel: We're just talking through the edx platform bits of maintenance. If you guys want to catch up on what conversations we have they're there. They're also being recorded and transcripted said they'll get posted along with the rest of the maintenance. work But if you have any questions about that while we're waiting for everybody to arrive, I'm happy to try to answer them.

Michelle Philbrick: Yeah, since Jeremy and I believe Robert are here. I just want to make sure they saw my response to they had a question about art triaging edx platform

00:25:00

Michelle Philbrick: osprs, and I just wanted to know if That was discussed at all while you were meeting or not, or if it requires a follow-up.

Feanil Patel: yeah, I think we just talked about it, which was that as the ospr should go to cc's and not to arkbomb at all at the moment. Yeah.

Michelle Philbrick: Yeah, I figured that would make more sense. Given the But if that changes let me know. Yeah.

Feanil Patel: I suspect that my hope is that that will change by having more of the Arkham team as CC's but that's like a different conversation that's happening right now.

Michelle Philbrick: Right, right. Yeah. Okay. Sounds good.

Feanil Patel: And get people two more minutes and then we'll get going. I think it'll be pretty sure today because I don't know if there's a lot of nonx platform updates, but I can summarize what we know so far and I'll mention a couple of things

Feanil Patel: All Okay gone. Hi everybody. Welcome to the main 14 group meeting. Not a lot of new stuff today real quick on the things from last time Michelle. Did you get a chance to seek a third triage person for the time being

Michelle Philbrick: And I have not yet. but after we meet today on the ospr product process, I plan to post something. I just want to have a little bit more information before bringing another person and

Feanil Patel: Yeah that makes sense. It's kind of annoying to have to bring them in when we're trying to move away from the process. But I think it'll make it easier for us to move away from the process and give you guys time to think more strategically about it.

Michelle Philbrick: Yeah, sounds good.

Feanil Patel: and then Tim and Adolfo were working on some docs.

Michelle Philbrick: Yeah, we started compiling things that already exist Adolfo was out this week.

Feanil Patel: States

Michelle Philbrick: So I expect next week will we'll get rolling on it.

Feanil Patel: yeah, okay Tim's good. And I did complete this figuring out what we need. to test on 311 through 12 for the most part at least what we need up for three eleven, so or there's a link here in the United platform meeting about the core python 311 test issue with a drop in messages here as well in the chat.

Feanil Patel: Now has a list of everything that needs 311 support and we're updating them for the ones that we know need 312 support as well. So that should help make it easier to know what to do in the different repos those issues live in the repos that they need to update. So maintenance should be able to easily assign themselves and get going. I mean so far I've seen Maria take on assigned the filters and events ones for herself. thank you to her. But if any of the rest of these have maintenance you should sign the tickets to yourself so that it's obvious that you have seen it in their planning on fixing it the target for the edx platform up. It is Redwood, which is the month and a half from now. So I think we're starting to get into sort of a level of urgency. That's a little higher and this should start getting prioritized for people who need to plan these things slightly further in advance.

00:30:00

Kyle McCormick: just minor clarification that the cut is less than a month from now. It's three weeks from now. It's the release.

Feanil Patel: Didn't we move it by two weeks?

Kyle McCormick: Does anybody on this call know the exact release date or the exact cut date?

Feanil Patel: My understanding is that we've definitely moved it by two weeks, but we might move it by four weeks. which was TBD by BTR Two weeks like that.

Kyle McCormick: Okay.

Feanil Patel: I think the exact cut or move date today is April. I want to say night like 18.

Feanil Patel: Sometime after that so actually no because it was nine. would be the 23rd. And then there's a chance it might move further. By the BTR, which I'm not really excited about because it's making it really hard to plan some of the rest of this stuff. So that's feedback. I'm gonna have for them at some point. both that they decided this and are not communicating it out very far and that it is in the air even as communicated.

Feanil Patel: but this was my last understanding from talking to adolfo's that they definitely moved it from the By two weeks and that they're going to move it further potentially.

Kyle McCormick: Cut it.

Feanil Patel: but for us, I think targeting the 23rd this makes the most sense, but again that doesn't leave us a lot of time and in fact, it actually leaves us. less than a month not month and a half so Yeah, we need to get going on this.

Feanil Patel: Computer thanks for assigning yourself for the couple that you're maintainer of I see that you just did that appreciate it. Yes. So I think the edx platform one is the one that I'm sort of focusing the most energy on because that's core to everything else the other services the notes API which acts and maintains is already running on 312. And testing on 312 I think the tutor updates. I'm not sure if those have landed yet, but I think Kyle you ticketed them up at least so that they are on track to get landed.

Feanil Patel: And then yeah, the other services nothing is happening here. So there's a lot more risk for those not Landing.

Feanil Patel: yeah, I mean there's only to be frank that I am working on the python upgrade. But I am one person and there's no way I'm gonna be able to land all of this. I know a bunch of the maintenance have stepped up but a lot of things are not under maintenance. So we need more people to step up and take on those things that are not under maintenance. I think we're getting to the point where if a thing has a ticket somebody should take it even if they're not the maintainer and we can help them get it over the line because we don't have time for sort of. Anything more complicated than that?

Feanil Patel: so the last thing I have is

Feanil Patel: I've been discussing with I think Jeremy and I have talked about it George Babbie to you and I talked about it about getting the two you team as core contributors just so that we can among other things simplify the process by which we maintain permissions across the system and also make it easier to sort of coordinate a lot of this maintenance work and have CC's that can review things more easily Etc that conversation is moving up to the TOC the technical oversight committee. I'm trying to share that information with them and make sure there are okay with those changes and mostly I wanted to tell the people here that I've started those conversations Upstream in progress so that everybody's on the same page because I'm not sure who else is communicating that information to everybody. So this is an inform that

00:35:00

Feanil Patel: Those conversations are moving forward with the TOC. Hopefully we'll get a agreement from them in the next couple of weeks and then we can make a plan to proceed with how to actually get from here to there. But I want to make sure that the Final Destination makes sense to them. Which is that everybody is a cc.

Feanil Patel: And if you have any questions on that, I can try to answer them now or hit me up and slack later.

Feanil Patel: And that's all I got. super short meeting today

Tim Krones: Yeah, I have one more thing and you might have seen it too because I think I pinged you. So after last week's meeting I discussed a little bit with Xavier in the comments on the Wiki page about next steps for management and…

Feanil Patel: Yeah.

Tim Krones: there were two questions that kind of came up there that I wanted to raise and they're both about automations. So one question is are we ready right now to automate some of the steps that Michelle and I are doing if so, what are those steps that we would want to automate? and then the other thing is sort of more about who would handle that work, is that something that Would be most efficient for accent to handle or is it something where you would be ready to accept an outside contribution for example from open craft to implement some of these automations?

Feanil Patel: And does it need to be accent?

Feanil Patel: I think for the second question is easier. So I'll answer it first, which is that I don't think it has to be accent.

Tim Krones: .

Feanil Patel: But probably the implementation would need to be discussed with us. So that it aligns with the accent security policies and whatnot around sort of securing the GitHub or so. I don't think it would have to be us but it probably needs to be somebody who can work with us on the design of it and then could implement it but I think that implementation help would be very welcome and…

Tim Krones: Okay.

Feanil Patel: in I think that first question is really a question for you and Michelle. And not for so you guys tell me are there pieces that we could automate?

Tim Krones: right

Feanil Patel: I think one of the things I saw in there that seemed like a reasonable thing to want to automate is informing the maintenance on issues directly. When they come in either by assigning them or by mentioning them?

Michelle Philbrick: Yeah, that would be great.

Tim Krones: yeah that yeah.

Michelle Philbrick: They got pinged.

Tim Krones: Yeah, I think these points are all sort of related. we want to let the r authors know. Those are the people that you can reach out to once you're ready for review at the same time. We want to learn the people that are the maintenance, here is a pull request that needs your attention. And then I think that the one thing that we discussed last time was in general to update messaging for the Bots, the stuff that it posts when somebody first raises a pull request that points them to some documentation about how the ospr process works and in my mind that step was a small First Step that we could take and that would potentially be less complicated than starting to think about how to Ping the

Tim Krones: Nurse and stuff like that. So yeah,…

Feanil Patel: Yeah, yeah.

Tim Krones: I think that the way I see it. That's probably just a contribution to the web. What was it called the Bots repository or…

Feanil Patel: WebEx yeah, yeah. That's super easy.

00:40:00

Tim Krones: web Hogs Is that something we should start with?

Feanil Patel: That's super easy. I just linked to where those templates are. So if you want to change the wording on that. Just open up before request tag me on it. I can help you. Get it over the line.

Michelle Philbrick: And in Tim, once it would be good to add the product thing in there as well. It's like hey, wait a second. Do you you know people that aren't aware of the product process. If you know something is we'll end up needing product review something in that message that says …

Feanil Patel: Yeah.

Michelle Philbrick: if it meets these few requirements then you got to do this instead or something.

Tim Krones: But yeah,…

Feanil Patel: Yeah.

Tim Krones: yeah, I think that was the impression that I got from the conversation that we had with Adolfo, between the three of us after last week's meeting too is we kind of have all the documentation already. It's a bit spread out in different places, but it's mainly a matter of getting people's eyes on it and informing the authors and informing the maintenance about it.

Feanil Patel: Yeah, so I think if you want to update at least the pr templates, which will help the authors. There's also I think a piece that I would suggest you guys experiment with is which is I think we could add the name of the maintainer to the comment without mentioning them saying just in code blocks or something where it's like when you are ready you can mention this. And that will allow the person who is ready to review this.

Feanil Patel: To know that it's ready.

Michelle Philbrick: Yeah, that would be great. So they don't get pinned.

Feanil Patel: Immediately one things come up, but then the author knows how to get the attention of the maintainer and it can all be automated. Yeah, exactly.

Tim Krones: That was my feeling too.

Feanil Patel: Yeah,

Tim Krones: It was like if we ping the maintenance too early then sometimes a lot of time passes until the stuff actually gets ready for engineering review. And at that point we haven't really gained anything from the automation…

Feanil Patel: Yeah.

Tim Krones: because then Michelle and I need to step in and be like, hey remember this pain so

Feanil Patel: Yeah.

Feanil Patel: I think getting the reviewers on their only after the authors have sort of checklisted all of the important things that we know that already makes a lot of sense.

Feanil Patel: and then yeah, that'll be a slightly bigger change, but I think you guys might be able to make that to the Web book spot yourself, but that automations already in place. So any improvements there are welcome and those will sort of flowing pretty easily There's probably less of a design discussion needed around that.

Tim Krones: All right.

Feanil Patel: I will say for anybody touching the open edx web host code it…

Tim Krones: Cool. Thank

Feanil Patel: bad it is like net has spent a lot of time cleaning it up before he left but it is just not the most beautiful not the best organized stuff there is and it's a little confusing because there's a I would say four generations of different ways of talking to GitHub that are sort of embedded in there to various degrees.

Feanil Patel: There's a lot of it that's been cleaned up. But if you're confused by something, feel free to just ask questions. There's a open edx webhooks Slack Channel.

Feanil Patel: and you can ask questions in there and I can do my best to help but require some code splunking.

Feanil Patel: Alright, does anybody else have anything they want to discuss?

Kelly Buchanan: I'm just a quick question on the tasks.

Feanil Patel: Yeah.

Kelly Buchanan: I'm just trying to understand get Hub issues asks thing. How do I find the tasks for the services on this?

Feanil Patel: Yeah.

Kelly Buchanan: Issue, credentials has one but it's just a checkbox. Are they?

Feanil Patel: If you click on the item. we're on the same page Kelly you're looking at this ticket in the next platform 34 to 29. Or you're looking at a different one.

Kelly Buchanan: No, I'm looking at public engineering 234 Which hat is like a parent that lists a bunch of stuff. because you 29 is just edx platform.

Feanil Patel: Okay. yeah.

Feanil Patel: Yeah, yeah, there's only a checklist item here because there isn't an issue yet. So we can make one pretty easily but nobody has gotten around to even making the issue for that yet.

00:45:00

Kelly Buchanan: okay, because a bunch of the other repos do have issues created and I was able to assign one to a team and that is very convenient, and I'm sure that The credentials maintainers would be happy to do this.

Feanil Patel: Okay, yeah.

Kelly Buchanan: I can create another issue.

Feanil Patel: Are you able to do a convert to issue on this one or…

Kelly Buchanan: I don't.

Feanil Patel: is that not a power you have right now?

Kelly Buchanan: I don't know how to do that.

Feanil Patel: Okay here all that one second. I'll show…

Kelly Buchanan: Okay. it's very

Feanil Patel: All So here's the ticket you're looking at. Yeah.

Kelly Buchanan: yeah, it looks very cool. Yeah, exactly, see how there's just the checkbox.

Feanil Patel: Yeah, so if you go over here into options. You can convert to issue.

Kelly Buchanan: Yeah, I just don't have the magic the juju.

Feanil Patel: Okay. Yeah. Okay. that's good information and…

Kelly Buchanan: Yeah.

Feanil Patel: I'll just Transfer this over to the credentials. Service, so it's lives over there.

Kelly Buchanan: me

Feanil Patel: And then it should be.

Kelly Buchanan: Matured last minute and…

Kelly Buchanan: GitHub no way.

Feanil Patel: Yeah, so that is An issue and it shows up as the issue here. And if an assignee is there it'll show up so you should have that one now. If there's other ones we didn't get around to the rest of these because I'm like I have no idea who's actually going to be working on them yet, and I wanted to focus on platform. But if there's other services that you're aware of that are under your purview. I'm happy to help with the process annoyance until we figure out how to give everybody the right permissions.

Feanil Patel: And maybe I'll just do the rest of these after. This meeting just so that they all exist in the right place.

Jeremy Ristau: Random question should I expect to see a parent ticket? the one that you were just showing on the open edx roadmap board?

Feanil Patel: On the open experiment board. I believe there is an upgrade ticket. I don't think it's a parent of this one yet. Just because putting the upgrades on the roadmap was a fairly new idea. So I don't think I've gotten all of the issue linking aligned yet. But we can do that.

Feanil Patel: Using you're saying the product roadmap. Yeah.

Jeremy Ristau: the open edx roadmap So it is not described as product specific which is why I guess I'm asking.

Feanil Patel: Fair enough. Yeah.

Jeremy Ristau: And for this specific example, I guess there's a question but also for the general does wide scale maintenance work show up on that board. is there one place to go to see what's happening or

Feanil Patel: So that is the plan we're tracking and I'll chat with Jenna about this and make sure. Either that it's on here somewhere. Or I think it should be on there and we've been discussing the upgrades in the product roadmap meetings. So it's on the spreadsheets that's generous using behind some of this stuff to track higher scale work and I think those are public but again, I understand having more places to look is not the answer so

Jeremy Ristau: Yeah, even which tab do I look at to see the fact that python shows up somewhere is tough.

Feanil Patel: Yeah.

Jeremy Ristau: So if any simplification around that process so that we can have …

Feanil Patel: Yeah.

Jeremy Ristau: this is the place that everyone can go to see the work in flight.

Feanil Patel: I don't need to be the one to check in with Jenna about whether or not this needs to be done Jeremy. Do you want to reach out to her and just ask her if upgrades can be on this? Board and how we can get them there.

Jeremy Ristau: To quote a famous person. I once knew I can definitely do that, but I don't have to be the person who does that. Yes, I can absolutely ask.

Feanil Patel: Yes.

Feanil Patel: you can delegate to Robert if you want to I'm just

Jeremy Ristau: Yeah, yeah, I'll bring it. It's just

Feanil Patel: yeah, I have a bad habit of just being like that needs to be done. I know how to do it. Therefore I will do it. And what I would love is for the maintenance working group to be more people like that that aren't just me and So I need your help to make sure I don't do that. And That's in everybody. Not just Jeremy's who's helping me. So please volunteer for things because it is really awkward to ask for help and then wait awkwardly in silence. So

00:50:00

Kyle McCormick: Feel free to mention that Daniel and I want this to happen though. So it's not just you trying to add work to Jenna's play or something.

Feanil Patel: yeah.

Feanil Patel: Yeah. Yeah, I think we just want to know if we can start tracking items there and what she wants the process to be there. And if you come back with that process we can document it and make sure it's something that we're doing to make our stuff visible there.

Feanil Patel: We're three minutes from time to anybody have anything last minute or any questions?

Feanil Patel: awesome thanks everybody. I really appreciate it.

Feanil Patel: That you'll hear me say And again Python 3 11 3 12 upgrade. Please work on pick a library anything that looks like it has Python and make sure it runs on 311 and 312. If you're not sure which ones to pick up one of the ones under edx platform.

Feanil Patel: There's a lot of them. You can assign them to yourself if you're working on them Please assign them to yourself. So that we know that you're working on them. If you have to stop working on them, please say that on the ticket instead of disappearing. All communication is helpful. Thank you. I think that's all I have.

Feanil Patel: Thanks, everybody. Have a good.

Kyle McCormick: See you later.

Feanil Patel: Your morning afternoon and evening.

Robert Raposa: Thank you.

Chintan Joshi: there go by

Meeting ended after 00:52:24 👋