EIPIP Meeting 119

Transcript

[Music] Heat. Heat. [Music] Heat. [Music] Heat.

Hold [Music] on. [Music] Heat. Heat.

[Music] Everything.

[Music] [Music]

Hey, [Music] hey hey. [Music] Heat. Heat. [Music] Oh, [Music] hey.

[Music] Hey, [Music] oh, [Music] hey. Heat. Heat.

[Music] [Music] Move

[Music] on. Hold on. Heat. Heat. N. Heat. Heat. N.

[Music] Heat. Heat. [Music] Oh,

[Music] come on. [Music] recording in progress. >> Welcome to EIP IP meeting number 119. This is August 20th and this agenda is added on issue number 1628 on Ethereum PM repo for discussion. We have some open issues pull request that we would

like to collect editors feedback thoughts and either merge or close these items. We have a couple of uh presentations aligned, couple of community projects that people would like to showcase and uh EIPS insight update. So um to kick off this meeting maybe we can start with call for input item. I am noticing that deadline for both the items have passed. would be curious to hear from Sam where we are if you can maybe briefly explain these proposals and any decisions on this one.

>> Uh sure. So on the first one here it looks like uh so this is 389 allow links to protocol buffer specification. Um this is about linking to a library's docs. Um yeah. Um if we want to do that, we'll approve this. It looks like we have what? One, two in favor, and me abstaining. So that looks like it'll probably go in. And then uh chain specific consideration section.

So this is um a proposal to add uh like a section for say test nets or for non-mainet chains. So um we I could imagine things like arbitrum or optimism getting specially noted in here or or test nets. Um yeah um those are the two uh outstanding call for inputs. Um >> do we want to keep it open for some more time by updating the deadline or do we want to close it today by making a decision based on the inputs collected so far?

>> Um if anybody else wants to comment on these do so before uh the end of the call. Um I'll close them then. >> That sounds good to me. Thank you so much Sam for taking care of that. Uh next is uh a list of proposals PRs. Um these PRs are update two final EIPs. Both are on ERC side. Um the first one is ERC PR number 1053.

It is to it is an update to ERC 165. Does anyone um object to merge it or Yeah. What do we think there? Um, I still think it's technically incorrect. So, I'll I'll talk to this person some more. >> Very well. With that, >> yeah, the next one. >> The second one is um 1159. I mean this really doesn't seem

necessary to update. It's changing the following standard allows for the implementation of a standard to this standard defines a common. It seems kind of unnecessary. >> We can perhaps close that given the proposal is already in final status. So we will only do whatever is necessary and seems right. With that we can move on to next few sets of uh PRs which is related to website update. Um there was this discussion even in the EIP editing meeting office hour meeting yesterday. I will come to that. But

maybe we can begin with the first PR which is PR on EIP repo 10163. I wonder what people think about it. I'm going to share the link here in chat for quick reference. uh Gajjender approved it but he mentioned that because this PR would require more than one reviewer's uh approval so I brought it in the EAPAP meeting people can add their review comment or objection if any I mean yeah we we can do this it's

we don't really have anything on our website that's attackable. So I don't really know the point but yeah sure we can we can merge this. Um that is good to know and it is even u good to see that people are trying to send some PRs in order to make the website even more like user friendly attractive and secured as well. Well, the next PR is to add a dark mode to our website. The number is 10154.

>> So, that one's specifically for adding um a toggle, right? It's more complicated than just dark mode. >> That's right. Yes. >> Yeah. So my personal opinion is just toggle it in your browser if you want um to change your theme. Um we already have a dark mode. >> Okay. Yeah. I think from the comment added by Gajjendra Singh, it seems like he's also not too much in favor of adding this. Do we really need this toggle functionality because there is already a dark mode there?

Yeah, I'll leave a comment. >> That sounds good. Thank you so much. There was this one problem that was discussed about adding or referring to an ERC in an EIP. It seems like uh the author tried multiple ways. It tried by absolute link. It tried by reference like slash and then the number. But none of them worked because of EIPW bot. So he also suggested a fix to the EIPW bot.

And the link to this PR is added here. I suppose the link uh to this PR is okay. The PR number is 101. Sorry 1 140. Um most likely um Sam we are leaning on your end to maybe take a look at it because this is EIPW and you have worked mostly on it. So would be it would be great if you could maybe take a look at this PR and see if this is a good trade.

We can merge it that will help a lot of people. So for the time being uh the author has removed the reference of that particular ERC from his proposal. Anyway the proposal was supposed to be moved as draft so he removed it and uh open to add it back when this part is fixed. >> Sure. But that also doesn't make Anyways I'll look into this. It it shouldn't be doing that. Um >> yeah yeah yeah we we tried all the methods live on the call but none of them worked so we thought we should

