Everything EOS Mandel Launch Group, 9 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS MANDEL Meeting #5 (March 9th 2022)

Description

All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37
#eos #mandel

Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.

// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF

A

All right welcome everybody. This is the fifth mandel working group call it's march 9th and uh let's have a look at the agenda and we can talk about if there's anything else to add I'll share my screen on the agenda. I've got some more clarity to follow up on the mandela cold strategy, some updates on testing on jungle.

A

We can get a check in on the survey and the the work we're doing on assembling contact information for all the exchanges and apps maybe revisit. This is something that came up in a previous call that we decided to park was whether we needed to set up a mandel development channel in telegram or elsewhere.

A

At the time we said it was maybe not yet necessary, but I think, maybe time to check back in and we can check in on how things are going on kylin as well all right, let's get into it start with this one. Here I saw this question from matthew in the chat which I think is related to this matthew was asking you just want to clarify, make sure I understand what is in mandel 3.1 from what I heard.

A

It's based on mandel 3.0 rc1, we're going to be merging in the b1 2.0 latest stuff, we'll be porting. The diffuse from 2.1 and transaction lifecycle features four of them per the api plus blue paper. Reputation should also include the state.

B

History, uh sorry, which one the rotation box organization, okay,.

A

B

Include the state history, loans.

A

Also includes state history.

C

Logs, I I just copy pasted in the mandel upgrade launch group channel in telegram the scope of of that with links included. You.

D

Want to verify.

C

That comes from stan actually, so it should be good, uh duplicated features on modules yeah. I uh posted that as well, so it's github issues, 7597 beauty, it's essentially just really three things: yeah three lot: big things: the blocks, log or state history logs and then the diffuse deepmind, logger and then the deprecated features- and I just add- I haven't gotten confirmation. So I retract my statement of last week. There was confirmation that confirmation was pulled back, and so I no longer have confirmation. That is what is being worked on.

C

So I'm still waiting on an update on that.

A

Okay, so is there any impact to our timelines that we discussed so far or I'll assume we're on on this the same pace at this point too early.

C

To tell likely no impact but uncertain as to whether or not the work is continuing, so I believe steven is on the call. I think, the last time the mandel repo was uh touched by the fractal team was 14 days ago today. So until I get an update, I can't answer. I don't know.

A

Stephen, are you able to provide an update? I.

C

A

Not been assigned to work on it at the moment, okay, so I'm waiting for updates from hireup cool, okay. Thank you so we'll we'll keep following up and we'll check back in next week. Anything else to add on this topic all right. Moving on well ted is.

D

A

D

Ted, can you comment on that question? Just ask which question on the question that eve commented on already. Is that what you're asking me to comment on what.

E

Did you ask stephen about in terms of the plan for work on mandel from your.

A

I think it's we're wondering that the status there is a portion of work that dan's team, the fractality team is, has been assigned that we're currently not sure what the status on whether or not they're working on it.

D

I know the exact status eve knows so I stand by eve's statement.

A

So yeah we need an update from the fractally team on that on whether or not they're committing to do the 3.1 release is that right.

C

If I mute it correct yes, okay, maybe, and if that is not the case, so essentially we're just trying to find out sooner rather than later, because if it is not the case, then we will have to assign different resources to it.

C

I, to the best of my knowledge that won't change the timeline, because the timeline for the transaction life cycles is still the end of june, and so I don't see how that would change it, but I I don't know until those new resources join and until we would need to know if we need to assign to them this particular file. So it's too early to tell at this point so basically waiting. Okay,.

A

I've added a comment with.

C

That update there and thank you, kevin kevin, is actually has been doing work in the repo. Thank you very much. That's one thing that maybe would be worth adding, I'm not sure where, but in the communication strategy. Maybe daniel I'd like to add an item about maybe just say, communicate mental repo and I'll I'll know what I want to say. Communicate.

A

Mandel reaper: what do you mean by that part of the develop developer resources package.

C

Kind of no in maybe put it in to do, and just.

A

D

C

I can touch upon whenever we have time in the agenda. Unless I explain it, then we're going to go into it right now and it's not the time remind.

A

Remind me what you wanted me to write just.

C

Say communicate mandel, repo and I'll know and then you'll when I'll explain that you'll be able to reword.

