EIPIP Meeting 45

Transcript

welcome to eipip meeting 45 i have shared the agenda in chat the first item listed there is a general consensus for closing recent most discussion to issues i understand we were discussing it uh in the last call like how do we manage the long list of open issues and how to point people for the right place to start the discussion to uh link for any new proposal i suppose we have updated the eip1 with a strong recommendation actually to start the discussion thread at fellowship of ethereum magician but

still we are receiving some of the new issues where this particular section is being used as a discussion link for new proposals i understand uh a few meetings ago we decided and there was a bot uh which was updated to generate message for new issues uh saying that if this is related to proposal discussion please create a fem thread and close this issue micah i see your comment that that message was supposed to be for the um new contributor only

yeah it's the greeter bot that gives that message out right now all right sorry i thought that it is for all new new issues that has been created but i suppose this can be updated and as per your comment so it doesn't look like you are against it so what do you think would that be a good idea to start uh for every new issues um i mean i guess the question i have is what do we want to actually use the issues for and maybe this is a discussion that will need a bigger quorum than just you and i to hash out but what's what is your initial thoughts on

what are the appropriate types of issues that's right i mean this is a broader discussion i agree but my thought process here was like the issue and challenges those are being faced by new people who are trying to contribute with their proposal or their ideas in the sense like not only for discussing the proposal but also the challenges that they are facing during the writing of it what kind of help they are looking for and if something sucks maybe i'm hoping to use that particular section to be a point where people come up with their issues and that issues could be discussed here in this eipip meeting in future to um help out and maybe streamline more

processes around eips and network upgrades so the issues would just be for basically editor discussion correct yeah because that is an eap uh github so it should be mostly for editors discussion here i'm fine with that but like i said we'll probably need to get more feedback from other editors see if they agree yeah i don't you just wait yep the easiest way is probably if you want to create a pr to eip1 and just mention alex matt me maybe tim as well all right yeah this is not something that has been

added to eip1 yet but uh i think it would make sense if we are in agreement or maybe we i can start with creating an issue in this issue section saying that how about we start using this issue shepsen for different purposes i mean i'm not discussing at this point like whether or not we should close the earlier issues which were created for that that may require a separate discussion but at least this new i suppose was that a question i think i missed it no no i mean yeah that was kind of a statement but yes i suppose we should keep it open for

next meeting or maybe i can go ahead and start discussing in the github itself we'll we'll see what feedback do we receive there yeah thank you i know today it is all on you because we have only one editor in the meeting sorry about putting you on the spot for this okay so uh the next item i have added here is an appropriate placeholder for the active eap validator so i see this pull request which has recently updated the readme of the eip repo which is good like we should not be having the old ruby one and we should be

redirecting to the right one but i was wondering like this uh points towards an individual's github repository which i think would not be a good practice i understand uh like currently he is uh he's a great contributor and we would like to keep it that way but it would be nice to have a placeholder for this eipv so that uh in future we can also get pull requests and updates from community as well as uh it would be easier for us to maintain rather than keeping it individuals this come up in the past matt is totally willing to move it over to ethereum we just need someone from the ops team to do so okay i mean i'm not sure if you if you

have any senses of what is required maybe i can follow up with the arts team and try to get it i don't know what the process is i've never looked into moving a repo my guess is that um they just need to create a new repository named i don't know eipv or whatever they want you want to name it um and then they would just uh clone like clients repository into that essentially make sense basically just do a little bit of get magic okay uh maybe um i'll talk to

um maybe jamie or someone from the ops team and try to get this new repository created cool moving on to the next item it's about an incidence which was reported for pull request four four seven eight four four seven nine and then four four eight four and four four eight five so the thing is i can't find eap seven two two in any of the repo i mean sorry the atm repo but my understanding is all these merges are associated with that i i saw that there were some comments reverted but i was wondering yeah why did it happen in the

first place it was a it was a bug in the auto merger it accidentally auto merged something that shouldn't have it's all the user created a new apip with a number they gave themselves they didn't realize that they weren't supposed to and the auto merge bot just said sure and emerged it alita very quickly fixed that so it shouldn't happen again and the eip has been moved to an appropriate location yeah right because i was seriously surprised like it can happen once it can happens twice it happened four times what's going on yeah great thank you alita for saving us yes

i believe the problem was is the initial pr got auto merged and then the user was then able to um edit their eip because they now had eip 722. and then i think alex finally got in contact with the user and moved it to the right location so it didn't exist anymore so if you looked after the fact it wasn't there yeah right i think i looked a little late and i could not find the proposal and that's caused my wonder thank you for updating that um the next item listed here is eip's insight that's a monthly reporting on eips so for the month of november we have

three new proposals introduced as uh as draft we have um three eips those are moved to stagnant and three resurrected from stagnant two to back to review and one is moved to draft from stagnant two proposals will move to last call but i suppose the review period is already ended and now there are a pull request uh in the repository to move it to the final status and there was one eip which was withdrawn by the author none of the eips were moved to review or

