EIPIP Meeting 80

EIPIP Meetings · 3 May 2023 · 15:13

Meeting 80 of EIPIP, held on 3 May 2023. EIP editors and community members go over the EIP process and the editorial issues currently open. This meeting covers the EIP bot issuing numbers, open pull requests and the monthly EIPsInsight report.

Topics

From EIPIP Meetings, hosted by ECH Institute.

Transcript

so starting with the first item which is an update to eip1 and which is also related to Auto numbering of eips along with the permission to merge eips as draft automatically um the pull request number here is 6976 anyone on the call maybe like to give an overview of where we are in numbering these proposals like automatically numbering and what editors think about this PR to be merged where's Canada

oh yeah he isn't on the call looks like I just don't understand what we spend most of the call talking about his proposals that he's never here that's a good question but yeah sometimes it is difficult for people to be here and we try to discuss it async as well and so we moved the call so that he could be here though like he hasn't been here in two months or more right if I understand correctly he is

um he will be available soon I think summer vacation is coming up so he should be able to join calls regularly but yeah we can probably think I mean like a collector thoughts from other editors what they think about this pull request which is to update uh EIP numbering I'm not sure I'm I'm totally on board with the exact wording that's there

right now but um we'll we'll hammer it out in the pr that makes sense I thought when he introduced it it was opt-in doesn't seem like it's the case now for what the bot I thought that editors still retained the ability to assign members it was like if you wanted to opt in to letting the bot assign numbers for you you could but now the wording is this replaces oh we're looking at something different than the clear rules regarding EIP numbering or I was thinking of the numbering bot oh

okay yeah so the yeah the bot right now doesn't work so I turned it off um but it's yeah it just assigns the number on merge and overrides whatever's in the Eep I mean I don't really care that much because I will probably opt in but it's just one of these things where it's not quite wood we talked about do we want it to be opt-in or do we want it to be mandatory I mean if everybody is okay with opting in that's okay I don't know if Greg was on board with opting in

I don't remember I think Greg was like one of the the staunchest proponents for the bot okay yeah in my mind having girl like uniform rule would be ideal instead of having it opt in because opt-in will require some Editor to obviously chime in and provide an EAP number and it can be confusing for new Authors so yeah either we go by editors providing numbers or maybe activate the part for it but it is

I think we're just gonna have to talk to Japan about this in Discord and see what's going on there so does anybody have any idea what which need not be unsigned editors means yeah I think that's supposed to allow um using the title as the EIP number for draft eips got it thank you I have noticed recently a ping going to

ABC user ABC for a location of EIP number is that we are talking about the unassigned God Sam oh in the pr it says um Erp editors and accounts authorized by any any EIP editor can decide numbers which need not be unsigned integers and I think that's specifically what Justin was asking about yeah but it doesn't make clear that whether you know after a movement from draft whether the EIP number would still be I mean any hex or any alphanumeric goes as far as El implementation goes I mean they use

the number to sort of signify that this particular hard Fork has this particular eips I'll make a note of that on the pr OK okay so it looks like this PR 6976 requires some more edits and discussion and that could happen either on Discord or maybe on the pull request uh well I think that is the major item

for discussion today the next one is also about the EAP bot issuing number so the current status is the part is of Sam or is it still active uh somebody's changed anything since it's it's reverted to an older version all right okay um if there's nothing more to add on it we can probably move on to the item number two which is discussion continued from the earlier meetings um I have added only one issue here which was related to EIP 5507 uh it looked like the date which is

mentioned in the document uh is not correctly reflecting on the website last date so uh does panda need to maybe take a look at it or it's some bug I'm not sure of that was there an actual bug for it sure of this the issue here is like the last call date that is mentioned in the uh like I have added the link here in the link is not correctly reflecting on

eips.insight as eips.ethereum.org I haven't seen this issue with any other proposal I don't know yeah that might be a GitHub Pages issue um I'm not sure yeah okay and would you suggest me to create an issue in eaps repository so someone can maybe take a look at it yeah for sure okay I'll do that it's called and they are reflecting

ly this particular proposal had an issue okay I'll create an issue for that okay and uh that's it on major side of it since this is third me only we have three eips added as draft one is informational EIP which is Network upgrade activation trigger added by um the number is 6953 it talks about all the upgrades and the activation block and time for those there are two more erc's 6808 and 6809 one is fungible key bound token and

another one is non-fungible keybound token okay there are two proposals moved to last call yesterday in the EIP editing office hour and that's pretty much all about eaps Insight we hope to add more insight as we go um yeah anyone else would like to discuss anything share talk about okay uh Victor yeah sure Victor has a proposaly applicator please go ahead yeah so um hi this is Victor and uh since there's no more uh antenna item I want to ask

um if uh there's any updates on Our intention to uh build our groups so the context is set recently I'm trying to uh uh work on a proposal that brings ERC authors and developers together in a regular meeting and would like to kind of basically gauge people's interests by their possible work groups and I do know that uh I think um the same is it you that uh in in the in a big list of the reviewers you actually three people into work groups is that a good way to think of how what groups are divided and then uh is that a good way

to kind of put people in the bracket in the future and actually we have a way of uh recognizing um work groups in a more uh consistent way I can follow up uh I can follow the way how you think uh the work but just want to put it on the table on whether our Erp editors uh have thoughts and kind of put out a work groups uh categorizations in some way so I think work groups are or working groups or whatever you want to call them or are probably a good idea it's just I don't think any of us have had time to organize them yet um and I don't think we want to commit

the time for it um but if that's something you're interested in doing I think go for it and if you want to use that big list of peer reviewers is like uh a starting point like just to message people and see if they're interested in participating I think that that'd be great because like the way I was doing it like assigning a peer reviewer didn't work very well so yeah understood I I think I am going to like learn that and ex maybe um the approach is to actually put people who happen to be have capacity uh for a particular peer review reviewing in a certain time in the room and then have the author explain it to them so

that they can have some life explanation and back and forth discussion and then it based hopefully that trigger is more interest in uh the asynchronized on Thresh uh on on Forum discussion as well yeah yeah and there is the um the nft working group that I think it's anit has organized um yeah so that one's that that would probably be a good place to get started from right and also 4337 probably has its own work group that we can reach out and yeah baby yeah yeah sounds good uh thanks I think I can start from there [Music]

for four three three seven we have also connected it the telegram working group has been connected to ethereum cater Justice con we have a channel dedicated for 4337 discussion so yeah you can probably reach out to people from there as well and uh I'll just pop uh put the proposal here uh so that your editors could also be informed of this uh this proposal and make suggestions are very well content we also look forward to your participation if you're interested or have capacity um it doesn't have to be a kind of

long-term commitment it can be sporadic and ad hoc whenever you have time um hopefully do this every two weeks and you know rotating um in a rotating schedule and so that it will be friendly to Asia and friendly to Europe time zones in in rotating way or this is currently the plan but yeah I just put paste it in the in a text anyone has got anything to share all right this seems to be one of our

shortest calls thank you everyone for joining us hope to see you in two weeks have a good one two weeks see ya