A

Okay, it's there.

E

Maybe maybe you mean by that and if not fine whatever but uh like, I wasn't sure of the procedures on mando repo, for instance, I have approval on a couple of pull requests, but I'm not sure does that mean then I should hit the merge or someone else will do that.

C

Yeah, that's I'll wait when we get to that item I'll, explain it's there's nothing wrong. It's there's an opportunity and I just want to so. Let's wait, let's wait for that item and then I'll explain it, and maybe it addresses what you're saying fair enough.

A

C

It's not because somebody did something has nothing to do with that. It's nothing bad.

A

Beauty: okay, moving on uh tess mandel, the only update I have to hear is: we've got a a couple. More bps have joined and have been put into producing spots, so we got uh aloha and astonishing are now also producing on jungle. I don't think we ever came up with what the threshold, how many bps we want to be running before we're ready to start the test, but I think we wanted more than this, so we'll keep working on getting more vps to register.

C

uh Stan would you be able to participate? I just I know that amsterdam isn't in the list you're on the call.

A

Oh yeah, yeah sure all right I'll. Add you to the list here. uh Well,.

D

E

On the call here that might be able.

A

To uh participate on jungle, okay, hefner can run a private node from home. Cool go ahead was that you kevin.

E

Yeah, I'm not sure about running a private note at home, uh maybe no worries. I think you know how to run nodes. I'm guessing. You know how yeah I'm not sure like what for serious. I'm not sure what like this throughput would be. I'm limited on my isp on like data transfers, so just just don't run a.

C

Public note and you'll be fine, but no, I was just joking but yeah. If we can get more people, that would be uh that'll, be good. I'm just scanning the chat here I don't know. Well, that's fine. We can keep looking yeah. Seven would be okay, because then seven people run three notes: each. Oh, it's kind of standard in the test nets, yeah.

A

I'm sure we can make do, let's we'll give stan a chance to reg, produce and check in on how we're doing next week. Maybe we'll have a few others also, and I.

C

Think costa rica mentioned they were trying, but they kept. They were having issues so that would potentially be another eighth one. I don't know if it's in your list or was.

A

C

I don't have them on the list, but I can put them. Was it the question? I think it was in jungle. He mentioned that it was yeah, it was javier. I think.

F

It had to do like the jungle. Monitor, has to be manually, registered it's a little different. Sometimes so I think they were ragged as a vp, but maybe it wasn't seeing their api and then, of course, I think they had some problems with their server.

C

Crash but yeah, one of our servers is having a bad day so anyways.

F

Maybe tentatives.

C

You want to put a javier as well cool, so costa rica yeah. I think.

A

That should be good yeah.

C

I'm not sure which name they'll go right.

A

I don't have anything I don't know. If uh stan you had a chance to look through the survey questions from 1.8. If there's any feedback, you've got at this point, cool we're still that's also. The somewhat related to this is the stuff you're working on any updates on the dev resources you're assembling. So I guess that this would include the documentation any progress on documentation stuff. All right. Who was that question directed to.

C

A

Sorry for stan no, I wrote I I was completely out for like a.

B

Few weeks, no problem.

A

No worries got an update from randall. Is he on the call randall you wanted to talk about the progress you made. I put the. I saw you shared with that year. You make this progress, your team. Did you want to talk to that? If not, if you're not able to speak, I can speak for you. I see your.

D

uh Yes, you cannot talk. Okay,.

A

Yeah, thank you randall, so randall and the eos support team have been working on creating a database of exchanges and dapps and so far they've collected 291 email addresses of the 363 that we've identified that we want to that. We want to target so making good progress there. Any updates ted on the docker image documentation the.

D

Gentleman that is has volunteered to do that has gotten was in the hospital and now has shingles and struggling with a bit of a health concern, and so he's asked for a little more time, but he has uh committed to doing that.

A

Okay, do you need a couple more weeks? Maybe at least next week will probably be too soon to check in let's try in two weeks and then that's the mandel development channel wanted to talk about that. We, it was brought up. I think on one of the first calls, and we did. We agreed as a group that for now the mandel working group channel we got is going to work fine as we get. I think the development we're getting more teams on board and things like that, I'm not sure is it time to revisit.