bring it to your attention here. >> Okay >> very well with that we are done with this miscellaneous I know we have bunch of more um force merge PRs. I wonder if uh because I understand mostly force merge are for Sam. So I wonder Sam if you would like to take it async and take a look into it and we can get into other. Perfect. Yeah. So um we are moving on to the next one and thank you for already taking care of a lot of PRs. I see half of them are already merged before this meeting. So thank you so much for taking care of it already.

The next one is new ERC editor on board. Um I believe uh Mercy she has been working and supporting as ERC reviewer and wants to make a case of onboarded as uh ERC editor. We do have a timeline of 6 months but uh I would like to give this opportunity to her to propose her case and collect thoughts from present editors. What do they think about it? Mercy floor is all yours. Okay, I don't really know what to say or how to officially make a case, but the idea point is I would love to officially be an EIP and ERC editor

and >> Sure. So, um, the official requirement is you get an approval from every one of the other editors. Um, for my part, it's basically you've been doing great work on the poll request, so I'm uh in favor on that respect. Um, I guess I'd just like to ask you a little bit about how you feel about Ethereum, what your thoughts are on like um the direction we're going, what kind of things you'd like to see in the space, and um I don't know just just generally how you would govern the EIP process if you were an editor.

>> Okay. Um so what I would love to my initial stick point would be to help authors um streamline to help streamline um EIP and ERC um proposals properly. For example, I'm building this tool that will help um it's more like an AI powered um sematic sax to for um Ethereum improvement proposal. So on the last call with Victor, he did mention about having similar um ERC's and then all of that. So I'm kind of trying to help authors to help them easily search and get similar related ERC's they are working on. I don't know if that makes sense. So it's for now it's kind of like on the command line aspect that's I'll

be the UI interface but I'm just trying to round up round um get over that and then I'll present it. I'll push the code today and then I'll send it to you to take a look at it. The problem I'm trying to solve is to the hundreds of open p requests at any given time. It's difficult for because I did um I did have a talk with some um authors and they said that most times they don't have the bandwidth to start sashing previously meshed to start getting information on to know whether it's what they are trying to implement or what they're trying to propose has already been proposed before. So, I kind of like see it as a way to help others streamline that aspect. That's also a

way of me contributing to the ecosystem. No, that sounds like a great uh improvement. I think we'd love to have something like that. Um, but I don't think you need to be an editor to contribute it. Um, I think we'd be happy to take that from anybody. Um, but that's not to say we don't want you as an editor. It's just um I think we want to hear more about like um the direction of Ethereum as like a cryptocurrency specifically and then like like Victor said um how how would you approach governance for the EIP IP process right that's too many processes EIP process >> I don't really have a particular answer for that I'm sorry

>> oh no worries we can uh yeah we can talk about it a little bit offline, but yeah, based on your contributions to like pull requests, I think I'd be really happy to have you on board. >> That's great. Um I have also shared in the chat just link of uh the work that she has been adding to the EIP and ERC repositories um from the chart that we have received from EIP insight. Moving on to the next item.

Next is community projects. Um I suppose Mercy wants to showcase a project that she is working on which is related to ERC checking tool. Yeah, Mercy please feel free to >> Okay, I I think I I did a little bit introduction about it too. So the whole idea is to have an AI powered cinematic sash to for Ethereum um ERC improve um proposal. So it's still on the command line um aspect. I will have to build a UI for it. But currently I I'm trying to solve the issue of having similar or related um ERC's being kind of like proposed when um

during the last call by Victor um we noticed similarities of um authors proposing similar that has been proposed before. So it's kind of like going to streamline that process of not them easily getting the information or even if it's not I know it's might not necessarily be the same in any way but it gives them the idea and also know that oh this kind of thing is in place if they if there's any adjustment or whatever so it's kind of I don't know. >> Yeah I think like I said I think that's a great idea. I think it'd be super helpful, especially if we could have like uh something that commented on new

poll requests saying like, "Hey, these are other things that might be in the same area as yours." Um, yeah, I think it's a great idea. >> I'm going to push the code today. >> Maybe later you can share it in the EIP editor's channel. um yeah with the editors if you would want anybody to review them. Thank you so much for this mercy. We hope to see the tool coming up and please feel free to provide updates on the EIP editors channel on caterus discord or EC discord

