Ryan how's it going? Good. Either Adobo. Hey, hey Brian jagadesh and our neighborhood AI.
Yeah, every time I don't know the last time I fed in a meeting without Xavi.
Having a bird's eye view of everything that's going on,
I think somehow got associated with a calendar like a shared calendar and now it's just every single meeting. It's It's wild.
I'm gonna hijack the last meetings page because they happen a second
first day of the month
Yeah, Thanks for the reminder and to go do all my bill payments stuff and whatnot. Yeah, me too.
So this is the link to the notes here in the chat.
And I'm going to share my screen shortly.
All right, there's not not much here but that doesn't mean we don't have anything to talk about. So anybody have anything specific they want to?
If not, that's fine. I have plenty of topics I can at least announce or talk about. First person I guess most important is you've been probably hearing, as I think I said last time some folks are were laid off at to you and that is totally true that that's going to affect the front end. In terms of in particular capacity for maintenance of right I if I remember correctly last time already asked for volunteers to main pain, different repos. And that still stands though. We're not even sure yet which repos are actually going to be dropped by to you as maintainers it's still up in the air but if you or anybody in your org is excited about a particular repository, and they're even if they're not yet knowledgeable at it, they want to start doing that or taking it up. Now would be a good time to do so. It's like me and Brian were were first in a few repos, but we're not versed in all of them. I don't think that's true about anybody in the community. So picking stuff up from scratch is totally fine. If you haven't been to the maintainers working group meeting that happened earlier today, it's a bit a tad had early for Americans in the East Coast even more as you go west. But it was done to sort of be a middle ground for folks further east to be able to join us well. We are going to be discussing there the particulars of who's maintaining what cross repository, tasks that need to happen and so on. If you're interested in any of that, I think the next one is going to happen in a couple of weeks. Keep tabs on that. There's a channel, a new channel and on Slack board. WG WG slack. What else? Anything important we want an analyst Brian that we discuss in our we have we just had our annual Oh hands at XM and we talked a lot about the front end so I know there's a lot mentioned. I don't know in what order what's more important. What do you think?
Um, we can we can look through the notes that we have from our recap yesterday and see if anything pops up. I guess we could announce this stuff about The MFE fees that were in quince as tutor plugins that we've decided we don't want for redwood. So that is front end debt payment and front end APP e commerce so those are
probably not going to be in revenue read with. Yeah, yeah.
We have them marked as no in the do we want it for redwoods. Awesome, so yeah. That seems like a good thing to share out.
The whole ecommerce thing is like nobody wants to maintain it. And nobody stepped up to do so. We're not even sure many people use it. So where like the idea is to just move them to unsupported at some point.
Yeah, it looks like for Neil is going to create the depper tickets. Or maybe he just noted that we should make depper tickets for those two MFPs Yeah, I think the path forward for E commerce that we were discussing was allow better integration with whatever ecommerce systems people are using instead of trying to roll our own
okay
all right, and other news. Pretty much keep going forward really strongly. That is definitely going to be in Redwood. Or I hate to make such a strong promise but that's the target and recon gang and open craft are working on it and in different parts of it. And it's looking good for redwood. Have no jangle rendered views for studio, which is my book pretty awesome. I am I'm basically reviewing PRs in recon gang and Jana is leading the project because it's a it's a it's a couple of Acts and funded contributions. But if you have any questions, feel free to ask how that's gone. There's some important stuff being discussed there, including how to actually present X blocks in an MFP world if there's any better way than to what learning MFE does it right now, which is basically just AI framing a unit so pretty, pretty important architectural discussions happening there. I'm encouraging the folks working on it. Basically GlitterBug gang, at this point, to come up with a DRS and we can discuss it more broadly. I wish there was one particular or a couple in particular I wish he had already had time to post so we could discuss them a little bit here but that's that hasn't been the case yet. Maybe next time, but I will announce them in the front of the working group when it comes. I know Brandon's particularly interested in looking at it or some of those so yeah. Um, what else?
You mentioned starting work on putting together an app for the pirate stuff.
So yeah, pirate. I just, we've talked about it in our all hands I just talked to Sargon a little bit about it. So we're going to build up some steam to get that going faster. So we can expect that to be revised. And then real reviewable states by the end of next week. And yeah, it looks like we might be might have a new funded contribution going on, or we'll see. Not sure yet. But keep that in mind.
And finally, the pluggability stuff.
Yeah, there
are actually three PRs in flight. None of them merged yet. That tackled applicability problem in the front end, from different angles. There's one buy to you. which up until a couple of days ago until yesterday, we weren't sure what was going to happen with it because of all the layoffs. But it seems that for at least six months, they will be able to work on it. So we can expect the learning MFE to land or the learning learner dashboard the MFI to land an iframe based plugin system. So we're going to have that where as your next thing, submitted a PR to frontal nap communications basically implementing one of the concepts that Braden blogged about and presented during the replicability Summit. He's been in that PR making a couple of reviews, which is great. Pretty excited about that one looks very flexible, and very useful. And then there's a third PR to force offering which is a more specific use case. Which is also fine. And it's one that depends on plug ability on plugins and the plugins in the backend as well. So depending on which plugins you have in the back end for index platform there are entries in the Resources page in the course authoring Yama fee for configure each of those. So Braden came up with a way to do that very. In a very pluggable way that gives us the best way to so that's likely going in all lot of a lot of excellent displays as you can see. I'm gonna be trying to make this all happen with brands help in the next few months, hopefully some of it before Redwood we'll see what we can make, by the way. I have to mention that. During our hands, we had one specific meeting about releases and how to test them. And we came up with very we think, very good ways to make the release. I'll try to put it less hectic at release time, and more evenly paced out. So everything's tested properly and so on and so forth, and developed properly with releases in mind. So if you are in the BTR meeting or you're interested in the subject, we will be talking about all the suggestions we came up during the next one. I think the next one is on Monday.
Yeah, we did a good job of doing a lot of discovery and just kind of what are the pain points, at least from an axon perspective, what have we seen as pain points and so it really is just kind of what we came up with as a way to start a conversation about how to improve the release process. So we've gotten to a point where it's like, alright, we have something to share, but there's definitely a lot of room for input before trying to implement anything at this point.
So if you're interested in that, make sure to join the next meeting. As far as the front end is concerned, I guess the impacts are going to be around how my fees are developed and tested during development. More more than
Yeah, yeah, integrating integrating using tutor and verifying in tutor into the review and development process will be huge because sometimes we haven't caught things until way late on and it's like oh, this has never been tested in tutor and the configuration doesn't work in tutor and things have had to been have had to be developed. When we were ready to release the feature and thought it was done because something wasn't working and it hadn't been tested and all of the places that we expect things to be tested. So just getting people more consolidated on let's test it in environments that match with the environments that we release in. will go a long way for preventing those types of surprises. Exactly.
And with the end goal, having a better relief, of course. Yeah, absolutely. I think but to be clear, I think we've been doing a great job with releases as a community. But there's always room for improvement. And if we can make the developers lives easier, or the testers lives easier, that would be awesome. We're probably going to be making the developers lives a little bit harder, but for a good reason. Right to get better and if he's in the Yeah,
absolutely. And I think one of the main ideas of doing more MFE development in tutor is to catch the pain points and get people talking about it and then have the improvements. That we want. Not just be Hey, I tried to use Twitter to do a thing and I like how DevStack does it better so I'm gonna go back and then not actually have any pressure to make tooter a better development environment for MFE development. So having more people using Twitter as a development environment for MSPs will really just put the pressure on and make it so it needs to be good because this is how people are doing it. And not having a well we support both strategy, kind of we'll get the effort for develop for developer experience, consolidated on a platform that is more in line with what we released on so yeah,
totally. That's that's a very important point like I made that very point in the maintenance working group meeting, when we were discussing how our X platform would be maintained and whether PRs can still be reverted by to you or not. And at some point, we came to like the expectation that we avoid reverts and stuff like that people. There should be a better checklist in each bar. So that, you know, developers can make sure certain things are working and one of the things I literally think we should defend is that ndpr should work in tutor, tutor deployment, particularly to edX platform and MFPs that are in the release. We might even automate some of the
Yeah, yeah, the work being done on PR sandboxes could definitely help with that automation because those are fear based. So a spin up a sandbox is working there. Cool. That means it's working good. Tutor. If and for small changes, people won't need to change their immediate development environments. Right. But as far as we move to do bigger development stuff, where something needs to, we need to add something to the config and we need to make sure that that works with runtime config, and we need to make sure that something that we're building works with different package versions and all of that kind of stuff when we're doing those bigger things. Sometimes those have been developed in very well it works for what we want to your needs ways, but not in a this works for everything that community needs way. And so ensuring that things are built in a way that works for the entire community is really the focus of this
yeah, that's, that's the release passing conversation and quality conversation. There's one last thing we we started doing. Right, Brian submitted a couple of prs. Yeah,
all the PRS have submitted so far have been merged. I am moving forward and continuing. I have a short list of let me find the ones that I'm still working on. I still have work. I have done template application authen and communications. I still got account course authoring discussions, Gradebook learner, DAF learning or a grading and profile to do the upgrades on. I think some of them will be easier than others. But basically, it's ensuring that we're installing. We're installing everything from the Open edX namespace now. So that means specifically front end, build and Paragon, those are the two that have been moved over. And then we have new breaking change versions. Of some intermediate dependencies that rely on the Open edX namespace things. So it's something where it is just kind of a process of ensuring things are updated and ready to move over to that namespace because we're trying to move everything over from edit at edX to be at Open edX when there are packages that are part of the Open edX organization being published out. And so this is just kind of a step along the way there.
Yep. And if anybody wants to help, I know jagadesh asked how he could contribute. I pointed me to this effort. And in particular to though, like I picked an MSc that I was reasonably up to date, make his job a little bit easier. So I suggested he look into doing this with the learner dashboard. Yeah, if
you want to take on learner dash, I will make a note to say that I will let you do that one.
If you want to do that. Yeah. I have one question. Just we need to rename, like namespace index from open X. Yeah, we need to build some command. Yeah. Anything else? Because I can't find any notes. Yeah, it will help me a lot. But I have this one question. I
find the PRS and then I can link you to the ones that I have done. I think that will help a lot. Yeah,
I sent one of them. I forgot which one. I think it was the front end of communications.
Yes, yes. Yes. Yeah.
Yeah, let me find
awesome. And also, I would like to also work as a maintainer if I can do some contribution here as well.
So wow, that's That's awesome. So basically, like I'm trying to get our Board of better organized, I mean, it's already organized. It's just not updated. To make sure the stuff like this one that we're working on now gets the attention it needs at the top right. So one of the things I want to do is create issues for each of the repos that needs this work done so that somebody can come in and you know, pick them up and assign themselves and work on it. So directly just by looking at the board
as a method drop a message in working group maintenance. Yeah, I would like to work here contribute here like this type message. No,
sir. Yeah, sure. But like in this case, you can already start on something right. You already. You already have something to work on. Yeah. Yeah. So so then we could take it from there. Like at a certain point, if you feel more comfortable, we can nominate you to be a core contributor. At a particular repository. Yeah,
yeah, that makes sense. Yeah.
And generally in that nomination process, we like to link to PRs that people have already done and say yes, they know this repo, we can see that they know this repo because of this PR and this PR and it just makes it easier for people to say Yeah, sounds great. Let's do it. Actually,
I done lots of contribution in the application Working Group.
Oh, cool. So which repositories Have you worked on more?
I think many I create many of prs. More than 20 to 20. By and that is successfully modular as well.
That's great. Yeah. Awesome. Yeah. It's great to have you. Great to have your help.
though. What is the process of core contributor? Yeah. How should I get a maintainer? Yeah, feature FYI. I get as a maintenance. So I don't know the process of this. Well, the
process is basically, first. You wanting to do it, because there's some responsibility associated with right. The second the second step is picking a repository that you want to work on. And usually you pick one where you already have a couple of contributions and so you know, we can nominate you for that repository, and use and points to your prs. Or your contributions
scored. I need to create any ticket for this. Yeah.
No, not really. Not really. This is this is done. I guess the first steps are done relatively informally because it's been here is the first step.
Currently, some day ago, I don't ever access completion, so I create a ExIm ticket. Then Sinaia I don't know the specific name. Ha ha Serena. Yeah, he gave me an excess of this. And now my name is right here. Oh,
you probably need a triage axis. Yeah, that's right. Is
this the process is like sim.
Not quite. process is generally somebody will make well nominate you on the forums. And you can nominate yourself. I nominated myself for CEC to be able to get there and then people will come in and comment and say yes, here's a couple sentences saying why I agree with this nomination, and I support this. And then after the nomination period ends, it either goes through or it doesn't and then you're a core contributor, along with core contributor status. You are you're either getting it for a specific repo, or a group of repos. So we have we have like all the all the MFPs, right, that is a group that you could get core contributor access to and that would allow you to merge PRs in any of those repos. So that could be a bit
clearer. Yeah, I don't need to be a core contributor to contribute. Okay. Yes, that you won't have merge Jack. Yeah, needs merge Jackson. Only needs more taxes if you want to help maintain the repository.
Exactly. So that's why core contributor and maintainer kind of go hand in hand. The idea is that the access to merge to a repo comes with core contributor status. And the responsibility to ensure things are reviewed and merged in a repo comes with being a maintainer and being a maintainer and being responsible for reviewing and merging things but not having access to wouldn't be a problem. So that's where we want core contributors. To be maintainers.
Okay, thank you.
Go ahead and call it
Hello, everyone. Sorry, I'm late for this meeting. So can I be the part of the action just like admission? Contribute to updating and making improving the operators? Can I be, can I make it? Also,
of course. You don't even you don't even have to be a programmer. You don't even have to do to do any coding. You could be we've had core contributors that our testers mostly like Yeah, unfortunately he he just left the community because you know, his his word. But we have poor contributors that work on documentation. You have core contributors that work on the front end exclusively others that work on specific repositories exclusively. Like I don't know. EdX platform obviously is one of them. So, basically, the first thing you should do, and this should come reasonably naturally, based on the work that you're already doing, right, there's probably a reason you're here. You're working with Open edX, right? So based on the what you're using Open edX for and the modifications, you're making an Open edX. And if you contribute those changes back to the repository where you do that it's going to be a natural one for you to want to become a core contributor. Maybe right. So it's really up to you. Which way I say the first step of the process is just first, you're going to want to the second is take a repository. Okay? But it should probably repository where you already contributes to, but you shouldn't necessarily start contributing because you want to be a core contributor, although that's okay. Right, that's perfectly okay.
Does that make sense? Yeah, sure.
Oh, well, the second item in the table MF is going to be unsupported soon. I wasn't in this meeting soon as I mentioned. So can you please make a quick note about this? And if he's going to be ordered soon.
Yeah, so yeah. Brian, go ahead.
Yeah, so the payment and E commerce MFPs. Those we have decided are not likely to make it into redwood. The idea behind that is that integration with existing ecommerce systems is a focus above, trying to build maintain our own e commerce system. And there will be deeper tickets created for both of those. So further discussion about that will be able to happen as a part of the deprecation process. Thank you.
Basically, if if you for instance are interested in E commerce or payment or something like that, when the dapper ticket comes out is where you jump up and say hey, look, I actually use this. I, you know, you can totally object to a deprecation it doesn't mean it will stop. But then the question is going to be alright. Are you willing to maintain this would be the next question. And it would help a lot if you were a core contributor in that repository. So because the decision is always like, how much work are we going to need to put into this board versus how much benefit the community is getting? especially as it pertains to axioms mission to improve learning everywhere, right. So when payments and E commerce come up, well, does it align with our mission? Maybe Verda. And, but it's a maintenance burden greater than important maintenance burden. So when we say we want to deprecate that means well, we don't want to maintain it. And part of the process is then finding if somebody does and if somebody does, what could happen is the payment any commerce repos are moved to or actually copied or forced to some other organization that then maintains. Yeah, that's roughly how it works. Usually, after the application process. The repos just moved to an unsupported organization or just forgotten about it's wet rare that the community picks something up like this. The first
Yeah, and it's not like we believed three bows they just move people can work from unsupported we just don't support them. So yeah, the code still exists.
Exactly. It's called deprecation. Yeah. But deletion. Yep. Yeah, exactly. Okay, folks, I don't anything else brand. Anybody anything else. Anybody have item? I have anything more.
You mentioned something about a funding contribution for parallel work. Could you expand upon that?
Basically, it's looking like we won't have any internal capacity to take this to completion. So we're going to be looking for people to help via a funded contribution. I don't know what the budget is going to be. I don't know when it's going to come out. Just a heads up that it probably will in the next month or two.
Okay, great. I'll be keeping an eye out for it.
All right, if that's all, I'll see you folks in a couple of weeks. Sounds good. See everybody? Cheers.