A

Do we want a special development channel for mandel? Do we need one? Does one exist that I don't know about, or are we happy to continue coordinating in the mandel upgrade channel.

C

When we have releases like this, the proprietary channel like that is good, it's temporary and then everything goes back to the main eos io dev channel, which I don't think we should fork out of because it's got so many people in there right. It's a.

D

C

Good user base: that's where people go for support in general, so I would not see the need to create a new channel or to change um other than again like what we're doing right now. It's a particular particular release or particular function. Then we just spin that off that way, there's less clutter and I would say that it should be open to anybody. So anybody who wants to join should be able to come into that channel and maybe, when we started.

A

By that channel you mean the existing the mandel working group channel that we are already using yeah. I agree, so we can continue coordinating there if it gets out of hand and we can fork off if we need to we're.

C

Going to need to put a bot stopper at some point if it becomes too much, but that's like any other, and we also leverage the jungle channel. The kylie channel, the main developer channel, the vp name, chat, channel.

A

Yeah yeah yeah there's quite a bit. uh We can do there, okay, so, and how about I'm going to just consider this we're going to close this and we agreed it's not necessary done, I'm coordinating with the allow mao to reactivate the faucet. Don't have any status progress to report other than that. I think that was it besides the new item now that communicate mandela repo, do you want to cover that eve.

C

Yes, one of the metrics that is often used from people outside of eos or just people in general, looking at any blockchain, they go and look at the main repo to see how much activity there is over a period of time, and one of the issues that we've had with the main repo that was under block one was that a lot of the development was being done in sub-branches or was being done in private repos and so from the outside world.

C

Looking in uh whenever they were doing marketing material or whenever their missouri reports or whatever it is, it always showed for the last after I guess. After the mainnet launch, we see a decline in prs. We see a decline in essentially development from their point of view, development of eos, and it would be great or there's an opportunity for anything that we do going forward. Everything will be open. Obviously, nothing should be private.

C

We should be figuring out how we can leverage the mandel report, whatever repo it becomes, so that everybody's contributing to it so that for the outside world that doesn't know all these sub branches, whatever they just go to one place and they can see. Oh great, a lot of green eos is being worked on, whereas right now they see. ah If you look at the block, one repo block, one has not touched it.

C

I think since july 10th or something like that- and that was just one bleep and before that was in may- would be great to have one location uh where we see a lot of commits where we see everybody is working in that one and why I was mentioning kevin was just because yeah when we look at the mandel repo we can see when the last time somebody touched it. It would be great if that becomes the norm. Everybody contributes to that one whatever. It is any work that comes out of the blue papers or ongoing.

C

Basically, it's all in the same repo. In a way, that's organized that for somebody who doesn't know what we're doing and all the subgroups and the sub branches and everything they can easily see all the development that's still being done by eos. So the story would be you'll stop developing publicly, and now it goes back up.

C

I don't know how we want to coordinate that what we need to do if there's, if even if that is a thing, if there's anything to do, but our competitors definitely capitalize on that and make sure that data is accessible publicly without needing to jump through hoops to get it because, typically it's coindesk or coin telegraph or whoever they'll just go to the main branch and just look at how much cream there is.

A

Yeah, so the goal, if I understand right, is to communicate the strategy. Broadly, that hey we want people all collaborating here. Stop collaborating in your silos, bring your work to this common repo. That kind of possible.

C

Yeah so that the yeah just so again for the externals, they won't know all of the hundreds of different repos that we're working in. If everybody contributed to the same repo, somehow they would still own that their work that it's still theirs. It's still linked to them. But there's that common point where the externals just go to one location, to find out all the work that's being done in er, whereas we don't have that right now and so from the outside world. It does look like there's no development on eos.

A

So the the real objective is to visu like to bring to the surface all the work that's happening in one place.

D

A

Everyone, whether it's like in one mandela, repo, that's, maybe that's one option to be able to meet that objective like I'll share it.

C

In the group- and maybe you want to pull it up on screen or whatever, but it's pretty obvious when you look at it just from a visual point of view and the idea is to be able to get back what we had before, which is a lot of contributions like you can see it died off. That's maybe not the best one. Let me find another one. This one is pretty obvious and if you go back to 2018, then that's when you see significant change because it counts everything, everybody who's contributed.