uh just to make sure that you are getting feedback and incorporating them accordingly. All right, with that we can move on to the next community project. I suppose Victor here wants to showcase or talk about weekend Ethereum newsletter that is initially recently started. Yeah, Victor, please go ahead. Uh we can't hear you Victor if you're speaking maybe unmute.

Okay, I I realized I was muted. Yeah. So, very happy. Hi, I'm Victor. And then I'm bringing in a uh a project that was supported uh by uh ERCF efforts. And then uh the goal is to help um people stay on top of development news. And this was inspired by a week in Ethereum newsletter uh by uh our very much AB uh I don't know how to pronounce his name but AB code hub co-op um and um this one is new and it was uh um supported by AI curation and then we are hope the next

stage is to put human in the loop and then hopefully uh improve the governance but at this stage we're trying to uh let people see them on the website and then also you can start subscribing it. It will be delivered in your uh mail list uh in your mailbox every week. Um and uh the code is also open source. You can take a look. Look forward to feedback. Look forward to uh contributions as well. Project lead is uh is Angela Lee. credit goes to her and uh look forward for more uh contributions and also uh suggestions.

>> This is great. Thank you so much, Victor. We can definitely use more information or more news around Ethereum. So, this is an addition to that. Thank you. The next one on agenda is okay. Next one is already shared. I think it's from the previous meeting. A platform designed to address critical pain points in the current EIP process. If people have missed it, maybe they can check out EIP IP meeting 118 and may follow the recording over there.

Moving on to the next agenda item which is um other discussion and updates. I noticed we discussed about uh updating a label called typo on EIP and ERC GitHub repo. I'm not sure if it is there but definitely we can filter it by using typo. Uh are we planning to add I don't know Sam. >> Uh let me see if I can do it. >> Okay. >> I I have no problem with it. So >> okay I think that would be helpful but even if we are using the word typo and we can filter it out we are getting it there. But I also noticed that EIPS insight has created a different chart in which these particular uh PRs are being counted and represented. We will get to

that. So that is also there if people want to follow. The next and important thing I don't know how much ready we are but I wanted to bring it here again and the decision on the new website version of EIPS inside which Sam was working on for some time. Sam, if you would like to maybe talk about it and see if anyone here on the call has has any objection or if they are all good and we can like just switch. Yeah. So, um I haven't done any work on it in months but it is basically ready to go. Um if anybody objects let me know otherwise I'll just do it one day and nobody will notice hopefully.

>> That would be the smoothest one. I mean I personally have no problem. I wonder any thoughts from Vector. No objection. Very well. So Sam, it is up to you. Whenever you feel ready, I mean like you as you said, it is already ready. Whenever you get a chance, maybe you just switch it over. Perfect. Uh the next item on the agenda is EIPS insight. We will get into monthly AP status reporting but I received I think uh uh there are a few few items that this team would like to talk about share and present. I see Danush Nikk on the call. Danush if you

would like to maybe share the updates and the progress from the last. >> Yeah sure. Uh hello everyone. The EIP insight team would like to demo a few new features we have been working on. These are designed to improve visibility into standards processes and make contributors easy uh contributions easier for authors and editors. So I would like to share my screen uh share just Hello. Is my screen visible? Hello.

>> No, it's not. >> Yeah. Just >> Mhm. If you would want I can share the screen as well but you may have to navigate or you can give it another try. >> Just uh let let I guess I don't have if you can't share the screen I don't know what's I would love. Yeah.

Okay. Um, can you go to analytics page? Okay. Okay. First, uh, okay. Um, we'll start with the PR labels distribution dashboard. Um this shows a uh this shows a bar graph of pull requests across the EIP, ERC's and RIPS repositories. You can filter it by uh repo. Toggle between custom governance such as uh c uh such as EIP update, type of fixes, status changes,

created bot and also get uh GitHub labels such as author review, editor review. uh you can filter it also and uh the filter by GitHub labels or uh other governance labels too and there's also an option to export the data CSV for offline analysis these this was one of do this type of fix and type of fixes PRs that we are

receiving these days. If we take a look at like what was there in early January this year, somewhere around 24 fixes and today is 17. >> So next is the proposal builder. This tool allows contributors is provided by EIPW. Uh it comes with live markdown preview.

Uh you can also search an EIP and if you want to uh validate any EIP you want uh simple uh or any validated uh we go and validate it. Yeah. And if you remove any field Mhm. Click on Y.

I just want to whether these are still validated even though when they discuss >> that's what I'm expecting. Nice. Um >> so this also has uh our uh markdown llinter so it will also give all the broken links. It'll it also has validation checkers and catch missing or invalid fields and once validated you can copy the markdown directly from submission on GitHub.

