EIPIP Meeting 34

Transcript

hello everyone welcome to eip ip meeting 34 i'm gonna share agenda in chat here so the first item um for discussion listed here is eip erc data we have been receiving interest from people uh they are showing up at ech discord and uh eip editing channel of eat rna discord so some of them have joined uh today the call to learn from the present editors and understand the next steps for them so i'm opening the flow for anyone who would like to like

take a lead on this and explain what would be the next steps for these aspirants so this is the um this is for people who are interested in onboarding right right so i believe one of the participants who showed interest in eip editing channel he is already here uh i don't know maybe uh brilliant if you would like to go ahead and introduce ourselves to the group and then if you have any question or trying to determine the process right okay yes so i'm brayton uh i

remember tim put out a message saying in one of the erp editing channels i think or saying that if anyone's lurking please try to get involved or at least uh signal your message and then also uh yeah say william mentioned previously i think that he was keen to do it as well so yeah it's really cool that there's interest and yeah i'd really be keen to sort of try to see if i could help out in any way awesome well thanks for showing interest for sure um and what what um exactly which aspects of the editing are you interested in either eip core editing like the um stuff that mica mostly does or erc editing that both mike the both uh light client does as well as core editing that he

does i'd be primarily interested in the former however it seems like there's more demand for the ladder or that the ladder is currently a bit less addressed so in the spirit of that i would be keen to just sort of kill any voids or to assist in the expansion of where resources need to be essentially and what would you say is your technical and ethereum background that would make you um qualified or someone who would uh that could train up for something like this so as a disclaimer i'm under the impression that a lot of the aip editing work is sort of just grunt work of checking that it's in the right format again so just being familiar with eip1 would be sufficient but regardless of that uh i would be less susceptible in some sense to working on

erc since i don't write smart contracts directly i just have a pretty broad interest in eips in the current eighth space in general i suppose okay great that's but i'm not a cryptographer for instance god are you a developer at all not particularly i just do some research in a relatively small firm in australia okay well um anyone who's interested i think um should definitely be given an opportunity to try to um on board in one way or another as kind of a maybe a junior editor or someone who can uh get a feel for how things are

and maybe even be our guinea pig for someone that we train up uh to see if the if you if it fits for you um if you actually like the work and it would work for you and that kind of thing uh and see if it's a good fit overall is kind of my thinking um i know from talking to the other editors recently there's not a lot of bandwidth um for um training up but i think what we can do is since people are starting to be interested make like a shared group chat and like discord um and just start going from there from the ground up um seeing how we can best give anecdotes to how we do things as

the ip editors and uh make sure that the newcomers are comfortable and get what they need to get to start working on it i hope that word vomit made sense i like the idea of having a group chat to help on board people i think a good way to have people get started is if we can create a chat with the current editors and the people who wanted it on onboard as editors and have a place where they can just ping us directly and say look i've reviewed this this is this uh this change is okay to go it just needs an editor to come in and double check in the merge happy to create one at edm cat address

in this card if that's fine with everyone here and editors are already there and we can add the assets yeah um i'd be okay with that well like client and micah specifically do you all check out the cat herders discord enough to or like are you gonna would you turn on a notification for that or would it be better to have a dm would you be more responsive over like a dm it doesn't really matter right to me i can turn on notifications for a specific channel and cat herders go that way or we can just have a dm just basically the same thing okay michael you have a preference

whatever no same okay yeah pooja let's set up a channel on the cat herders discord then microreads every channel honestly this is true that's true yeah it's really no different to him i don't see the lie there um okay so uh yeah we'll get this channel set up and thank you so much um how do you want to go by sport druid bray do you want to go by your name or by your nickname or so my name is grayson but i'm responsive to either okay just be score or something i don't use spore uh i'm joking yeah names now huh

no that's true okay cool um all right uh that's about it for that piece i think puja unless you have anything yeah yeah i'm fine uh so the next item i i believe hudson if you would like to speak for it as well yeah so we've been given word that the ecosystem support program from the ethereum foundation which is a they what they do is they do some form of grant giving and other types of support for ecosystem participants has given us a grant of ten thousand dollars to start out

uh paying eip editors from discussions individually with the eip editors it looks like we're going to be funding light client for their work eip editing for a certain number of months do you remember what we laid out puja i don't have it in front of me i think it's initially for three months and then yeah will be really validated and then we also have funding for was it two junior editors yeah yeah great so basically um we can release the numbers later for those who are

interested but um this is just kind of starting out as a test thing for how much and um how frequent we would pay editors um because we only are guaranteed ten thousand dollars for a i think a three month period like you mentioned pooja we can reevaluate after that um what we get what funding we can get from other places or from esp again um so i i don't foresee that being an issue but i don't want to jump the gun either so we're just being careful with how we distribute the funds but we've allocated all ten thousand over three months for three people basically yeah um and uh one last thing before