C

So the second one I just put yeah you can see.

D

C

Is no longer being worked on. That would be great that we now have a repo where everybody works in again.

A

And you mentioned that, it's common that I guess, crypto aggregators or people who are trying to assess the health of a crypto project are using this as evidence on the health of a crypto project. Kind of thing. For.

C

Sure, yes, because they they likely don't go embed themselves in the community, to ask hey what are the 150 repos you're working in you go to the main eos branch and then they look at the main contracts. That's and they're.

A

Like oh nothing's being done on espn nothing's,.

C

A

They can't see all the working groups, that's.

C

A

On and all that stuff is hidden if.

C

You look at this, then they. It also reinforces the idea. That was the repo that people were working in right, because there is a lot of. There are a lot of contributions, and so it reinforces that the repo that they're looking at is a valid repo. I said it just it's a terrible narrative and right. You can't blame.

F

Them so we wanted they're, not even not they're, not in any.

C

Blockchain they're just they're cambridge analytica they're, whatever their missouri reports, they're whatever.

A

So our repo should ideally be the inverse of this we're flat and now we're.

E

A

Could anyone have thoughts on how we might accomplish that yeah.

E

So that is mainly due to just the way, github github reports and then block one's branching strategy that they used so the way their idea was, they wanted the main landing page in github, the the master branch, or now they call main right. The main branch when you land to be the last re release or the most recently released version of the software and those graphs would update when we would merge when we switch over the current main branch to that given release.

E

So it would be show like nothing until release day and then it would like all retroactively and then it would set idle until the next release date. Now, when those releases were far apart, you know, depending on when you look yeah, nothing happened, which is true. Absolutely nothing happened on the main branch until they did a release. So the way to play the game quote unquote is to simply just make the main branch, the landing page branch which doesn't have to be made, rename it to developer.

E

You can make you can change that setting in github, although I think you're better off just going with the defaults. Otherwise, you have other issues with github, but just make the main branch be quote. Unquote your development branch, where everything is happening and then do release branches for when you do a release, uh and then you won't have this. You won't have this issue, then the only thing you need to do is on the readme on the main page.

E

Just make sure that it's clear that hey this is the development branch, but you probably don't want this version. You want to go here to get the download releases. I.

A

See ted nodding his head in agreement. Did I capture that we're going to? We want to make the main branch the development branch and make a release branch when you do releases yes, and that would be that's something that all I guess all the anyone who's working on the mandel code base needs to be factored in, or is that something that the enf has to change in the way that they that the github repo is set up? Mandela repo is already set up that way. Okay,.

C

I guess to be clear: what I would like is that, whatever it is, we do here just like what kevin mentioned, the way that it's done. We would then communicate that to everybody else. That's working in eos, for example, on the blue papers, so that, ideally, whatever is coming out of the blue papers. They work in the mandel repo to do that, so that everything that's being done for eos is in one location. It's still, you know linked to all a bunch of other locations, but that way eos as a whole is capturing.

C

So the repo as a whole is capturing the work that's being done in the ecosystem.

A

So it's beyond updates.

C

Yes, and no, because all of the work that would be done in the arguably the work that'd be done in the blue papers relates to eos io.

A

Yeah, so that's the I don't expect we'll be doing our pomelo stuff in the mandel repo, for example. That's eos work so we're with blue papers yeah. It makes sense, but maybe we need.

C

A

C

Whatever it is, we communicate the way that kevin just mentioned it, that we replicate that elsewhere, so that we have a formal like this is how it's done. This is how.

E

We're doing it this.

C

Is why we're doing it we'll just copy paste that whenever people will be doing work for the booth.

E

You can consider doing is like merging back in cdt and, like example, contracts into the main repo as well. That gets you additional traffic there and you go back to back to more of a mono repo, so merging.

A

Sorry say that again merging what was the so.

E

What we did at block one was right: we ripped out all the various components. What used to be eos was broken up into many different repos. We created a contracts repro, and then we even went one step further than that recently, where we broke out each individual contract into its own repo, you know, and so that that goes against what you're trying to do here. So you know you could bring the the contract example quote-unquote example: contracts back into the main repo you could bring cbt back into the main repo.

