AI generated summary
Quick recap
The Ethereum Improvement Proposal (EIP) editors’ meeting focused on addressing various issues and updates related to the EIP process. Editors discussed several call-for-input topics, including updates to the EIP website’s citation system and the status of informational EIPs. They also addressed concerns about overwhelming GitHub notifications for editors and explored potential solutions, such as adjusting the bot’s behavior or creating AI agents to assist with reviewing low-hanging fruit. The team reviewed updates on PRs for LTA review and consensus, as well as the need for a collection of EIP documentation formats for test cases and reference implementations. Dhanush from the EIPS Insight team presented new board sections and contributor analysis pages, which received positive feedback from the editors. The conversation ended with a review of February’s EIP insights and a discussion about identifying external contributors to upgrades.
Next steps
- All EIP editors: Review and provide input on the PR regarding status tag in citation (whether to show status for all except living/final, or only for living/final), and add comments to reach consensus.
- All EIP editors: Review and comment on the informational EIP status discussion (final vs living) and add input so the PR can be closed as needed.
- Sam: Add the decision and close the overdue informational EIP status discussion PR after sufficient editor input is received.
- All EIP editors: Review the outstanding PRs (including those with typos and those where authors have requested closure) and close or merge as appropriate.
- Pooja: Reach out to Zainan on Discord to involve him in the discussion/thread about reference implementation and test case documentation for contributors.
- All EIP editors: Sign up for upcoming office hour slots (March 3rd and 10th) if available.
- Dhanush (EIPS Insight team): Investigate and implement tracking/reporting of the number of EIP authors outside the client development team whose proposals are included in upgrades, potentially with assistance from Pooja in identifying non-client-team authors.
- All EIP editors: Review and provide feedback on the new “boards new” section, and decide if it should become the main board, replacing the old one.
- All EIP editors: Take a look at all open “call for input” items so they can be closed on time (as requested at meeting close).
Summary
EIP Editors Meeting Welcome Session
The EIP meeting began with Pooja welcoming attendees and introducing the agenda, which included call for inputs, editor discussions, and previous meeting topics, along with an EIP insight for the month. Pooja noted the presence of various editors, including Johan and Joachim, and mentioned that she had reached out to other editors to confirm their attendance. The meeting was set to start after a brief delay to allow for additional editors to join.
EIP Pull Requests and Reviews
The team discussed several pull requests and calls for input related to EIPs. Sam mentioned two pull requests regarding Unicode technical standards that need approval. Pooja explained a PR to fix a bug with citation status displays, which was reviewed by Kachandar Singh. The team is seeking editor input on whether the citation status should be shown for all EIPs except living and final, or only for those. They also discussed an informational EIP’s status, with some editor responses received but more desired.
EIP Proposal Status Updates
The team discussed the status of EIP proposals, with Sam advocating for final status for external documents while allowing living status for internal governance documents where authors can be involved in updates. Pooja noted that Proposal 6953, which documents historical upgrade activation triggers, had reached final status. The team agreed to move forward with closing the proposal as final, with Sam offering to add the decision. They also briefly touched on the issue of overwhelming GitHub notifications for EIP and ERC repositories, with Pooja mentioning she had picked it up that morning.
EIP Bot Notification System Issues
The team discussed issues with the EIP bot’s notification system, where editors were receiving overwhelming mentions on GitHub. Sam suggested removing editor usernames from the bot to reduce notifications, while Pooja proposed adjusting the bot to notify editors only when PRs are ready for review, rather than immediately. They also addressed a bug in the bot’s architecture that prevented proper EIP identification, and discussed several PRs that needed editor review, including one that could be closed as per the author’s request.
AI Editors and Documentation Review
The team discussed the potential implementation of AI agents to assist editors in reviewing and closing PRs, with Pooja proposing a reviewer agent that could automatically close PRs with minor issues like typos. They also considered adding bots with limited permissions to help editors manage their workload. The group acknowledged that while bots could be helpful, they should not replace human editors. Finally, they discussed the need for a collection of EIP documentation formats for test cases and reference implementations, noting that a contributing.md file had recently been added but this specific documentation was still missing.
EIP Documentation Guidelines Discussion
The team discussed creating documentation guidelines for EIP contributors, with Pooja suggesting a new section in the contributing documentation for implementation references and test cases. Zainan expressed interest in being involved with sharing reference implementations and requested to be notified of relevant discussions. Pooja also mentioned the need for more editors to sign up for office hours on March 3rd and 10th, and encouraged editors to add themselves to a signup document.
EIPS Board and Contributor Updates
Dhanush from the EIPS Insight team presented updates on a new board section and contributor analysis pages. The new board section uses content filters to distribute open PRs for editor review, including filters for EIP status changes and PR priorities based on last reviewable action. The contributor analysis pages show detailed activity timelines, repository breakdowns, and rankings for all contributors, with updates every 6-7 hours. Pooja suggested that editors might switch to using the new board section as the main board, replacing the old one.
EIP and ERC Status Review
Dhanush presented February’s EIP and ERC status, noting 10 draft EIPs, 3 ERCs on review, and 3 in final status. Pooja inquired about tracking EIP authors outside client development teams, and Dhanush agreed to investigate this. The conversation ended with a reminder for editors to review open calls for input and for participants to sign up for the next office hour.