there's some pas autopilot. I don't know if it was in this meeting or not, but he may not be able to join the Navy his autopilot will be Hey guys
valid everybody
don't have too many open topics right now on my list is pretty short so I don't know if there's anything in particular that's top of mind for for the team but I can share the things that are that are things that want to find. So, unit navigation and some pull requests that are open for that is one thing that I wanted to sort of flag. Make sure we're aligned on sort of where we're going there. So that's the first thing. And I think there's some like, open like Project sizing like roadmap, questions that are sort of mentioned briefly as well. And that those might be for validity or it may be other input on that, but But um, yeah, anything else from anyone that we want to make sure we cover today? Today? Maybe a quick one?
Yeah, if we have a moment after
this? Yeah.
Sorry, I just gotta say I wanted to see all the open pull requests and see if we could take a look at them together.
Yeah, great idea. I think yeah.
Okay, let's start with that and the more things that come up we can add to that I think like the unit navigation or flight pretty quick. I think one thing to flag is like, this is something that I saw come across in one of the like quick bugs, quick bug tickets that are that's in the pull request queue. My understanding from reading this PR is that it is behind the flag. And so if so, I think there's no like immediate concern for me, but this is an example of one where like, we had talked many weeks ago about sort of like navigationally, the differences between where edX was going and where the Open edX app was going in terms of that would be to an extent moving towards like full unit page composition and the navigation that sort of makes that work versus the component by component next browse directions that the next I piles currently, so I just want to like make sure it's clear that like the, it looks like this work is already sort of in flight to sort of fully ship to sequence navigation towards edX as experience and as long as that's behind a flag. Like that's, that's fine for now, but we wanted to make sure that that was still clear to like directionally, we're still moving towards the full page in our navigation. So as long as that's clear, that's kind of like we're good. That's all I wanted to double check. So I think there is a flag but
yeah, there is a flag we try not to go in different directions. As much as possible, as much as possible when we're trying to be aligned, because unfortunately, these flags complicate things. It means you have to support two different navigation, you know, like formats when it's wrong for bugs. It's wrong for things to break. Its overhead. That's its cognitive complexity, just managing that. Maybe we'll find the blog and our navigation, but your navigation is fine. So that's like, Oh, crap, we have to do that to the other way around. Ideally, in the ideal world, we shouldn't have this and we would just all get away I hope over time, we'll get more aligned with product. There's also a lot of changes happening on our side. And so maybe, maybe things will shift, I don't know. But if we can get more aligned, they will just make a better product overall, with less complexity and less code which is the desire. So but for now they are behind the feature flag, Marcos or we shouldn't be impacting your direction.
Yeah, and I think once we also are able to kick off the project to hopefully work towards not just native video, but more things being available offline that they may also simplify things for us the way things load with us right now fully in their own separate activity or frame or whatever it is, in the past at least was a limit or just the direction we could go anyway. So So yeah, it may be easier in the future to sort of like resolve that but Okay, so that's it on that on. And I think like otherwise on like the project sizing and roadmap, I think like one thing to flag, high level blood minerals, I think the XM is eager to kick off the next so W for what things you've sized in scope. And you know, for context, I think like, you know, obviously like a not signed so w is like pretty loose, like non committed necessarily, but like for, you know, for this broader group's context on like things that are coming down the pipe the pipeline. There are some there's a project that's not really of interest at access learning site selection, so it's like Canvas the ability to switch learning sites, but that is one of the Open edX projects in queue. We've been doing a lot more like parody focused up of late but that is one first like, jump outside that space in a while. Then there's like date, and calendar personalization. There's a lot of that that's already been contributed by touch app next night. But some aspects of that project that were outside the scope of what the team is focused on right now includes like an app level dates page so it looks across all your enrolled courses. And gives you the date summary. So that plus the server side requirements necessary to be able to have an automatically synced server side cap subscribable calendar for each student. So that would let us move to sort of a more like cross course. Date thinking stuff eventually. So those two things are still in the scope of that one. And then offline mode project is sort of another larger one to flag that is also being scoped. And I know that that members of touch after next night have some context on that as well. So that's something that you know, well, we'll be able to share more about as well in terms of like, it's not gonna kick off for a bit, but at least that's one of the things that we've initially scoped for problems and text being able to be offline and so you can toggle the full course to be offline and then finally, I think like one of the things that we're looking into as well, is how, like, notifications on the server side. So we talked about like, notifications branches, what the edX team is going to look at. The Firebase equivalent is something that we're hoping to also push forward. But then separately on the server side, there's taking a look at how we can route a notification from the platform through to respect notification level, user settings. And so that right now, tentatively, is where that one is, there's a lot more to figure out on the technical direction on that one, maybe but anyway, so that's the queue of things that we're looking at. And then beyond that, there is like, the the for so navigation projects that are sort of like cleaned up at various stages of the of the views. That's also one of the things that we're sizing and reviewing, but both merit team haven't had like full designs to fully size for those. So right now, it's just like loose sizing. And that hasn't started quite yet. But all the other ones we have initial sizes. So anyway, that's whether all those get put into the queue right away or not. I don't know but those are the ones that we're kind of looking at, beyond the set of activities that we're still making progress on. So.
Are there going to be a suitable use for each one of these?
I I suspect that it'll be lumped into one larger one. And then we'll still have different project pages and everything else to track collateral and epics for all these things. But just in terms of trying to sort of like calendar schedule and understand recommending teams, availability and whatnot. I suspect there'll be lumped into one that's ultimately up to XM and working gang to figure out but that's where we've been headed.
So it sounds like Londoners and I have a lot of work obviously going to get help.
Yeah, so right now, again, that's like the the part that is unclear right now. And that's one of the other open questions from axiom is, it's like, what is calendar time looks like for this for the right if you add up all the hours for these, and some of these like dates and counter personalization are now like the estimates that Volodymyr team had originally have smaller now because the other things have been contributed by accident and other so so actually, we'll see what the final calendar time Gantt chart like. Yeah, that's the that's the current plan. And so, it sounds good.
I mean, the only thing I'd like to see is when you have it sort of buttoned down or you haven't like written up, let's review it, because I think there's some overlap between our gains. So I just want to be careful so that we use our time especially especially in the ACC, some sites are we're not duplicating some of the initiatives we're doing. Because then we're just wasting time. So it would be great if this was complimentary, like offline, for example, even though our teams are doing it. What's missing and offline is like state management. And like content that requires state anything with quizzes, anything with questions, anything with forms, things like that. Offline right now, I would say is pretty stupid. And like what I mean by that is it's only like video support and like asynchronous support. There's no sort of like upstream state. And like, that's a complex problem actually. And like, I love for that to be tucked
in right think like, I will say like on the product side, originally, my feedback was like, stay away from state like, let offline problems be dumb. Like don't want to deal with like, educators to change the courses mid flight and there's state that hasn't been thanked and all that stuff. Ultimately, like I think, like we're recommending team have done initial technical exploration like I think, correct me if I'm wrong, like there is a path forward to being able to do the state stuff. And obviously we can get that reviewed from this broader group. I know there's lots of people that have context on that and have worked on in the past. So we might even be able to go further than where I thought we might draw the line. Now, what that means for like, you know, there's gonna be some small fraction, for example of edX courses that are like being authored as they're live and like, you know, what does it mean for someone who's making changes to courses? Like do we give them warnings about you know, if there's courses being used in offline like, you know, there's there are ways to mitigate some of the state challenges for the edge cases of authoring and other course changes. But it's possible we might get something more robust for learners on mobile, which is of course a win but we do need to account for some of those, like, you know, authoring
it, so like, in this in this case, there'll be something with version control, like GitHub, like you know, which which GitHub does this problem all the time, right, everybody's committing doing things. So they have a robust version control system. I don't know if we're gonna ever build something like that, because that's, that's an overkill, but it would need some sort of version control management
was interesting. Like there is like, we wound up in 2019, having a build sort of a version control layer for grading, because we were running into some of these issues already, not fully state management. But issues were like oh, like I got a five out of six but then the you know, on this problem, but that now instructor added three more problems. So I have a five out of nine like what the hell like nope, like you keep your five out of six unless the instructor regrade it and they can recreate it forcibly, which will give you a five out of nine or recreate it, but let all students that had a previously higher grade keep the previous higher grade. So like that was robust grades on the open platform. Something similar may be necessary to consider eventually for, you know, if you're offline and you had no similar idea, right, but But anyway, getting ahead of myself, but But yeah, absolutely, totally agreed on, like the openness and visibility into what the team is working on. I suspect we will run into more of these things where like, Oh, you were gonna do this, but like, we didn't pick that up and are ready to contribute that or whatever. So like, well, we'll figure that out. But we're trying to just like just like a town or personalization was already partially built, same idea. But yeah, so that covers the items that I had. We can jump into PR reviews unless anyone else has anything else.
Any questions before we dive into PR?
Yeah, go on over worldwide about figma and one source of truth for design if a soundboard is going there or like in general Hernan and Kalahari working now because I have chatted on with your teammates today. And I realized that you still working because our design in iOS and Android teams working quite, you know, implementing features in several ways. It's not a big problem. It's a different platform. So some features can be different, okay? But we need to at least post put some screenshots to figma just to know that we have to add it to the design later. I don't know. Cuz we will implement a lot of features and then we will lose them on the design and I don't know how to handle it later.
Yeah, it's actually problematic, because like, you don't have good design resources assigned. And there's just like resource constraints. So like what we've been doing, at least our team like can speak recall, it seemed like what we've been doing is using the production app, and the Paragon sort of like design you know, Paragon was a whole conversation because like, there's no mobile design Paragon, really, it's a web based design system, which was not great for what we're doing. And like, I don't think it was great to use that on the production apps. But we are still following it because we don't have anything to replace it with at the moment. And like, what we're doing is using the production as sort of like there's designs from production that we're using currently internal to figma. Like Eugene provides the last one we follow that. But like, in some cases, we just improvise and like, figure stuff out is like, you know, literally try to stick to native implementation of things, which means you don't have to worry about the design so much, because natively it's already linked. So we just implement some native controller, for example, or native view, that doesn't like a menu, for example, and you just have to basically figure out how do you order things. So we tried to do that, but you're right. I mean, it's a problem. I hope that after March, you know, lots of things are in flight right now. It's very unclear. What's going to happen after March to be frank. But like if you do go forward and continue we should assign a dedicated design resource and collaborate much more closer to Sam because I know Sam was also doing stuff in figma. And we're not using that at the moment, which is unfortunate. You know, I wish we would sort of consolidate from both sides. I see Michael here. Maybe you have thoughts on that you got on screen.
Yeah, just just hop back on. Yeah, I think there definitely isn't like maybe we do set that for like March as we get through this is we kind of take that full inventory and create like a new one source of truth file that we can use. Like there's like this point where we draw, you know, it's like, Okay, we're here, and maybe we set that for March and come back and be like, Okay, here's where we are, but whatever we have to do, you know, lay it out in like a fig jam and then we can really use big jam or figma as a as like a springboard into what what we need to do. I think that makes a ton of sense. A ton of sense. Yeah, absolutely. Yep.
One One thing I'll mention here is like in the work that schema has cued up in the last time we engage with action and reviewed like, Hey, this is the stuff that is coming down the pipe for us. We added two really tiny projects that are like when I say tiny, they're like six to 10 hour things for the two there's two efforts that have been effectively merged or are about to be fully merged, pretty login mobile app exploration and social login off. And they're, you know, there's a bunch of screens and workflows tied in that and we knew that X was limited on time from like, like contributing to the figma file. So what we told him is like, look, we may have to do this for other things, but these are tiny little mini projects that we'll put at the back of our queue. In case you know, at XD You wind up having time on the design side, but we do want to make sure that that figma file is kind of like caught up and reflect everything. So right now we have these two little mini projects, and you know the end of our queue. And so if by the time we are done with all the other stuff and next to you has been with the contributor and stuff on the on the figma site great because obviously you guys will have been the ones that are most familiar with it both from the past and promote still. But you know, if not, we'll keep using the app, figure out all the screens, ask the guy that does all the red screens and make sure it's reflected in figma in like a quick little project but you generally want to try and keep up to date. We're a little behind right now, but that's you know, the time that that will happen when we we went from a really small team to like, boom, big team on the development side. So it's gonna happen, no worries, but like, eventually hopefully we'll catch up. But those are the two that were we have like a small six to 10 hour thing for the others. We have not planned for exactly
one year.
Yeah, just to add to my previous words, I mean, we designed this project, like design first project and I really want to have everything that goes into the upstream in figma. I understand you need to go set up design because you have really strict deadline, but maybe for now we can just create some page on FEMA like to do and put off all of screenshots of all the current screens to this page and then we'll design them later. Someone will design them later. I don't know. Maybe design from record game maybe design from schema made design for a designer for to you whatever. I mean, just from the design point of view from the designer point of view, we have to talk about all the screens case, designers not following all of this PRs, they can meet some features or something we all have to know about the screens.
Maybe it real quick noise maybe take that as a next product conversation. Yeah, for design. With Eugene, maybe we can family we can consolidate what lowdham are saying is true.
Yeah, it's just the nature of the MVP. Now he's in right now we are basically development and we have very limited design bandwidth at the moment using is also occupied with the microburst transformation on to you. And so mostly it's schema that's contributing towards those designs. But that's the nature of work. But yeah, once we do live, ideal status definitely should have designed for each, sorry, each and every screen.
Was that I thought, I thought you just had something I'll ask her because I thought she had a page that when we kick this off that Sam and her were using so let me look into that. But I also put it in, we're gonna we're gonna do just a design retro. So I added that in in that as like things to start. So I made note of that, that we can, you know, we'll talk about that next week in our in our design meetings as well. So thank you
Carly. I see you and
yeah, so I do agree with the word Amir like, we should be keeping track of the screens that are being added and for those that that don't have resigned. Another part of this is that there are certain students whose design has been added by Sam and some of our team members are actively collaborating with with Sam on figma. So we have room for that is like the dates page, the pls and calendar. So that's actively being worked on and we're going back and forth with Sam on that. So I think wherever there are designs we can go back and forth with Sam and for whichever screens we don't have like kind of designs or we need to like wing it. Those are the kinds of screens where we can have like screenshots and maybe have a different page within figma or where it says that hey, these are the things that that weren't actually which activities are designed. These are just the things that have been implemented.
Yeah, and honestly, like one thing that you really might want to see from Mike and Moiz for for your conversations in the next couple of weeks. Maybe Maybe this is this last point is helpful is like the right now there's like placeholders in the figma file. I wouldn't say like It's like accurately reflecting all the screens and all levels and but there are four different pages. It's like account level dashboard, the recording Level Sequence level. There's some gray boxes that I've added that are like to be added social login off like we can want to make sure those are added and like start common threads there. Or, even better would be potentially like as long as we are noted in the chat. Like even screenshots of like we're building against what the NX app looks like. Even that being in there because then we can flag things like hey, like this is the you know, being contributed but it'll be behind a feature flag. Like because right now like nothing that's behind the feature flag is actually reflected in that file either, which I'm also realizing right like and if you eventually want like the figma file to be the design reflection and echo of what the app is like. Presumably you want some visibility into some of the feature flags, right not just like, you know, the bass thing or whatever we're assuming as default. So that does actually suggest that there's maybe lower lighter weight faster figma contributions that don't involve like fully using native figma components. But hey, here's the screenshot, not like where we want to be, but it's visible, because basic visibility would be a huge step forward.
Couple, since we're out of sight, like there's a couple of things so feature flags are it's not just a design thing. It's also we need a technical documentation. And we talked about this with Colin said, like features from a developer standpoint, I need to understand what are the feature flags do what's available to other developers that are forking the repo? Then there's a design components of that, right? Like what does it look like? And then there's a third one to that theming. So even though like Sam was designing it, so it's neutral, the computer abuse and then implementing a neutral app, right? We have addicts logo and branding and so on, and that's also part of that. And like it's a question, how does that get into figma? So like, what I propose, is like, Moiz, when we figure this out, like in terms of like, you know, just collaborating and like, maybe something already exists, as Michael was talking about, maybe something we have, we can get our team if they have some bandwidth to just upload the screenshots for every single implementation that was done. And next, we can have a theming deal. We can have like a clearer sense of like, what's the what's not the end? What's behind feature flags, right? And like, kind of like an audit, and like, I'm happy to do that. But I think first we should find like, what's the shared space and we're going to do for that before we invest energy because that's going to take you know, a few weeks ago, to put it all up there. So I'm so willing to do it. So let's just do it next step about like figuring out what the shared places are like we'll get that out of the way. Anything else before we move on to PRs, or anything
I mentioned on that last point is there wasn't a web app or Open edX platform proposal that was merged May of last year something that was like the platform level, like best practice on developer documentation, which I think just means like we use swagger. So I don't know whether that is a part of and you know, are is the right direction for mobile? I don't know. But yeah, it does seem like a really useful technical meeting topic or meeting topic for for us to advance and it's it just say hanging out kind of empty on the roadmap. But yeah, I fully agree. That that's out of anything. And nothing else.
I'm going to show my screen
I think from me, and we can jump to the power stuff, just one sentence. We found. We reviewed the whole application design and we found was my design team, like 15 sentences that we'd like to change can't say sounds negative or not really clear. And we will prepare some big mouth documentaries comprised and you know, like the old the new one. Maybe we will launch voting changes to the design and then create the Ouroboros application can say we check them and you know, now we're allies. It looks really weird. So yeah, no
negative, no negative sentiment. Okay, I'm gonna start with Android. Okay, so first lemon, I curious which one was this was a social login one and the social signup? Is that the right one?
Yeah, this one this one? Yeah, that's yeah, so
let's see. So this was done. It's this is like probably outdated screenshot. So what needs to be done for this one, or is it I don't know if it's assigned who's or there's no reviewers assigned?
Yeah, looking at the makeup this PR crew. If you want to add something else I need first of all, I need to fix tests. Their assigned reviewers. I think it's enough to description for me. I've reviewed the half of it. So I mean, maybe I will provide you feedback through career. We will discuss it and we'll see. But I think mostly we need review of (Axinite) Kinzer
from our side. The review will start tomorrow. It's
amazing because I really like to measure this power to you know, to create religious to master it's need to be done.
Real command from excellent team that someone started reviewing process. I think maybe I
need to
tell you below some
Yeah, this is started
to raise I think it was a mayor from six and a team and he leaves the comment below that he's
that that Homer is currently reviewing your teeming PR S Sorry,
it was teeming. But can we put more more eyes on this bar? Not on teaming. Teaming is not very big. And I saw this activity on another Android PRs but I saw no activity on this. Can you? The
reason is that the one the one developer from from our team who has the most knowledge about this and has the most experience this has been assigned to him and he told us today that he'll be stuck in start reviewing disappear tomorrow.
It's a lot here. So clearly, we wrote a lot of
yes, there is a deep refactoring because our QA team found some cases and I can't fix coordinate fix them with the relevant code base so I have to write a lot of stuff because
there's a social blogging I just wanted was taking so long
Yeah, I got it. I just asked was it real? Yeah, no, it's great.
Okay, so we got that one. Go back to that. course dates better. This one is approved already. That's not merged yet. Right. This was
Yeah. One of the areas of conflict resolution after that, it'll be good to emerged.
Okay, blogging. We're gonna have a lot of these.
Yeah, we'll take a look. Okay. Yeah.
This is the famous one right girl. This was not one that was being looked at. Okay, they have reviewers. And
there is already Oh, it has confirmed conflict. Okay. I will resolve it
as conflicts to figure out what's going on and then we have what's this? This is from where?
Contribution from my belly.
I think it's from open.
Open craft. Yep. Sorry. Open crop.
The next two. Okay.
Oh three they might they might conflict with this. So I don't know.
I believe it's a bit in other flows. It's implemented. But
yeah. It's like a feature as I understand it, it's a feature flag. So instead of having the native login registration, you would trigger the WebView for whatever that instance or platform is their login and so I think all three of those kind of like are connected I don't know what the last one actually
for providing alternative resource directory. This was
perfect structure before like to make it to generalize it in a way that it is easier to configure. Set up the configuration of the new app. I don't think this this is relevant now. But I might be wrong as well. I haven't given in an in depth review of this, but
he mentioned kinda like that. Yes.
Yeah. Yes. We can
provide the link to close the armored car and close this one. But we have to figure out what to do with this open powers. We can just ignore them.
Yeah, I don't know why the guard is open that X ray call you can have your drag this one
okay, I got this I got
so I can just speak for our PRC Oh, I can't speak for the community. With you gotta manage that. Okay. So and then we have so before I close off, so we need to get some eyes on social signup and we need to get some eyes on the theming and the course these three basically.
Okay, iOS now moving here. main course menu item were bright. This is sorry, I'm looking at the wrong thing. Okay. human progress negation style. This Oh, that's what these things are in the in the progress bar. who's reviewing this? This is signed and logged in here. Did you have any questions on this one? Anything else needed for this?
Anyone? No, no, I just think it's a pretty big PR we just needed some time for that. This one oh no, no, no, no, sorry. Sorry. This not this one. I've meant another videos. Yeah. This one from today right. This is recent.
A few hours ago?
Yeah, two hours.
That's what's new page writing. With this is probably it's just hide from the onboarding that it shows you could decide to election I think
PR Charcot promised to see this. Some, I don't think here will have some problems. Yeah. This page had to seem some stuff. So when we implement our script, it will right file with what's new pages.
Yeah, it just hides one page which was site selection. Yeah. Yeah. Because that's one example. Marco already can show that feature. Because it doesn't apply to us.
Just to clarify the What's New feature. So, learning site selection is referenced but I'm not sure I understand. So the What's New feature will be used or
or not. So like, it'd be easier if I had a screenshot you would understand right away. When you open this when they open the app for the first time. There's onboarding screens and you swipe left and right. Yeah.
So link to to the top Yeah, for you will open issue. Yeah.
Yeah, this page, okay, so there's what's new, and you see stuff and this, this particular one, you see, I see. Okay, so it's just gonna hide this page, basically. Yeah, I won't say that. It's gonna show all the other ones all the other ones will be here. This makes sense
to merge but it is something to think about in the future for what happens when a given release. We need to have images and text for like, you know, a feature that may not be turned on for everyone. So that is a more generalized problem. To think about in the future. Otherwise, we'll need to like, wrap like conditionals with all these things, it's fine for now, we should merge the Senate and move forward. But it is an interesting problem in the future where it's like, you know, how can X in their build time determine which what's yours that are in the full list to not show because they might we might need something more general? I don't know.
They should have a feature flood ideally. So like anything we want to show here with the feature flag concern like it applies to open that it doesn't apply to that I don't know if it's done this way. Now. I'm done right? It's not done that way.
know right now, it's just a JSON file with Title images, and no description. And right now we just replace this file from all config.
So we're gonna have to do feature flag here eventually, because that's not the the best.
It's not luck. It's implemented by sending script. So it will be overwrite only after we run our script.
I understand what I'm saying is it's not the way you want to go. It's not it's not the implementation we want like this worthless and this should be a feature flag. So look, I description
to some conflictual space, like two sides. I e, one, three and five are example. Right?
And yeah, I find like, I do think like, one of the challenges with the feature flag is that like, because this isn't a static feature, it's just like a, you know, for as updates are happening. Like there'll be a bunch of these. Eventually they fall off the map in the sense that it's like, oh, these much new screens are really old so we can get rid of them. And so if we have feature flags here, I think we'd have to update feature flags more often. But however we want to do it but it hopefully will be easy for for an app to say yes, I want the messages. No, I don't want these if that the answer for that. Technically, is config. Great if it's something else great. But yeah, these these things change all the time.
And just something like I don't know who implemented this thing, is this plugin or is this here? Where does this come from?
I think this was probably like a placeholder screenshots template in figma for like demonstrating the What's New Features?
Yeah, currently, it's not like the real picture. Okay, I believe we discuss it but anyway, it's not a real screenshots that we provide in like, what's new, it's not the real features. It was like the example from figma that we implemented was this feature. You can replace all of the screens by your config when you build and care build. I mean, I'm not sure to hide like page one or four cuz it can be very different from release to release.
Yeah, I know. But like some feedback here. Margins are not aligned. Yeah. I just adjusted revisit this and get the accent.
Because it's in white, Korean short on the white background. It's not the real, you know, elements is just whatever.
Yeah, we can just give feedback you could do what you want.
Should be replaced for the real release of salons. Okay.
By the way, I've gotten in front like a slightly tangential approach in this regard. I think I mentioned it in one of the past meetings as well was, since this is something about your item is something related to learning sites. And we should have feature flag will in any way. We'll be having feature flag for learning sites right? For the structure. So there should be a base feature flag for learning sites. And since that will always be disabled for addicts. So during what's new if if ever there is a page that has been added for learning sites, it should be controlled through that feature pack as well. So let's say there are four items in the What's New for a specific release. And the third page is around learning sites. So if there are, if the learning sites feature flag is off, that third page should always be in visible or gone for that specific configuration. And I don't think we should need the script to actually configure that or say that for these releases hide this this this page.
Yeah, that makes more sense. It's one that's actually a good idea. Yeah, no. feature flag. That's
yeah. And we'll reduce times that we miss it, or build the don't and catch that. It's yeah, so that makes sense to double check any new feature flags and if it's applicable, yeah, that all makes sense. Yeah,
it's like a global feature flag. You know, this is supported and everything else. hooks into that feature flag. That's right. And it's true the
configuration can still let you override it, but this way we like prevent someone from missing it. More. Yeah, makes sense.
Okay, Davidson's screen style changes,
just to like, summarize on the beer I Do we all agree that this beer doesn't need to be reviewed for now. And we'll be closing it out in favor of like the feature flag and learning sites feature flag being the one opposed to proceed
Yeah, I think that's right. Because if he doesn't have time, but after it's executed, but it just won't go back until then tells Yeah.
Yeah, whenever you guys decide, like right now the learning side feature isn't even real. So there's not even a feature flag that you could turn this off on. So whatever like I said that screenshot could have been unicorns and ponies. It's like meant as a placeholder. So whatever you guys decide to do merge forward fix later on ticket for what we talked about whatever, not merged this year. You guys can Yeah.
I would propose keep this beer as it is. Don't merge it and like label it like, we don't need to merge or review this beer for now.
But we do because Wait, merge it or not merge that confused?
Not not not merged that sounds like we don't need this model for now.
But the production model show
What's New page hide exists one. Okay.
If we if we don't merge it look what happens. This page will be visible to all edX users. That's what we're seeing right now.
I'll just delete this page. Just delete the first page from this from just from the JSON file and screenshots if it's all here problem for now. Let's do it. It's not the real page. There's not real data.
Yeah, got it.
Yeah, and
yeah, I had conversation news site. And he told me for this will be my new JSON file. And this JSON will be it for every level is different file. So right now we place this file in all config repo. And we will implement this file when we run this Python script four seven. So if we prepare json file for every ladies will can place this in our config repo and we will have the latest json file, don't need to change this in open project and commit to open open edX repo.
Because this is just just make the site so like we're gonna we're not gonna merge this PR in time. That's what I'm hearing. Is that a concern for you? Are we just delete this page? Basically, that's going to be the different PR.
Or I got what I mean. It's doesn't need to change this PR for now just to providing this customer json file for each of your releases, but not hiding some page by page plugs.
Yeah, we just have JSON file this out this page. Okay, we implement this copy from our config repo to project and then release. So we manage it Okay, yeah, we don't touch people at all it will be placed to conflict repo. Private Okay. Adex config repo. So this script will apply this if this file is present. It's all
sir, again, it's issue please, back to the PR
issue. You clicked on issues. keep forgetting some of my apologies. This was the What's New page this one? Yes.
This one? Yeah, sorry.
Okay. Okay, so let's do that. And then we'll leave that for now. That's just the configuration thing. Okay. And then we have dates. This is my oldest son by accident inside this
chapter, especially, say this currently programming code on this and they're actually like reviewing in the form of a program.
Okay, so it's not ready yet probably to my right. So it's still a work in progress.
Yes, still need to approve it and then he'll like forwarded to touch up and Valdimir.
Okay, cool. Cool. Cool. So we got that and we have course Boris. I think this is the one that's scary.
Yeah. Yeah. There's a big stick of files. Yeah.
Yeah, there's a big deal. Massive. There's questions here. Eugene is not here. This week is going back and next week, Monday. So let's leave this open for now. Right? We're just doing more diligence on this.
By the way, again, calling out that this this is a p one and I don't know if we should like cooperrider Is it over P zero. stuff?
Well, there's no more P zeros coming. So everyone's doing P there's no P zeros left. Okay, and like the work has been done. So why not? Unless you see some other P zero. That's not being done. You know, feel free to call it out, but I don't see one.
Yeah, again, like there are certain things like a lender, other beers that are coming in. I know that visuals are being bogged down and there's still some like the abstraction of the movement and navigation things. So once though, I am just like trying to emphasize that if some p zero PR comes up this can be it. And should be delayed.
Yeah, well, so we say P zero theory. I agree. But you know, the work has been done here. So I don't think we should ignore it either. So, you know, and I looked at this it's pretty good in terms of like, it goes both downloads and you can switch live you basically change the size of the file that you want to download. I don't know what they call it the how much space but that's a big there's a big deal. So the only thing that's usually my answer the questions that are posed here, and we all agree that P zero takes priority, but since the work is done, many things won't get to them unless there's like concerns about flat out fails. Android is also
just second out if we have bandwidth to create more value in the app for MVP. We're not
Yeah. We're looking for wins, you know. So if we're ahead, that's a good thing. One last question I have is the push notification. So like worst, Anton started the abstraction and like that's the whole thing about brace. We just need to pair anything. Anthony can't do this himself anyway. So let's just take let's take this as a joint effort between our teams, you know, touch up and do it together. Doesn't matter who does what. It's just like, we need to attach the end to end because otherwise they have no idea of the attraction is implemented correctly. So that's cool. I don't know if he'll pair you call it you can figure out who he should care with.
That's part of the reason why I tagged one of my engineers who was most experienced in braids and configuration and testing is actually build one sometimes there will help out and on and in configure and all the stuff that was required. And I'll look into what kind of access is needed and talk with Pete about it as well.
Thank you anything else I can we went through everything.
That's it. I added some comments to some of the link tickets inside of that large PR that we just looked at, for, for the team but otherwise, it's just more FYI. So there's nothing else for me
think it's good progress. The only thing I start with is the calendar implementation if we can divide that into pieces, so that we're not because there seems to be a lot of work there so they don't get delayed too much. We're thinking we're not talking about this. But we're also finding a lot of bugs and issues in the apps a lot. And there's like a whole list of them and issues and GitHub. So I think March will just be a month where we just tackle these issues.
One one thing to flag is there is like the q1 Bug tickets that the teams made. So there are a bunch of things that are queuing up in there. So yeah, maybe that it's a bunch of that to review. Yeah. Make sense?
Yeah, March, we're just putting out fires and making things stable. But we have you know, that's why I'm asking for the calendar to be divided into pieces so that we're not over cooking. So another lesson let's break it into post NDP and go out with minimal that we need.
I think I would merge on that as well. And it's currently being worked on for Android in our team. And it seems like it will be finished very soon, like maybe in the next a week or two. And the implementation that the team is doing is doesn't include deeplinks because because it hasn't been implemented. So I think also we do we could do is have like deep links within the calendar invites that will be there. But if it's simple enough after the difference have been integrated into the app, we can add that if that adds more value. And as far as I was concerned, I think that will be a good call as well. But I'll let Moiz add to it as well.
So I was thinking since the team was primarily working on the integration part of it right? It'll be able to create events on the local calendar, and it will sync and it'll change and update. Only remaining part of the implementation of the plug so if you don't have is working on the abstraction part of it. Once abstraction is done, we can use wherever deep we want to and I think we can come to an agreement on it pretty soon so if we do Yeah, yeah. Okay. Yeah, so we sort of so we'll have a decision on it.
Yeah, I will add possibility to add any amount of service branch any of this?
And that's the ideal approach. Perfect. So why don't we take these like two things in parallel? Who wants the calendar integration has done I'm hoping people will be there. So just implementing deep links with those calendar events will not be much effort. So like I'm confident we can go to them before the code freeze.
Okay. Anything else?
Just guys, please don't forget to create some ADR or something when we adding some third party services just send to remember in three years why we chose them. Exactly as this one.
Yeah. Is that can you point us where like an example or something that the team can follow?
Yeah, like I guess. Yeah, those are some guy believe Karela know how to do it. He created one or
two girl has created one around flows, flows usage and then easy to go there is a sport that has all the assets
folder for ducks, especially for a DR state in each triple rep.
Okay, cool. I'm gonna ask you for some help. Maybe when he was doing this, we can make those videos and explain how this stuff works. And then we'll do the same thing, Anton for iOS. And we also have the same thing for feature flags. And I know we have to start documenting them right and sort of like people set up the app so they can just get started with the project the same thing for theming. They need to just like instructions how to theme so last little Okay, cool, everyone. Thank you so much. Have a good day. And we'll chat as things come up. Feel free to ping us on Slack. We don't have to wait until you know next call. So but I feel like we talked enough anyway, so it's all good.