we move on to another topic unless anyone has any question uh which i'm not sure if you have had a chance to look into the document in which uh the primary requirement of an eip editor and high level responsibilities are already mentioned so feel free to refer the documents here sounds good sure and i think that is it for that topic if anyone has any other questions about it or um is interested in becoming an editor or junior editor um outside of the people who have spoken up which would be william and spore just let me know all right so

uh the next item of our discussion is progress on eip github uh repo action but um i know uh this issue or that is linked if the agenda is open for a while uh so i'm just trying to understand like if the initial task has been uh completed and we can close up that issue i understand that what uh work is something going to be an ongoing task and um uh yeah i mean like we can always open a new issue if there is new task any update i don't know it's on the card no i don't see her on the call today so i think like i think the initial task

is done and micah would have to confirm on that um the well i guess aside from essentially the only thing remaining is i have to turn the spot on which i'm going to be doing today so um and then kind of like following up with any issues that occur right where are you at so that makes sense it mines with my understanding yeah thank you so very much anita for the update so another thing uh i mean i just

randomly saw it there um uh if it is not i don't know uh there was this message related to but blocking several merges i believe that is already on the radar so not sure if people would like to uh like discuss it here or async is fine for that um did you say oh yeah it's blocking merges yeah yeah so we're gonna be changing that like that's the final step i guess and that one is uh gonna be changing to no longer blocking today if that means i mean like so as i feel

like it used to not be merging and then now it's going to and that's kind of like uh the change that should hopefully close out the tickets i think what she's referring to is the um thing we talked about that we're gonna do after uh we get this started to merge which is the bot should notice when an eip editor approves an eip that is changing statuses and then unblock at that point yeah i think that there was one uh i think this is like previously i don't know um yeah that's something that i will be

addressing thank you very much um real quick can you add when you make that group uh for the eip editors and perspective editors can you add aleda to the group if you don't mind alita so we can ask questions about the bot um that might come up yeah sure thanks cool i'll i know that today um yeah so if anyone has any question on this uh item particularly or comment if not we can move on i think the next item

is progress on json rpc api spec in 81.4 so this one is we like i'm kind of in the works right now with tomas kind of planning out um the timeline and expected like like outcome of the product um it's kind of like there's a lot of work involved with json rpc perhaps like more than i think a lot of people realize uh at least assuming that you want to do the edge casing stuff that hasn't been like super well defined um but in any case the step number one is going to be um

just building out like the baseline converting eap1474 into an open rpc format and that is in progress but i mean the goal is to get that done by the next meeting if i understand correct data is there any requirement for any other resource uh like further action from other people uh no i don't believe so okay sounds good okay

so uh next item listed here is uh progress on canonical sources for eips yeah i got got that um my understanding of the goals are we want to separate the eip standardization standardization process from the network upgrade process and we also want to remove the ercs from the eye repository and then i notice on the agenda changes to eip1 so i'm wondering my recollection is we decided to leave eip1 in the eip repository but anyway yeah i'm wondering what's up with that sorry about that uh i think uh that particular point i have added

uh uh to kind of list the changes which has been uh which have been discussed in uh different meetings of the apip itself and they have not yet been updated to current eip1 so if we can have that listed somewhere maybe that would be helpful someone can uh you know create a full request for all those changes okay so um it is yeah i guess i'm not familiar with those changes um okay is there a list of those changes somewhere or something confirmation that's that's what i was

trying to get here like if you can create that list i'm not sure like in if someone can go through the uh like earlier meeting notes and whatever the decisions taken maybe i can work with you on this async and try to come up with that list so that we bring it up well that sounds good yeah if you could help me with that i appreciate that and i'll try and carve out some time for that um one another thing that i found on the document the wip document that is added here in the item that is about uh adding the search button to eips dot org so um i'm wondering what group thinks about

it like i i think that it is something that is uh that could be helpful um is anyone from the group like willing to work on that or how do we see that as a priority here one possible easy way to do that is there's a way to configure a google search so it's just a simple plugin to tell google to to and and other sites do this too and have google and you and you just restrict the google search to the site you want to search so we can restrict it to eips.ethereum.org and and then people could type in there and search only that content that's one real easy way to do that kind of stuff

or with some and another suggestion was to use they pointed to some other site that has a wordpress search um custom built for wordpress sites but i don't know if that would work for us but anyway those are two possibilities yeah i think there was this issue created i'm going to share here the link i am not sure if that is already like looked into okay okay yes sam okay yeah yeah i'll review that and it

looks like that's the place to talk about um more of those possibilities i'll review that site and see if i can um help contribute there also sounds good i think if we can add that in the document like as a point to be considered would be great like if and when we have people to work on this particular feature to be added on ethereum uhdm.org i think that is going to be helpful yeah the document's getting a little bit out of date a lot of things have changed since i last worked on that so i'll work on getting that cleaned up too right so one last thing that i wanted to bring up