E

You can bring the usgs back into the main reaper right, so you could basically merge all the various eos repos into the mandel repo, and then that gives you of course, then a lot more activity.

D

In that particular region, there was at one point before I left block one. An initiative dan had started to create, go back to the mono repo and he had. We had started funding to get a person to work on it. Greg lee and and todd fleming were starting to look at it and then that's when they made a kind of big shift. Dan stopped, focusing on it and gregory was moved over to uh b2b sales and stuff like that and it just the initiative died.

D

But that concept was something that dan realized to become a bit unwieldy and had started to ask for a model after dan had started like full-time coding again and started working on rodeos and stuff like that. But it died out. It's a big effort to do that. To get it all, working and compiling correctly.

C

Yeah and when you say it's a big effort, is it in terms of human resources and time like multiple people over a lengthy period of time, or is it one person for.

D

A month more than a month, and we we were getting to the point where we felt we would need- and this stephen we should hear what stephen has to say, but where greg- and I felt we should hire a full-on build master so that the person merged was able to merge it all back into a mono repo but was able to make the whole repo be able to build and all the dependencies stay in alignment and everything. Because what was hap.

D

What dan was finding, as he returned back to coding, was very hard to set a developer environment up and have all of these different repos coordinate correctly. So.

A

This big effort would be specifically for this if we were to try to merge the cdt, esg js and example, contracts back that, whereas this on its own would be a minimal effort. I'm guessing.

D

Yes- and I think dan was probably going further than just the four items you list there- I think you're going to take it a little farther than that to go back to the model repo.

D

So you would call that initiative, mono repo, it's because they're split across each one of those things is a repo and so you're moving them out of their separate repos, eos js cos cdt et cetera and you're, just making them subdirectories in one big repo and then you're building trying to build that whole repo and everything. And so that's where it's called a mono repo versus multiple repos, a single repo.

C

Anybody listening in that might be something that you want to write: a thousand to three thousand words on submit to the blue paper feedback strategy with a budget, a proposal.

A

Yeah, I guess yes, do. We have an action item here. Besides, hey community you now, you know that this is something we want so raise your hand if uh this is something you want to help kevin.

D

Or stephen, do you guys want to talk more about the pros and cons of kevin or steve a proponent of going back to amano repo, or do you see a lot of pros about staying as separate repos.

A

So the main disadvantage is that git is just not really designed to handle mono repos, because git's model is, you have to get everything. The monorepo works better with a version control system where you can pull subdirectories at will.

D

What about the fact that it used to be the case that even for pieces that were not dependent block one, for whatever reason, one wanted? Probably because of brendan, wanted to make a big release splash each time, so they would hold back stuff that could be released independently and wait for the big release so that that might have made it where, in the block one way of doing things, the mono repo wasn't as painful, because you had the one big splash release every six nine months whatever in in the new world.

D

We're saying we'll release things that are unrelated when they're ready would that have any impact on it. Stephen or possibly,.

E

When model repo was discussed internally for what dan was talking about, there speak for dan a little bit here, which probably shouldn't but the normally. When we talked about the monorepo, it wasn't so much bringing cdt and usgas back in and the oas js into the repo is is a little weird, probably but cdt used to be part of the main repo, as well as the example contracts.

E

But when we talk about tomorrow, repo we're strictly talking about at least recently the all the sub module repos like fc and chain base and app base and all those the model repo was mainly about bringing those back in because they're a pain in the butt with like some modules in github or earning get is just are a real pain, particularly when you start trying to support multiple releases like I often if I have a change that needs to that affects fc along with eosio there's times when I have to create, as many as as a dozen pull requests to get one small change in, because there are multiple versions of sc, a sub module that you have to have a pull request into, and then you have to then update that sub module in all the various eos branches, and so it just blooms out into this.

E

Like mess of things of all, I want to make this small little change in fc and wow. It's just not worth it. If I can live with what's currently there, because it it really it's just a pain in the butt to do all that.

E

Where a model repo, you would uh simply have to do that it cuts that in half in terms of you only have to do it in each of the release branches now, once in fc and then once in an eos and word help you if you've got an app based on chain base and an fc change that you have to do you wind up doing 30 pr's just to get some change in once you start supporting multiple releases across multiple sub modules. It it becomes a real nightmare.