Yeah, >> quick question. Yes, I don't imagine that this discussion to link should be null here. Mhm. >> So, you may want to take a look at it. Oh, it is null. So, the tool is working well. Maybe it is not added here or maybe we can look into the raw file of it. So you may want to go back and check if there is discussion to link available for ERC20.

I I don't find it in EIPS inside and that may be the reason why it is throwing so many error because uh the >> the first thing uh I noticed was like they have missing discussion to must be a valid URL and there are so other uh issues we can perhaps get into detail like why is it not validating but yeah that's a good catch. >> All right. Um >> yes. >> Do you want to move somewhere else? We gone. Yeah. Uh insight.

We will go to August insights. Check to check the third feature. Uh so it has the third feature is the submission trends dashboard. It provides a dynamic chart uh tracking the flow of draft versus final EIPS. Uh you can also break down break it down by type or category giving a clear picture of how proposals are progressing over time. We have both step status view and category view over time. >> Nice.

>> Any views? >> All right. So the last inunda was uh our monthly insights which we which we shared in honor Twitter Twitter earlier this month reflecting the study throughput on healthy momentum on Ethereum standard development can show that Twitter uh >> yeah sure >> very three months.

>> Thank you so much Danosha. I wonder if anyone has any question or any other improvement suggestion. So if they have improvement suggestion where they can go or feedback about fixing anything >> uh can add an issues or maybe yeah >> GitHub repo. Okay. Yeah. >> Yeah. GitHub repo. >> I'm noticing that GitHub repo is already added on almost every page. So people can add an issue there. >> Yeah. Yeah. >> That is good. Thank you so much.

>> Mhm. >> All right. Uh the next one unless anyone has any question comment. Okay. So the next one here is uh oh sorry the link is missing EIP editing office hour. So the next EIP editing office hour is scheduled for Tuesday August 26 with Sam Wilson. It would be for EIP and ERC both uh reviews and uh I have opened the calendar for other editors to fill in for the future editing office hours. Please feel free to respond on the editor's channel if you have an opening and you would like

to take the next editing office hours. With that we have almost covered what was there in the agenda but I want to discuss one big thing which I want to I think I have already shared with editors but I would like to hear uh from people who are present. How much value add do we see in continuing this meeting and do we want to continue or u do we think that we can we have reached to a place where we are organized and perhaps can address issues through the discord channel itself.

I mean it is important that u we we need to address these issues but there are ways I was just trying to see. Okay. Okay. So uh I was just trying to see what EIP editors um think about continuing this EIP IP meeting. We did very good in addressing issues. Now from bi-weekly meeting we have moved to once a month meeting. I'm curious do people see value in continuing the meeting once a month or do we want to give it a rest and address most of the issues via

Discord communication? I mean, if we're doing less than once a month meetings, I mean, what's even the point of having EIPs? Like, there must be stuff for us to talk about. Um, but that said, like all of the stuff that came up today is stuff we could have done on Discord, like pretty painlessly. So um yeah, I mean, I guess I'm good getting rid of it and just having u meetings if we need them. And I also feel like some of the issues can be handled uh uh in office hour because now we are getting more PRs where authors are trying to understand how things work. We have less things to work on process side. So we can we can

yeah maybe move it to discord and see if there is a strong need demand coming from all editors that we need to be on the same page. We need to get back to EIP meeting and then we can bring it back. >> Works for me. >> Yeah, thank you Victor. I think Victor is open to participate with monthly cadence. Um but the main idea of having this EIP meeting is to have all editors in the room. We have been seeing less presence of editors in this monthly meeting.

Maybe they forget about this meeting or something, but they are definitely more active on Discord and we are planning editing office hour for the community. So yeah, that that makes sense. Okay, I can perhaps make a vote uh in the discord channel so people can respond to it and based on that we can make any decision. If the decision will be in favor of continuing the meeting then we would meet on third Wednesday of the month of the next month. Um at 1400 is our regular timing. Today it was requested to delay it by an hour so we moved it.

Uh but we will provide the exact date and information in the discord channel if we get voting for continuing this. We do use Google calendar. That is correct. We are using Ethereum protocol calendar to uh let people know that this meeting is happening. So yeah. Okay. So people are saying that shifting hour is hard. Yeah, I get that part. Okay. Specific people. Okay.

Cool. So yeah, I think that is all for today. If there is anything that people would like to share. >> Uh nothing for my end. Thanks for hosting Puja. >> My pleasure. Thank you everyone for joining us here today. See you all around. Have a great rest of the day. [Music] Hey,

[Music] hold on. [Music] Heat. Heat.

[Music] Hey, [Music] hey hey. [Music]