in this particular topic was uh the cleanup of eips.etm.org i took a dump sometimes ago and it seems that there are 361 eips on total that is existing on the website and out of that 360 1 242 are in draft status we can see that the uh present poll request in the eips github repo is not that much like it's a very small number so there are high chances that either these proposals have have been superseded by some some other proposal or

is obsolete and maybe we would want to move them to withdrawn wondering if there is any way or any part or any program that can be that can be helpful to figure out and bring them together in sync do people have thoughts on that yeah so for the bot can i possibly look at the inactivity the last edit or last time there's a pr for that file and move it to withdrawn after say a year so the present part already closes it

like if it is inactive for three months or six month period of time it already closes the pull request the issue uh that i think is here is the status is not being changed before it is closed so so i'm not talking about the pull request i'm saying can the bot chain open a pr to change the status if it's in draft for say here that is certainly possible right now we're doing that manually right micah right now we don't do it at all we've talked about doing it before that's

right yes it'd be a good idea to set something up to do that i don't really know how urgent that is someone else can kind of figure that out yeah right i mean like on like priority uh i mean this may not be something of very high priority but it would be good to have um maybe we can create an issue and if and when someone is available to do this task that can be assigned that would be a good task for one of the

junior editors to get started on maybe yeah yeah okay micah just said it in chat yeah okay so i maybe created an issue for this particular task and let's see how we proceed in this thanks future okay um [Music] looks like we are going to end up this early today we have already reached to the last item unfortunately we did not have uh meeting notes available

as of now but i think we should have uh some action item listed here let me see uh yeah uh so or if you would like to walk us through that yeah so sorry about the notes uh the interaction items maker felt that one thing that we could do would be the banner to put up the big red banner to say that this erc is not accepted it's still facing a draft status and then elita said that she would be keen to have a go with that i think oh yeah i totally forgot about this i will too look um is this is so the requirement here

like i look into it a little bit and it would be a little bit challenging to actually have css in um in the markdown so i think the easiest way would be like if we just included a picture of it and then just like displayed it on the top like is it is are people okay with that [Music] what's what's the reason we can't do html css well gee you can actually uh if you do like the rich markdown um instead of just regular markdown you can do it but the problem would be

like you would need to uh convert it to a rich markdown which i'm not sure if there's like some issues with that or whatever it might just be easy html file i thought um inline styles worked in march what was that instant sorry uh inline styles uh worked fine oh wait i think i think you should be able to do so if you look in the eips repo under underscore layouts folder um i don't know i don't know which one of

these it is but either under underscore layouts underscore data or underscore includes i believe um somewhere in there is like the the page itself um not the earpiece but the page like the renders the aps and in that one it just should just be html and you can just add css like inline or as a style sheet i believe and that would show up on every page that matches some requirement so in this case a draft would be the requirement and it would every page that matches its draft would get some header oh i see any means so you're talking about like

a banner on the the eips like dot org thing yeah the eaps.ethereum.org um so not this banner would not show up in the github repo but our hope it and belief is that most people are interacting with eips through the ethereum.org except for authors and if that is true then those people will see this banner when they're browsing that page all right yeah that should be easy then um okay do you mind like giving me a bit more like just like chatting with me on discord and telling me the exact like specifications of the name okay thanks yeah now we can do that in let's do that in

the cat herders cip's room or the uh r d eaps room in case other people have opinions uh i will anyway create the channel today so um i think uh it can be continued in either of the forum okay um maybe it would be a good idea um later just to have a reminder on that

because this is the chance that he would be undertaking so you know create an issue and then rotate that status later on sure that's fine uh by the way i should create these tickets on um i think the ethereum categories right eid region that should be nice i mean like the apa github or you can create an issue there okay sounds good thanks okay um another point is a discussion arrows to brother william schwab should become an erc editor

unfortunately he could not join today he had a conflict i did mention it to him so i'll add him in the group as well um if he is still like looking into uh i mean looking to be an erc editor and looking into this uh this direction nightline crazed the idea of hosting consultation hour uh where people could come and they could use they could just uh give five minutes pitch of their idea and some could stamp it like this is not an erc when you should have provided some resistance to this idea okay fine i don't see any action item uh implied here so uh we can just leave it when

we will have it in the inner part of meeting notes so that is it yeah i think this is going to be one of the shortest either does anyone have anything else to bring up okay um in the case um may i take a few moments to announce a survey which is directly not related to the process improvement but with the ethereum ecosystem in general so yesterday canada's uh distributed a survey that we are conducting for ethereum blockchain users

and developers it's for better understanding of future requirements of client developers in terms of both tools and documentation um so if people who are listening uh this medium on the youtube if you interact with ethereum blockchain run ethereum 1.0 or 2.0 or otherwise contribute to blockchain technology uh please respond to this survey i'm gonna drop the link in the description box this research is uh done in association with uh nedermein our core client of ethereum so that's all for the meeting today thank you everyone for joining see you in two weeks thank you