D

I think it's what kevin made a really important point: it's the sub modules like chain based and fc, or whatever not things like eos js, which is javascript, and nothing to do with c, compiling and dependencies and libraries and stuff like that. So the mono repo would be more of those sub modules and not things like eos, js or possibly, not even that that might be a consideration if those have been split out.

D

I think that's what dan bumped into when he started, trying to compile latest versions and he was getting wrong versions of sub modules. In with the larger thing he was compiling.

A

App base fc chain based vm app base fc. Is that all two separate fc here, comma, slash, fc and chain base.

E

And usb m and avios.

A

The spelling of all these things too so.

C

A

Else can post the list and I'll paste it in there or I'll save this as an issue, and anyone is actually. This is a public repo, so anyone can add it.

C

So generally, the idea would still be that when somebody from an external, that's, that's doing a report on how much the chains are being developed at least now, even if we went with just with the the monorepo sub modules made me naughty os js, not cdt, for example, they would still come into eos and still only see three things. It's easy to click on three things: it's really difficult to click on 140 things, you'd still get.

C

They would still be able to add those three numbers or four numbers, it's much easier and that would mirror what other people doing. Does anybody see? I'm not saying that we will necessarily do that, but is anybody vehemently opposed to this idea if we started exploring that from the enf's point of view.

B

Maybe we point the user out to activity reports if we just need to show the activity on on github like these.

C

B

Aren't common to us.

C

That's what I'm saying these people aren't reaching out and asking information. Just these people are typing in eos github. They go to the link, they see and they just click. They never talk to you, you never even know they were working on their own.

B

Read me just the first few lines and read me of of the central repository just put a few links.

C

B

Yeah, there's no repo make their.

C

Job much easier as well like I'm not saying not do it but and I guess then the question was more so would you be opposed to if we started exploring this idea, I would say yeah.

B

Developers, uh code maintenance, I think, is primary priority right. If you can reduce the number of sub modules and make life of code management easier, we should do that if we just need to display activity, we have ways to do that. We can just point: just publish the links on on on readme. We can place the links for pointing to development activity and most the the actual development branches.

B

So we can just guide the user where to look for activity. If you want to see the activity.

A

In the same organization, just different repos is that right, you can.

B

D

A

Repos too, so one thing about d7 moduling. If we do it, we have to do it all at once. Block one made the mistake of partially of doing it trying to do it incrementally and only applied it to some branches and that made it 10 times worse.

E

Yeah, it was a nightmare because we did it and then undid it and so merging across those branches were yeah. It was basically you had to remove your entire directory structure and start over every time you had to sleep. It was a complete nightmare, but stan I'd be interested in your opinion on like, for instance, you use chain based, I believe, or app-based or app based as well. Yeah, both yeah cfc as well having it in a model. Repo complicates your ability to some degree because yeah yeah, I mean they're libraries, I'm.

B

Using them as libraries right exactly you don't belong to one one ripper instead of three. That would be the same work for me, but if they belong to mandel as a whole eoc or software yeah, that makes a bit complicated, but it's also doable. I mean it's also possible. That would be just supporter in usi repository, which I would have as a model that works too. I would say yeah we need to analyze calls and pros and cons for maybe is there plans to move like chronicle into? I know it's not obvious.

B

It's possible it's possible to have because it is integrating integrated in with the usio and also it depends on state history version right. If state history format changes, I need to update chronic. Also it is linked quite tightly so yeah. It could be also sub project on that needs. Thinking. I think we we just need to have just maybe a few proposals on organizing.

E

The code for sure yeah there are different, pros and cons here. It's not all on one side and in the end of the day, you may decide that the effort's not worth the the different, because you just switch one pro for one con in a lot of cases, but.

A

Okay, how do we want to move forward eve? You mentioned that the enf might investigate this further. Is that right, do you guys have I have uh we have a.

C

Blue paper feedback process going on right now, there's a thousand eos 2000 eos online for things that may have been omitted in food papers. This could be a way for somebody. So.

D

There's only incentives on the line for somebody just to make a little proposal.

C

And say what the pros and cons are, what the potential budget would be. What would be needed to make this happen? Call to action then, to.

A

