Sorry for the backup in the waiting room there. I didn't realize that nobody was looking let him know Wait just one more minute
all right. I think we can go ahead and get started
gives us a title before I can circulate it
Alright, so let's do the typical approach. So a quick round robin of updates for all of the In Progress projects coming in hot with roles and permissions. So as of this week, unfortunately, Brian is no longer with edX. So Brian was the product lead who was driving the roles and permissions work at edX, as of this week, is no longer there. So and there's also an open question I think as to whether this is going to be prioritized on the open or on the roadmap going forward. I suspect probably not. Given the trends we've been seeing this week, they've been dropping quite a few projects related to the teaching and learning platform, and I suspect that this one is going to be dropped as well. And so that kind of leaves an opening for this to be driven by the community. I think it's something that Aksum can kind of coordinate and drive going forward. But I'm not sure what the timeline is going to look like. We've already got quite a bit on the roadmap on the roadmap for Redwood as we as we already have it, but I wanted to touch base with you fleet basis this is probably going to impact you most directly with the work with the Spanish group and get your thoughts on what might be immediate blockers or concerns or red flags if x is no longer working on this as of next week.
Yeah, there are some some parts of that work that we do in order to complete the last four goals there. We have three goals or four, three goals that impact the community for that flexible groupings, or project. And what I'm what I'm mostly worried about is if to you is reducing the output they will have a teaching and learning not only will they no longer do or back but also will then not review the PRS or therefore block everything or just by community input. Could we continue moving forward with your two in which case we're not so blocked there? We could take more work on our back. It's like a balance there of not only can we take more work, but if we take that work will be blocked will we be blocked as we have been in other places? So
yeah, I think there is going to be a concern about to you reviewing prs. But that being said, with projects that we're taking on select the content libraries project, for example, we're going to be triaging the PRS that come through with that this project going forward. Internally at Axim. We're not I mean, not not internally like we do with the community on board will be triaging and coordinating those with the intent of, you know, mitigating any potential blockers from folks that to you not being able to review them. And if if we could take the same approach with their roles and permissions as well.
Good. In that case, they're the exact scope that we could take on and what the current status of the what has been done up to now in your back. Is that enough or not? I don't have that top of mind, but I can circle back with my team and I'll let you know.
I'll touch base with Brad as well because I think he's kind of the interim as of this week Product Manager for for roles and permissions with Brian not being there anymore. And so if if they are going to end up dropping it then we can get with Hilary who was the engineering lead and with Brad who is sort of the interim product lead, and we can do like a very thorough status update and get a sense of make sure we know exactly what work has been done and what hasn't been done so far. Yeah, it's good.
We knew we knew from the beginning that this wouldn't cover all the all the scope that we wanted, so it was just a matter of we wanted to build on top of what they had to us to not make a parallel system for for permissions. So we'll see. Okay,
sounds good. So it sounds like a next step would be that possible handover meeting? And so I'll keep you in the loop as to what I hear from Brad in the next day or so. But I think we'll we'll know probably by early next week, whether what's going to happen with that project. File Management is luckily done. It's going to it's currently live on edx.org. And so I'm now in the Redwood planning so we'll put together a testing plan for this and the new files and management about manage. Sorry, file management page will be available in Redwood tied to this as well. It looks it's looking like fingers crossed all of the studio. conversion to MFP will be complete. So this was part of this project. There was some additional work as well to add new features and functionality. But one of the biggest, biggest parts of this project was converting the page to the new Paragon framework for as an MFP. I mean, it's looking like all of studio is going to be able to we'll be able to complete all of studio in terms of MFE conversion and Paragon conversion for Redwood as well. So good news on that front
and find me there. Last time we spoke with Brad he said that this was happening in maybe it was the timeline was around the waiver and he said this was going to happen and he would send me the branches but this was been worked. He never did but I found them anyways. And it looks like it is present in causal theory. And at least to my external view, I don't know if the leads are like feature parties complete, but it looks like is there and that that impacts us for the for the studio home later on the list but looks like that is unblocked so so far so good.
Well, aspects is Chelsea on the call. Don't think so. There's been quite a bit of movement Sorry to keep coughing. I went running this morning and it's very cold. And I seem to be coughing now. I'm just going to find that we have a complete set of requirements now for aspects which is very exciting. One second here.
circulate this
so
here is the I've just added it to the agenda. Read who are aspects product requirements. Let me share my screen here to give a quick overview
alright everybody see expect to be one document. Cool. So I'm gonna go through this in huge bonuses. Chelsea is the product lead for this, but she's got a number key use cases here that she's been using to drive. She we're going to be dividing this into a number of different dashboards. So aspects we want is going to launch as a new set of features in superset. The eventual goal for future releases is to have an in platform rendering of those reports ups in some way. But for the MVP in order to get this out the door we wanted to focus more on speed and agility. And so we're going to be building all of these new reports and dashboards first in superset with some sort of wait for folks to be able to log into the superset from from the platform, and that's one of the features. Yes, flipping.
I was gonna mention that for the project. One of our requirements was to put that in independent, but that turned out to be super easy, and we made up an extender plug into that so it's not like I understand not being part of the one and I completely not like a super blocker if someone definitely wants to have them in. Yep. It's relatively easy technical.
Sounds good. So maybe I'm in terms of we can scope the requirements a little bit to include the, the plugin for the MVP, and then we'll look at maybe building on that down the road for a platform like, you know, platform approach to any plot because
blogging is limited. It only puts them in the instructor dashboard in the instructor taps. But it could it could be as the exact same thing everywhere else in the planet for money.
So she's been thinking about grouping or category categorizing the reports and dashboards around three, three categories. One is around enrollment. And there's a number of different use cases outlined here. One around learner engagement, some around performance. And then one of the a lot of this is built on insights already provided solutions and I think better graphical representations of the data to make it more readable and more engaging for look for core staff. One of the new things that we're going to experiment with in the MVP and put out in a very kind of MVP, MVP fashion is is approach to the problem or the user story of, I want to be able to track individual learner data as well or data for small groups of learners. This is something that she heard quite a bit in her interviews. And so we wanted to include some sort of MVP approach to this in the in the first release of aspects as well. And so there's going to be a set of reports as well for small groups of learners, or subsets of learners who meet certain criteria, as well as a set of reports for individual learners. And the focus here is going to be on mitigation and identifying at risk learners first and foremost. So that's kind of the use case that we're building on for the MVP is how can we identify learners who are potentially at risk of dropping a course or at risk of, you know, failing a course or not doing well on a course. And so these reports are built to support that particular use case. Um, in terms of deliverables, there will be a course dashboard in superset, which will aggregate all of the course level data. There will be a way in some sort of way for instructors and course authors to navigate from the dashboard to the Open edX LMS fleabay. Maybe we expand this conversation and say that we actually build on a plug in here. That's that's a possibility. There will be some sort of learner group and individual learner dashboard and superset. And then there will be a very basic operator dashboard and superset as well. primary focus for v1, our course authors, instructional designers and chorus. Teams, we're really going to focus on data visualization and nailing that as part of the MVP. I'm hoping hoping to work with a data visualization specialist as part of this project. And so that's, that's the scope for the MVP. What's likely to be a fast follow for this is going to be cross course and hold incidence reporting. We were experimenting with the question of learner demographic data. This has come up as an important use case for research. There's a lot of questions around how we would gather that data, and also what our platform point of view would be on in terms of aggregating it and making it out it may not be appropriate as an out of the box capability, but that's for future discovery work. And then more configuration options, so giving course teams the ability to configure custom learner groups, as well as some sort of better embedding of the dashboards from superset into the open edX platform.
So I've linked this document sorry, in the in the agenda for today, um, feel free to take a deeper look at it, feel free to make comments on it. This is the point where it's ready for open review from the community. This has already been circulated to the product working group. It's been circulated to the data working group so happy for folks to chime in with your input.
Anybody I see that Christian from our side of recommender and some of those that's on my to do list.
I think we have a meeting later today as well with Chelsea to talk about possible preparing implementation of this as well. Yeah. Any other questions, comments?
Maybe just want to up to the timeline. Of these. When would we want to have the MVP like is that related to the record release? It's something that we would like to put, like when with the same, I don't know, June 9 date or something like that. Yeah,
it's, I would like to tie it to the release even though it's not directly tied to like the code cut off with the only getting that some like the one feature around potentially linking folks out of the LMS into superset. But other than that aspects can kind of develop on its on its own timeline because it's being all developed in superset. But that being said, I want to tie this to the redwood release so that we can have a narrative around us a set of features that are going to support the competency based education in Redwood and aspects is a huge part of that. So the goal is to have the MVP for this done by like early June. So that we can do testing of it kind of alongside alongside Redwood testing.
Even if he doesn't make the same data for the cut off even if he doesn't make the release. The idea that we can tell people it's worth upgrading to Redwood solid you could ask as is.
Yeah, that's that's the intent and the technical standpoint.
You can do that from the Naknek release app like there is no there is nothing that is blocking the connection of those two parts, but it requires internal workings and basically it requires that you have Christian in your team is not like is he's the only one that knows how to put those pieces together. But anyone else could start from reading done and that's good. Yeah.
And that's the messaging we want to tie to it as well is aspects is sort of, you know, available outside of a beta environment. It's it's the full launch for redwood. And the nice thing too about how it's being developed in superset is that we can do more incremental releasing, we don't have to necessarily wait for sumac to do the next release. We can be continuing to build iteratively on the reports and the dashboards, even on like a monthly or a quarterly basis and in a superset which is exciting so that we can do continual development.
Yes, absolutely. I suspect that but I'm jumping ahead to some discussions we might have with customers, but not everyone will be interested in doing migrations in between releases, and we'll just jump to the next one. But that's perfectly fine as well. Yeah.
Any other comments or questions on aspects
before we jump to agree to discussions I saw that Brad hopped on and Brad, we've already gone through roles and permissions and file management, but I wanted to circle back and see if you want I wanted to add any context to that especially because bluebay and the Spanish team are doing quite a bit of work on roles and permissions and maybe in a position to support some of that work going forward. So any status updates would be hugely helpful if you if you have them and realize you may not
sure, I think I could do like a really brief one. I know there's a bunch of people who I've never met
and a bunch of people will have anyways I'm Brad I'm the basically Product Manager for edX studio. As far as roles and permissions, adding permission checks in locations where roles are currently checked, and in new places in the code that will allow for a fine grained content over access to our specific elements. That's basically
the progress update.
Does that basically what you said yeah,
no, I did not.
know if that means the up to that scope is still prioritize, and I don't know Hillary and the technical team will continue working on that until they reach that state. Or is that like done in master and we just need to wait for them. It's really Yeah,
it's hard for me to answer questions about the future right now. I'm like, what the plan is to continue. But I probably would have more to say but I just I can't really update. So
these are the plans you're going to do and we'll see what happens.
Okay, that's helpful. Thanks. Good. Okay, I'm Cassie. Any updates on grid discussions?
Um, yes. So we actually met with the team from ESU. Yesterday. We they've had a bit of time to go through the first draft of the spec. So Elizabeth was on the call as well. And yeah, so we basically we've looked at it we've reviewed what the Asus goals are and we've we need to rein back the scope a little bit, just to make it more MVP like so we are I'm going to be working on that in the next sprint. Basically raining things in making it very sort of, I wouldn't say basic, but just just pulling it back and then we'll take it from there. Once everyone's happy at ASU with a scope. The direction we're going in we're going to do an estimate and see if we can, they can fund it, and then we'll release it to the to the community to to review.
Cool, thanks, Cassie.
I'm still home. Felipe. I think this is actually on your back burner at the moment, right? Yep. It
wasn't gonna because we were waiting for The MFE code to be available, as I mentioned, and then maybe, Brett, you can give me a confirmation of that. But I read through the code maybe last week or one week before and I found the studio home parts and it looks like it's working. I don't know if a feature party is like 100% complete, but it looks like we can start building on top of that.
It's 100% Complete.
That's wonderful. We don't have a because the especially continues, moves onward and we are consuming the capacity all over the place. We probably are looking to like the more strategic changes that we want. We have the the large like vision figma for the long term vision of where that needs to go. And we would be focusing on the filtering capabilities like being able to type and just the list shows you the courses that match your query, sort of I need to do some work of scoping exactly up to what point we would plan to to involve ourselves, but probably strategically in that area like the filtering capabilities. That's where we want to put our efforts
Yep, that sounds reasonable to me, and that would be a good I would position that just like a first phase. I think that's totally fine.
Add I think it's going to try and hop on to the half hour so we'll hold off on any order updates. Um, so in terms of the central LTI configuration, there's a couple of strings of work that are ongoing for this. The there's a team at nginx that's working on designing an authoring environment, like a UI for authors for this. There's three kind of like three sets of features there. A set of features for or like a set of UI for authors to be able to set configurations once at the course level and then reuse them both within the course as well as for other courses namely course, other course runs is like the main use case there. So nginx is currently working on some designs for that they're doing some prototyping and usability tests for those that will share the the feedback from those in the UX UI Working Group. Um, hopefully in the next, the next month or so. Questions about whether this is going to make it into Redwood or not, I think it's going to depend on what the effort estimation estimate. estimations come out to be from the UI work, but that'll be kind of TBD until we get the UI into more complete state.
We'd be any of your time turn it in.
Yes, a little bit tight to order and that will be probably worth having a larger conversation, but in the aspects of evaluation that is over all changes that we wanted to do the evaluation process. The even though we have the programming process, were still blocked at that stage. Like there hasn't been much progress in the way of reviews or approvals or outright like denials like we don't want featuring and we are reaching the point where the originally the Spanish contract was until December but we made an extension for to work to be able to eat delivered up until end of April. I don't know mid May something like this. And we are starting to be very worried about can we still put some of these in master by that time or deliver some of the work by the time and we've talked with natural odd having like a separate conversation or whatever that is actually possible or not maybe with Juliana and or it probably we can also discuss it here in conversation, but
then I think that some things should change in their product review pipeline because we have like five or four things that are blocked since October and the one of
things has been yesterday. So my something has said about that. But it is not clear if it's yes or no but other five things they have never been answered. So we don't know if we can do them or not or what's happened so probably the product review pipelines should be changed or, or I don't know what to do, but we're gonna reach the deadline of the project and we need to do these things or not all know what happens.
Yeah, there's I think part of the blocking is we were trying to come up with a rubric in place to see if we could figure out a better way to coordinate and triage the reviews. But that's been sort of stalled. So I'm going to I'm going to make it a goal to get those remaining five reviewed by the end of January if that works for you. So within the next two weeks, and aim to have like answers at least for the ones that are stuck in the backlog by then. Because I don't want like the process for the operations to get in the way of the actual work. So we'll be getting those reviewed and rather rubric issue later on.
So thank you very much. So you, you speak we celebrate because they send me the list of the ones that are I know for example, it took me 18 There were some objections, but the it wasn't said not bad. It's also stuck. So you speak with Felipe and see we can go on these five or six things. Thank you.
That's good. Does that work by the end of the month? By the
end of the month? That's fine. Great, because we still need to like reach an agreement and then start working on the technical specs. Yeah.
Sounds good.
Flexible grading is still on the backburner, no progress there. Again, credentials. We'll see if Ed pops on. I think the Salesforce integration was also kind of on the backburner. Was there any any current movement on that Elizabeth or Fox?
Time we loaded 70,000 students the platform in the last three months. Oh, so yeah, we've been busy. That's it. That's great. We're super excited. Not all of them have activated and actually joined but they're loaded so it's good stuff
um, same thing blueprint. Children's course children courses are on the backburner. The next step will be to do some product discovery but I don't think that's going to happen until probably sumac
completion API. Okay.
Yeah, that one has been in the backburner for a while kind of waiting of what happens with the graded discussion because they shared some technical technical aspects here and also was waiting on the the factories that were presented. Changing the way that grading works, and we never proposed this one because I don't know it was the sixth or the next one in line and we didn't come around to it. So it's in the back burner but probably will be unlocked. Soon is this info on PTR things and I'll take the next one as well. Please no grouping that one kind of kind of tie this back to where our back so three, three major changes are minor minor. Three significant changes that we want to include there. And if Arabic is a still sensible point, the other two are ready for like a final engineering review. That's kind of where they've been blocked for the for the last month, month and a half. And I wanted to ask if, can we I don't know take some drawing time or get a get some effort from maximum involved in having a technical review that says this is what continuing are not going to US planning to just stack de vos B and try to push him like annoy him into doing the review but probably asking for, like an official instance of that is
Yeah, would you mind dropping the links to the PRS here, and then I can see who would be the best person to triage that.
Sure. Absolutely. I'll give you that in a few minutes. Okay. I'll confirm one that being that I'm looking at the right ones.
Great. Okay, I think that's everything. We'll get the credentials, maybe an aura updated asynchronously, any other updates from the group anything else to share?
And one thing I wanted to flag is we're reviving the discussion around the sidebar, navigation, the learner, learners sidebar navigation in the LMS. There's a link in the discourse forums if that's something you're interested in. We've got a proposal kind of open for community feedback. There's pretty broad consensus that this is something that folks want to see brought back onto the platform. And so we're trying to align on a couple of design decisions in terms of how that would be implemented. So if that's something of interest, have a look at the Open edX forums and I'll link that in the slack thread as well.
I am very interesting that because one of our teams, the one that works with the person directly, the they they didn't an additional MFE that just does that just does does only cyber. So I will ask them to look at that. But also if you happen to meet with Scott for any other reasons. And I'll try to tell him that this is happening as well. So they don't they don't have that as a poll but can continue.
Yeah, Scott's been involved in this point. And we're actually looking at some of the Pearson designs as a point of reference. So
beautiful. That's great.
Do you know what one thing I want to mention, open cropped at one point was going to be doing a new theme design. Welbeck and we earlier now we're playing with the sidebar. So we've actually got some wireframes some which I can share
because we've got like six different iterations of this design now from six different organizations open craft is like number six, tiny
I'm happy to share them. I mean, yeah, they probably need some work, but I know we had we put a lot of thought into into it, especially from the mobile perspective and how that would change.
I'd love your I'd love your eyes on this as well then let me find I'll just link it here in the group as well.
That'd be great. I'll share this with Ellie and then I'll put together a document that you can see what we were thinking.
Yeah, it might be what might be most helpful is to see like where your, your thinking kind of aligns with. So we've got other designs from Pearson. We've got designs from abstract technology. We've got designs from raccoon gang, we've got designs from edX. So there's quite a few people who have been thinking about about the design for this. I think there's, there's a couple of key things that we need to land on. One is a decision about whether we keep the horizontal navigation within the unit as well because there's kind of conflicting navigation options that you can choose from if you've got horizontal as well as vertical. So that's one another big one is what happens do we have do we use up both the right hand and the left hand sidebars within the course. I know edX is thinking about focus, a focus mode approach which might help to alleviate some of the concerns about distractions or distracting away from course content. But there's questions about whether the right hand side of the left hand side if we use both the right hand side and the left hand side for stuff or not. So we'd be curious for your your take on that. If it's something you've been thinking about, feel free in the in the wiki, that'd be great to start the car. I
can just I was gonna ask you can I just dump some stuff in the wiki? Okay, great. I'll do that next week. Okay.
Nobody has anything else. We will see you everyone in the month.
