Sit. So eventually it might be only robots. And if the meeting is important enough, you know, that's how AI takes over.
Actually, you know, what I would love is because only AI is in meetings this way we wouldn't be able to interact async and they would just represent us that would be actually not that.
I'm not judging, maybe it'll be better, but you know,
it's probably only good yeah.
Hey, everyone.
How's it going? Well I think we're gonna start right. It's almost 1105 So we're ready live in five. Great, so it is really recording. I'm going to share with you they bought the GitHub board we are always following this meeting.
Here it is. And I'm going to share my screen as well.
So we normally start with the upcoming meeting agenda, and after that, we move forward to the In Progress column. But I just want to confirm that there are no items in the upcoming meeting agenda is certainly very interested in adding a discussion topic before starting the meeting. Or
I just want to call out the the situation with red Redwood cut from Master right. The findings from the last meeting were that we are now aiming towards may 9 or the cut off but if we can do it sooner, we will. Right and we're and that means that in our next meeting on the 25th we will review all the pending issues. And if we all think it's fine, we can you know cut from master as soon as is decided at that meeting. But for now, it's May 9, right? And if you're interested in in having that happen sooner come to that meeting on the 25th.
With it, I will I will make a posting in the forums just make sure everyone is aware of the current situation. But yeah, this conversation has been happening mainly in monthly meeting where we plan the red blood release effort among all the teams involved, not just the BTR but also product working group and another core contributors that have been working in implementations that are currently the reason why we are waiting a little bit more for including those in the release. So as I mentioned, if you are eager to join us for this last mile for decision making the next meeting will be next week's Thursday, the 25.
I also posted in the chat link to the redwood blockers that currently exist that are being worked on. That is going to be driving the decision to do one thing or another. Sorry for cutting you off.
No, no, thank you very much for those. Great so yeah, go ahead and this small
thing is my introduction. like to introduce Carlos marischal. Here in the middle is a new member of our team and you will be participating in some of the meeting says basically DevOps infrastructure and operations.
Hello, welcome.
Thank you a lot for a turn me into this meeting. is very nice to is my first workout. Like this free code organizations. It will be nice to contribute. Awesome.
That's great. Welcome. Welcome, Carlos.
Carlos, let us know if we can help you in any way. Okay. burgeoning a great community so we can collaborate in the future looks great. And something else to the coming meeting. Agenda column
on my screen. I was aware last week so I haven't really followed the route stuff. But then, like when I hear about the spring release, I feel like I need to do a historical reminder of why we have like specific dates for releases. Because in the past we try to do too much in some releases and other places shipping to win one, and everyone suffered a bit from that. So I'm not saying that's what happens because again, I wasn't there. So I have no idea. But this is just just to remind of that fact in case that happens again.
We're we're actually not delaying the release. We're just the lean the cut off from Master. So the release is still happening on June What nine floors some some something like that 10th or 11th. Anyway the differences that were waiting more to create the master branch and and the main reason is so that we can get a few interesting features in before right to make redwoods. Have more shiny things.
Again, I'm not saying anything specific is happening is just like, because I haven't followed. Maybe that's something that I have more in mind. But yeah, but does that mean that the testing will be like how does that work? If the good thing happens later, but the release still on time? So we get testing time?
So somewhat Yes, but it was offset by a few things. Right. So the main concern I'm going to rerun through the major concerns so hey, this is major concern was it takes time to upgrade the tutor plugins. Once the cut off from Master happens, and that is time that they tracked directly from the testing because the sandbox can only be created once the plugins get upgraded. And to in response to that, we like we now have a product process. Right. And it was product basically that came forward with the idea of putting pushing back the cut off from Master. So since that was agreed to the flip side of the coin is that product now allow owns the testing sheet. So product now like makes testing better and easier. Hopefully and more straight to the point. But not only that, because product also owns the development pipeline more than before not fully. That means that we can test stuff and tutor before the cut off, right. So the plugins and the features are already being tested in Twitter. So we don't expect there to be as much of a rush to get things working. Right. So, I mean, there's a lot to talk about. I'm just trying to say that there has actually been a discussion and we're going to see, we're going to see if this works, right? There's going to be an extensive post mortem or posts living after the release whatever you want to call it. So we want to make sure that we fix anything that didn't work, right.
Just rip it out. It's no no criticism at all. I'm sure there were there was a lot of reason is it's just something that I put in there. But it's true that a lot has changed with the the focus on product and I think a lot of those changes are pretty good. So it makes sense that it would move things around a little bit. Cool. Thanks for the story. Yeah.
Awesome. Cool. So moving forward. The next column is the issues that are in progress. So we are going to basically follow up on each one of them starting with the factory increase. So sorry, I don't know if you could provide a quick update on basic if if there has been some movement and the specification
might have been but the problem is that I probably haven't cooked up with it if there has been. So I'm guessing that if the stuff has progressed that will be on the maintenance working group but again, I haven't followed last week and if anyone else did
otherwise, when I get your async capital the meeting, I'll try to put that in there. The progress but I think last time I stayed like this so that's when we caught but it was going well there were additional people are offering to do maintenance. I don't know how we are in terms of completing like filling all the gap and etc. But at least things have been like quite a few organization and even your community members who have stepped up so So even for just that that has had an effect. And again, I don't know the specific a different number, a different factor number that we have now, but it's it's hopefully at least a few Dizzy mounts up. So
don't remember if if that was explained in a in a recent meeting, but there is currently an elephant factor that is that is being measured. So even though it's not updated, there is at least like a first measurement of that or, or
Yeah, well, historically, the measurement was very simple. That was one because it X was contributing more than 50% so it just needed that x to feel that 50%. So I don't know currently actually, index is below 50%. But at least given the amount of work that axemen has been doing. I'm guessing that that's starting to factor in there. So hopefully we're above one No but I don't know exactly how much. There was a tool that ADOT started putting in place to follow some, like KPIs within the community, Karima if I remember correctly, and then the I think the elephant factor was one of those because that's when one of the Kaos metrics which I think Grimoire is based on like, that's vague memory. So probably some some of what I'm saying is wrong, but at least Yes, there is a place for that. I don't know if it's being updated currently. But, but from the moment that elephant factor goes below one it becomes interesting to track it a bit more because that gives a representation of how much the different actors are like linked from from the project. So yeah, probably that's some question that we can ask next time is in a meeting or maybe on one of those tickets, because he's the one that will put it in place. So I think it's still accessible online somewhere. Again, I don't remember if there is actually the metric but since is tracking, like the pull requests and the merge and etc. That is probably the data to do that, I think is the organization that was like because I think that might have been one of the improvement points at the time. But again, all of that is old, big memory, so you would probably know much better.
Okay, it was trying to find the link of that dashboard yet. I think it is now in a service that is called bitter Jaya or something like that. So we can maybe you can add the link to the notes
later. Yes, um, yeah, if we find it, I'll try to have a look to it and maybe you will probably have more links for us.
Thank you. Then we have the core contributors as backcap reviewers so the last update of decision was last month.
So again, that will be outdated information from at least a week. But I know that there has been more work being done by Misha and team on that recently I saw a salvo of beings of contributors, being paying for like all requests that are pending. I don't know how successful that thing has been and how much of that is, is being done. But they know that they are actually following that and know really like as a matter of like standard procedure, thinking people work or contributors, hopefully on stuff that corresponds to their expertise when they know about it. I think there's also work being done to keep identifying like the main thing is like linking the maintainers with people cite the repository with them and 10 years and also with the core contributors that correspond to that, to try to have something that if not automated by both, ideally as some someday can be easier for patients and team to ping people. And some of that is related to what we were mentioning with the maintenance working group in the US as a nation of you maintainers because those go into the tool that makes that link and Ben it's easier to find what to pick. And I think the last beat also that was being looked at so that I just saw very quickly before going but I saw that vision and teamwork calling for a third project manager to assist them to do the triaging especially because there might be a transition phase where we need to start basically considering to use pull requests as any other pull requests, but they have a lot of pull requests. So there might be a phase where it's a lot to handle for the historically more limited OSPF process. So again, they probably have done some stuff and posted some stuff that I haven't seen in the meantime, but I know this is moving at least on those
next, we have other day software contributors to take on more permission and write rights and responsibilities. I think this is also related to everything is aiming to basically
I think this one signer has been doing quite a bit of work, because I saw several things from her and trying to follow up individually with people who had offered to do something. So So yeah, so and there have been like several announcements for the maintenance and that's actually what has brought up some of the new contributors or uncovered some, some organization to do that. So I mean, we can probably still do more on this and probably forever but a lot of that as has been done.
Gold and I think one of the more visible impacts these have had, at least for me is the increase in the number of containers and core contributors as well. I've been seeing a lot of new candidates in both slack and on the forum. So that's
Yeah, it really showed that sometimes you just need to make it obvious that that people would be welcome and necessary to something and actually some people would already have been considered it so it might be a good lesson to keep for like the future to do that regularly every six months, one year. Make a call for for for maintainers and contributors. Because they don't like I mean we've all been in that situation on the fence looking at what's happening and filling out this this looks like it's It's difficult. It's only in the really good ones. We do that and it's not true. It's just the ones who they're basically and so encouraging that can be really good. Yeah
so next we have the Requests for Comments from Udolpho for Essen rising on GitHub milestones of course workbooks. I don't know.
I don't hear any objections. But I did not actually do any work on making this happen.
Imagine with with redwood. Sure, yeah.
So yeah, that's where it is, like, I'm hoping to be able to automate this using axioms tools that I'm gonna need a little bit of time to to make that
hey, thank you know your friends
haven't seen any objections either. So I mean, I think like if that's kind of what glues consensus is, so technically that means the thing is adopted, right? So
yeah, I did ask some people directly like in particular Aksum engineering, everybody thought it was okay or a good idea even. It's just like the time to make it happen.
Great. The next item is obtaining feedback and iterate on current sprint, check ins and raters.
So I know that I've been teasing people a bit more, but when we were still, let's postpone it was like a week or so ago. Still, just like only 1/3 of the country Rita would feel this. So I think we'll need to have a bit more before we can get anything from that. So I mean, I am guessing that most of the people in this meeting I've already answered it, because that's kind of the more active ones. If you haven't, definitely please do. Because, yeah, that might influence the way we work afterwards. So if we just yeah, we need to get everyone's opinion basically. And I'm guessing then, because you will be falling maybe more individually chasing people who haven't replied yet to try to get that percentage higher. But that's why it is.
Thanks, have you?
Sorry, no,
I've just put an update these everyone knows 29 out of 66 responses. We're sitting at Ellie's currently on leave but like you say she sent out a reminder about a week ago or so. And when she's back next week, we'll discuss the way forward. Yeah, and we'll just take it from there and we'll just keep the group updated.
Yeah, I think like I was saying probably at that point is probably worth like, going to ask individually the people who haven't replied because I don't know if the the sometimes automated emails might end up in spam or people might be it's not important because it's not talking to me or it's like a group thing. Nobody cares. But, but yeah, maybe it's something more personal so that people see that. It counts individually. Great.
Perfect. Thank you.
So I did ask the core contributors at my team to answer the survey. I know some of them did. But if it's easy for you to get that information Cassie and you can let me know which members of FedEx core contributors from Edo Knicks are still pending for answering the survey. Please let me know and I can ask them directly to do it. We know this is important. Okay,
I'll see what information is available because I think it will just be who submitted so I can send you who's submitted and then you can take it from there. Great. Thanks.
Cool. So next we have improving the ability to participate as synchronously. Yes, of better a sync tools.
That actually just came up in a thread in the forum. I forgot we had a ticket for it. When we look at it, what number is that?
111 way to live it is it sounds someone asking about do stuff asynchronously in the farm I haven't seen yet.
There's this big not to get into it. But there's this big thread about the fronton plugins and I'll link to it shortly but so we made the decision to have front end plugins for redwoods based on the findings of the previous front end plugin Summit, right. But there was a concern that the decision was made in a meeting. And there wasn't, I guess, communicated asynchronously. Even though, like the progress actually was during many months, and it shouldn't have been a surprise to anybody. But it still was. I'm not disputing that. So anyway, the conclusion was maybe we should find better ways to to do this asynchronously. which is why I'm bringing this up
Yeah, I agree. I think I mean, the meetings thing is, I think it's difficult to avoid on topics that need to, to move forward, at least in this community, like historically. Do meetings if you don't meet like things just take forever or don't happen. At all. But, but it's true also that in their needs, at least, to be away for both we're not in the meeting to like jump in, be aware of that and etc. And I think there is already quite a lot of working group with to, like a good update. With good summaries on the wiki. But if you don't keep an eye on that, maybe you don't see it either. But so posting about big decisions on the forum, I think makes sense in my opinion, even if you have a meeting to really like iron out some of some of the stuff I think generally. Yeah, I can't think of a thread you can participate in the forum asynchronously on big decisions would be a good thing. Like most open source project would say that I mean, you have some discussions that always under being done on IRC and etc, but still
think for big ones. Yeah, it's it's like I, of course, I agree, of course, right. It's just that this particular decision was a bit time sensitive. Because we there's value and getting some form of front end deployability out in Redwood. Like actually there's a lot of value, not just because of the plugins but because this allows us to remove a lot of a lot of to you code from Master so it doesn't go out and read through it, right. So there are a bunch of like, I made the arguments in there. But but like even though there was a good reason to make that decision in the meeting and go forward with it. I agree. Like ideally we'd have more time in general or more. But like the last point I made then that we do publicize everything, right? It's all done in the open but it seems like there's never there's always gonna be somebody that surprised, right? There's only so much we can do. If we reach if we do like the 80% That's good. We're never gonna be able to wait for 100% of people to participate. So anyway, right? I'm agreeing with everything you said. It's just that it's there's always going to be somebody that was left out. I guess that's what I'm trying to say.
For sure. Because it's always a curse. All right, between over communicating were actually like people end up saying less thing because it's too much or not enough. but I think like if people don't see something in time, when it's already there, it's one thing if it only happens in the meeting, that's a different thing because in that first case, you're able to point to the person to say Yeah, but that was on the form. Are you reading the form? And and and then the people who haven't seen it know, the next step or next time okay, I didn't know I needed to follow that category in the form of something. It
was also in the form like it was a thread that starts with an announcement. Look, look, this is this is the front end plugin framework and look at it, you know, and still people didn't look and were surprised. Yeah,
but then I think that becomes a different conversation which is more about, okay, you didn't see it when it was there. Okay, what could have made it more apparent to you and etc. And then then I don't know, we realize that a lot of people don't read the forum. So we need to advertise that mode something versus Oh, I wasn't in all the meetings which is a lot harder to do action. I think a lot of it is about people feeling that if they want to be in they can't follow next time like they have something fixable that they can do and that won't happen anymore versus how sometimes it happens behind closed up which is definitely like developer or contributor returns for sure.
Like in this particular case, not to point fingers but just an example right? Not all the organizations are participating very actively in front end discussions in our community. And I think that's, that's what happened here in particular, right. So the fix is, if you're an organization in this community you should also follow developments in the front end, right? And that's historically been not the case, because historically too, you did all of the front end work and didn't ask any questions about anybody, right? It's just they just did it. And that's changing slowly, but some more haven't caught up, I guess. Right. So this totally wasn't a look, this is how we're going to do it. And we don't care about your opinion. It was really just oh wait. I didn't I didn't participate in time but now I don't agree. What do we do? Right kind of thing. Yeah, I guess. Yeah. Sorry. Anyway, yeah. I've I don't mean to get into really deep into it, but this has happened. So it's a still a very relevant conversation. Right? But that's what I meant. For sure.
Again, I couldn't give my opinion because they are one of the surprised guys.
See, sorry.
No, sorry for being surprised they shouldn't. Maybe sometimes what happens is that announcement like like this, you know, my first impression when a when I heard about the plugins is another plugin. It's not another plugin. Another type of plugins because we already have openedx plugins. We already have tutor plugins. And now we have further plugins.
Next blocks to well,
we can say that x x block is is an Dangar plugin. Okay, let's, but yes. So many plugins. That was no I agree. The point is that an announcement like that may or may have sound kind of too technical. And sometimes, you know, in the computer, there are many perspectives. If you take the developers perspective, for example, upgrading the younger version or upgrading to the latest node version. Okay, from the, from the developers perspective, it may be interesting, interesting, because you might have to change the code or developer stuff. But from the marketing perspective, which is also important. It might be difficult to for example, upgrading general version will is something important for marketing. I doubt I don't think so. But implementing a new plug in mechanism. So I don't know do some things in the paper. It might be interesting. Not only for marketing, I'm saying marketing because it might be an extreme but site operators. I don't know maybe even co authors who is really interested in something new that's happening in it's actually part of the of the backlog of the roadmap. Right? And sometimes things like that might might some kind of technical if I see a new plugin I don't care. It's not for me, I'm not interested. But then, if somebody explains what what is really the impact of a change to the student, to the author to the teacher to a site operator to the marketing team, where then may be maybe it's just thinking out loud aloud. How to attract the attention of other people who might be impacted. Will just okay, went through the news. Didn't pay attention.
What if I'm hearing you completely? And here's what I'm thinking. What if there were a sort of newsletter? I'm not saying actual newsletter, but something in that rough format that comes out every month. Like a digest with with different, like, here's the section for developers. Here's the section for operators. Here's the section for I don't know burners, whatever other like. And I don't even know what to call this stages, like developers don't i don't know like stuff that's happening that we might need your input on. I don't know I'm just thinking on my feet here because clearly, it's it's might be too much to ask for people to just read all the forum threads and pick out the ones that might be important to them. I'm not even talking about following GitHub notifications about prs. And edX Proposals or anything like that, but I'm just talking about the forum's now. So yeah, I don't know.
I don't really discuss has notification. Conference does send notifications for new thing new stuff and chooses what may be interesting to you. I don't know. You
can discuss you can you can pick which categories you get notification and each category like what kind like if it's why when the new thing only when you're paying stuff like that. You do have that? And therefore I would definitely plus one what you mentioned the newsletter. It's actually one of the changes that we've been discussing with kacian and Alia about, like the type of collaboration we do with between co contributors because I mean, I know that the reports are a little dry currently. So not that many people read them. But what you describe is kind of one of the goals or like one of the core goals is like one place where what what is happening, we need help, like what do you need to know and etc. So, again, we'll need to get to see the results of this survey. And I don't know maybe just if you want to say some some words about things that that have been thought of with this, but But yeah, I think we need something like that. And I don't know what the best format is, but but that's a way to make sure that people are aware and that collaboration can happen when when needed. Or
maybe another section in the forum about coming up what's coming up in in openedx. I think people will be interested in knowing what are we planning for the next releases. What's in the roadmap? Maybe not everything that's in the roadmap, but things that past the first stages and say, Okay, this probably coming up in the next releases.
Or problem like, we could do that. And I think we might even do that. But I still think there should be a curated short or as short as possible. At a Glance way for different classes of users of the platform. We have several to keep up to date, right? In a way that doesn't take like hours every month, but like minutes every month. So
yeah, I think that has lost activity. has lost a bit of attraction lately.
Sorry, I missed my impression. What what mill what happened for I don't understand what the
forum has lost. Oh, has lost attractive or has lost appeal or has lost activity?
Or I don't know.
I have the feeling the feeling that some there was some discussions happening there that before might not have like, like some recent dev claims about, about implementations and etc. I mean, there used to be mostly people coming saying I'm trying to install that that crashes will can help me and no answer. So that there was a lot of activity of that for sure. But that wasn't great. I think no, there are more answers. Maybe a bit less people who are on crutches. So I don't know if it's a good or bad news, if it's less people doing it or if they just have less problems. I don't know. But I do. I do feel that we do get. I mean, probably not enough. I think a lot of those discussions are still happening in meetings like like we were just talking about, but some discussions happen in the forum. So yeah, like maybe it's also a question of like, following the notifications in the right place and right categories, maybe I don't know. But
I just want to maybe mentioned something I think once we have the the results from the survey, we can toss around some ideas because I think one of my tasks that's currently blocked is also to to document our processes and to kind of define how for the these different roles in the community what were the bases do go etcetera, etcetera. And I mean, we could come up with the stuff as a group is what and they can just like, it can evolve as time goes by. So, just waiting for those results from the TV, I would say.
Yeah, makes a lot of sense. It's true. The documentation is like there are some stuff that are really well documented. There are a few things that are not that will be good to fix for sure.
Sure, your feedback, Andreas I wanted to say for anything else. Sometimes, a single person's feedback may drive like significant change when it comes at the right time. Anyway, sorry, go ahead.
That's true. I would agree. It's important to share about those things and to put them and the thing that I was just saying is more of a detail is just that, once we have that base doc about the processes, one thing that becomes easier is to iterate over that because then like changing processes, like either a pull request or an edit of the the existing process, and and so for example, if someone doesn't get the information and etc. And these interaction is how you missed it, so where would that where would you have seen it and then once you know that, then you change the process to also positive pay or something. So just to mention that like that documentation of it like code can have like I could improvements this way that might be useful.
Right, thanks unfortunately, this next item is all proposal reviews. Guess this is related to the next openedx conference. Or
I think this has been kind of done right. And we like I think mostly the people who have been doing that have been asked directly Amex to try so I mean, I haven't followed that very closely. But since I think all the proposals have been reviewed that kind of close I think
think at this time all the all the top proposals have had been reviewed right? I mean,
I think so. Yes. Oh,
oh. Speakers should have received their confirmations.
Remember last time I heard something about these may be in January or or December. The number of job proposals that we received was way lower than than last year. I don't know if that sufficient changed during during the recent month or
so Serena would know like that kind of stuff, but I don't think there was any problem filling slots right
yeah. So I didn't know if we could mark this as stone severe or, or or
I don't think so I think you can move it.
Okay, so.
Right so the last two items we have here. The first one is a sync working group of dates. And the section. I think this is also related to what you have discussed a few minutes ago.
Yes, yes and no. This one was more I mean, it is related actually because it's the reports that depends on the survey and etc. Everything is waiting on a survey but I think this one was to specifically to facilitate the life of combining information. So that was like the different working group posting the update. I think we're still pretty irregular all across the board about doing this. And I guess adding a step one some working groups don't really do even though the note taking might be tricky. But yeah, that might be something to consider also as part of the of the changes around the newsletter, the reports and etc. So I don't know if you have that on your radar, but that might be something else.
Yes, I think that's all going to be just it's going to all have naturally as we get the results and yeah, so definitely
Is there a deadline for for for publishing the results of the survey or you're just waiting, like until gathering enough information for actually closing?
Yes, we're waiting to gather all information then we can go through the results and we'll put together a report for the community to see and then once we have the results we'll also then come up with a plan would suggest suggested plan and obviously obviously everyone was collaborate based on what our results are. But yeah, so we will consolidate everything so everyone can see what we've what we've come up well, what's the results on?
Awesome awesome. Maybe that's a good segue for for deciding which unfortunately, I haven't been able to, to move the discussion forward. But basically, I mean, as they said, segue because maybe I could I could discuss these these proposed proposal in that space where after we get the results of that survey, we're just like, brainstorming ideas to actually improve the process, the processes in the community. But where this is saving to is basically to to to have a Northstar metric or or or something that could tell us as a community if how, how successful we are being with with all the work we we are doing year after year, so So sometimes I get these existential questions where I asked myself, Where is the community heading to what do we want to accomplish right. So what is like that future we are trying to reach out together so I think we are putting a lot of effort in this project. So sometimes I just, I just want to have more clear north, right. So this is something we are we are all trying to figure out in our like, companies and everything but I think it is important to to have this this conversation in the community as well. So, so that way maybe, normally what what what we can get with this is alignment focus and a more clear winner, winner without all the effort we will So I mentioned that objectives and key results are more or less common framework for for this stuff. But also having or starting simple as as just using a Northstar metric where where we can basically focus all our efforts to move that needle at first. That could be something that could work for at least, like as a first step. But the thing we we need to improve our our I don't know processes or or mechanisms we were using to measure our impact as a community. So basically, this is this is what this issue is about. So hopefully, we'll have a little bit more time during the next weeks to, to, to to make a proposal or or to maybe start the conversation in the community about OKRs and maybe we can align that with with the results of this RV and the action items that we can get from that.
Yeah, thank you for great 3d rendering, some metrics and even even if we don't get only even if we just don't focus only on the numbers, it's always like coming up with them and analyzing the evolution is a good way to raise topics and to focus on Yeah, we would agree with that. How do you see the discussion for like choosing them or brainstorming them or setting them?
So I think the first step for me would be to engage people into the need at first so right so so I'm trying to convince you, this is important. It doesn't matter what we use. So so so I'm just thinking out loud when I want to talk about OKRs that there are several methodologies for this. But I just want to, to, to gather way more people to this specific need, which is the need of First of all, a more clear vision as a community and secondly, a way to measure it. So to measure our progress toward that vision. So once we agree on the fact that's important, and that's something we we maybe don't have yet. I think we can we can move forward to the next step which is thinking about what would be a good solution for that. So So I would like to start the conversation about that specific need first before just we're giving ideas, methodologies and frameworks.
Make sense? On my site is already where do I sign so that
so 1% of the progress is already great. So yeah, please, please, please give me more time to think about this. I was just finishing some Argentine stuff in at 18. So I expect to have more deep, deep, deep, deep work capacity for for this during countries. thing with that in mind, we covered everything in the in the in progress and Phillip column. We have three more minutes. So I don't know if any of you would would like to add something else. Something urgent that maybe we missed and with that we can close the session. If not, I think we can. We can we can. We can finish it there. Thank you very much everyone for for joining us today. We will publish the recording the notes and the summary of the session. And see you in the synchronous channels. Thank you. Thanks everyone. Have a nice day.