The community to hey here's, something we're looking for feedback on.

C

It's not necessarily that we would do it, but again the like uh kevin just mentioned: there's pros and cons of both, but then, if we had the information we'd be able to make the decision.

D

Thousand dollars, if someone writes a proposal that gets approved into the blue paper, it's 2 000 eos. To do this stan. If you wrote one and kevin, you wrote one even if they disagreed, but they were both viable options. You could both make four thousand dollars to just hammer out a thousand word proposal on how this.

C

Could be done nobody's using the web form if you can't read instructions, it's very difficult to justify four thousand dollars. These are three.

B

New guys that are joining all new guys, maybe just assign a task to this code structure and propose.

D

Repository until april 11th and april 18th, assuming they all start when they said they were going to what might be nice if you would be willing, is we form a very small subgroup of maybe stan kevin stephen. If you would be willing plus those three gentlemen and we do a quick investigation or something I think missing. Brian johnson as well would be very helpful if we could get a few of you to be willing to do that, but they won't start. They can't work on anything for us until after april, 11th and april 18th.

D

So two will join in the eleventh and one and eighteen that.

B

Is okay? I mean it's, it's not urgent, right, refactoring,.

D

B

Refactoring, the whole structure structure is a long work. Basically analyze. You need to write a proposal, analyze all pros and cons and then actually do the move. It's six months ahead of uh to actually finalize so, if they're coming in a month, it's fine, just they're, fresh, so they're fresh on the assignments. This is.

C

There's more work, there's more work than people. It's not a problem, stand, there's not a problem. I've got we've got way more files that are being requested of them of than people that we have to be assigned to those files. So I'm not also not saying that necessarily. This is what they'd be working on at all. That's why I'm making call out to the community who's listening to this, that this might be something that somebody might be passionate about, that they may have.

C

You know feedback that they'd like to provide there's, currently a process, incentivized process for obtaining that feedback, for something that wasn't captured in the blue papers. That, I think, would be an opportunity worth capturing potentially depending on again on.

A

The pros and cons four thousand dollars not just for submitting it, has to be accepted. How did how does.

D

Accepted you'll get 200 you'll get 100 eos just for submitting as long as you follow the guidelines for submit after that, if you get accepted it's 4 000, it's a two thousand eolios, so it'll be more than four thousand, so I I would believe that kevin or stan could knock this thing out, at least at at most four hours. That's 500 bucks an hour if it and I think theirs would probably get approved, even if we don't implement it. Just we accept it as it's a good alternative or good additional proposal.

D

It doesn't have to ever get paid for implementing, doesn't.

A

Have to be accepted as being implement has to be accepted, as this is valuable for the blue papers. This was valuable.

C

Feedback correct: it was valuable feedback that was not formally put in the blue papers now, maybe something that was thought of from the original authors, but they decided because obviously the blue paper is what is the final product. There's hundreds of pages behind that it may be that the teams decided, you know they're only putting their top seven or whatever things, and they left that one out.

C

But then that's external feedback from a third party that say actually we think this should go in and then the authors again go back and say ah now: we've got somebody else that thinks this should go in so there's a process with the the original authors as well. But essentially, if it's accepted in the community, enhanced version of the blue papers, then yeah you get. Your bounty sounds.

A

Like a good opportunity, there was mention so you're you're, mentioning some names there for a sub. Do we want to talk about a subgroup, or is it too early for that? I think it's.

C

Too early for now, in my opinion,.

A

I'll leave that off for now and then we'll see what comes out of the blue paper feedback and then, if we need a subgroup, we go from there.

D

A

Any anything else to add on that topic. I will maybe read the name, maybe.

C

That's what I was thinking, yeah initiative or something like repo.

A

How's that and I'll get this cleaned up after the call. Maybe someone can help me with the list of stuff, I'm missing.

C

In the main chat in the mandel chat, uh a few people posted oh great. Thank you I'll.

A

Have a look at that after okay, anything else, those were the items on the agenda. Are there any other items anyone wanted to discuss while we're here great all right? Thank you. Everybody we'll see you again in a week and I'll put out the summary and the video when it's ready. Thank you very much. Thank.

C

A

Thank you guys. Thank you. Everybody thanks daniel. Thank you.