the final status but i suppose there were some non-normative changes for eip 2681 and 2124 some of the noticeable updates for this month for eip1 where we have updated the eip process the process image for stagnant status and there is now um description for preamble fields to eip1 change in the field review period end it has now been updated to last call deadline and the updated field has been removed from the template

couple of other uh updates uh the one is running the rule for the discussion to urls so that's on the eip inside side um the next item listed here is a eip editor's apprenticeship meeting um we could not conduct the second meeting this week but i have seen quite a few interest from community and they have started contributing um from like on different proposals yeah i would like to say yeah it is and i also talked to a couple of people uh individually and they said that like

we can see some of the inputs the comments on the repo itself but there are people who are also working in the back end connecting with authors uh there is this guy who is talking to richard because richard is trying to pull his proposal back and uh it's nice to see people are trying to engage themselves i suppose we will get one sorry yeah what do we think is the right next step uh to keep these people engaged like how do we ideally eventually convert a couple of them to eip editors like what do we want to see or like yeah i'm curious

you know how because because i think we we want like people to like you know proactively do stuff and whatnot but once they are doing it uh how do we like encourage them and and get that keep them engaged so that yeah they stick around ideally that is an excellent question i still don't know why i stick around so i don't have an answer yeah i think it's it's something that we need to think about sorry stephen i saw you were unmuting uh please go ahead uh yeah thanks uh from my point of view i just contributed my my in my first two bounties and i just learning everything and having a look around and i think um

what you do brilliantly is all the documentation it's it's really good to to get the foot in and i think you're a strong community and that's the base for for for a good onboarding um i'll i report back when i've got more information from my point of view if that helps yeah 100 uh and if there's things you know you think are confusing or it can be done better or like yeah that are just like friction points if you can share those that's that's really valuable um yeah because it's it's the first time that we have like kind of a cohort of interesting people interested people um yeah and i think we want to make sure that we we don't lose people because like we just have a bad process or whatever

sure yeah we'll do yeah awesome thanks so uh we have planned the next meeting on december 7th as i mentioned earlier i hope to see more people or people coming with the sharing their experience for the past two three weeks and if they have any new questions so anyone listening to this on the youtube if you are interested and by insurance if you have missed earlier meeting please make sure to join this one otherwise the recording will always be shared with the community all right that was it and uh we are almost at the last

item that is listed on the agenda for today uh the review action item unfortunately we do not have the notes for it uh i was informed that it will be up later today uh sorry for the delay guys but i have a point uh listed it out what were the action items from the last meeting so um i made a poll request to update the web link to uh text removed from bibliography from eib1 i see it has been approved by one of the editor but it might require um address like one more approval from the there's two editors uh to be merged there is this period made sorry please if it goes another two weeks with no one else reviewing it we

can just go ahead and merge my policy is generally if we get two editors to review then we merge right away if we can't if we only get one person to review then just wait a month and then merge oh all right that's nice okay and uh the couple of other um pull requests are one to update the discussion to place and status cases and i think it has been merged already um yeah there was one action item on me to create an issue where we can start looking into adding labels to prs i have shared the eip bot um

github repository with a few people in the community like the new contributors whom we are interacting and i'm looking forward to get some input get some update and help from these people i know stefan is one of those i shared the aip github repository so we may be expecting some help in future i know alita left some comment unfortunately she is not here uh for this meeting she is traveling but she left some questions and uh concerns that she has about this sharing responsibility or transitioning responsibility as of now i do not have any one single person in my mind like who can be like

taking over completely but if you do not get anyone i'm hoping to make it decentralized like making these chats bounty based and get it done but for sure we will be having people around to take care of ech engineering chess uh that's all from the item listed i know uh tim um uh you you missed the discussion on the first item when we were discussing about uh the discussion two link for uh general issues so i'm i'm hoping they're like maybe we can

create an issue or pull request and tag you and uh and rest of the ap editors and have the discussion over there um yeah that's all anyone yeah yeah please anyone wants to bring anything up regarding elita's comment on or question that she has in the agenda i'm fine with her just picking so if she wants to do number two of her options i'm okay with that yeah that's all right yeah i mean it's on her comfort level like of what whatever she wants to do like any thing i mean generally we try to label them and out and i don't think there are a lot of issues so

when it's like when there will be a lot of issues then that can be priority based but that's okay good to know yeah anything else anyone wants to bring up otherwise this is going to be one of the shortest meeting of either it's nice when no one shows up because they're all out makes it very easy to come to decisions yeah right i have nothing else in danger all right folks thank you for joining in

uh the one major change that i'm hoping to get it done in future is about like whatever the issues and challenges people are facing that needs to be added somewhere from where we can start getting data because it's random and i have to search on all the discord and the issues and github's repository so i'm hoping to make the eip github repository issue section is the section where anything that you want to be discussed or brought into attention offer the eip editors can be listed and we can take it out and start discussing in this eipab meeting so folks if you are listening and if you have questions comment concerns anything either show up on our discord channel or add it there in

the issue section we'll try to bring it up in this meeting thank you everyone for joining us today um i hope to see you in next two weeks have a good rest of the day thank you thank you likewise