AI Generated Meeting summary
Quick recap
The EIPIP Meeting 129 covered updates on open call for inputs, including the approval status of allowing links to Unicode standards and strict rules for changing EIP authors. The group discussed the implications of changing author permissions and the importance of protecting EIP numbers, with Sam and jochem-brouwer exchanging views on potential conflicts and process improvements. They reviewed changes to contributing.md to clarify EIP number allocation and prevent self-allocation by authors. The meeting addressed issues with Meta EIP 7773 being blocked due to unrelated changes, such as the addition of a mascot EIP, and the need for better process alignment between ACD and EIP editors. Updates on the Rust implementation of the rendering system and EIP numbering automation were shared, with limited progress reported. Pooja announced plans for an EIP Hub at DevCon and invited programming partners. The next meeting was scheduled for September 16.
Next steps
Pooja
- Bring up the issue of the mascot EIP blocking the Meta EIP in the next AllCoreDevs (ACD) meeting and discuss the process for including such changes.
- Reach out to potential programming partners for the EIP Hub at DevCon and coordinate with editors planning to attend.
Sam
- Fix the conflict and force merge the CFI for allowing links to the Unicode technical standard.
jochem-brouwer
- Propose and create a pull request to update agents.md to include a note that AI/LLMs should not allocate EIP numbers.
- Take a look at the Rust implementation of the rendering system for the EIP working group.
Summary
Call for Inputs Approval Discussion
The team discussed several call for inputs (CFIs) pending approval, including allowing links to Unicode standards and associating EIP editors. Jochem identified a conflict in the Unicode CFI that required resolution, and Sam agreed to handle the forced merge since additional approvals were unlikely. The meeting also covered a CFI regarding strict rules for changing authors, with Pooja sharing details about the August 15th deadline.
EIP Author List Protection Proposal
Jochem-Brouwer proposed a rule preventing office members from changing author lists to avoid potential conflicts and taking EIPs hostage. Sam expressed concerns about the potential for conflicts in edge cases, particularly around EIP number ownership and compromised accounts. Both participants acknowledged the importance of protecting EIP numbers while considering the implications of their proposed changes.
Community Decision Waiting Period Discussion
The team discussed implementing a waiting period for community decisions, where members would have time to object to removals before they are finalized. Pooja suggested continuing the discussion on Discord to gather more editor feedback before making a decision on how to proceed with the current review process.
EIP Bot Status Updates
The team discussed the status of a bot that checks for references to non-final EIPs and ERCs. Sam confirmed he had re-enabled the pull requests, though he hadn’t tested if they were working properly. Pooja mentioned she had received a flag on a recent EIP, indicating the bot was now functioning on both the EIP and ERC repositories. The discussion then moved to updates on PR merge policies for active EIPs, where Pooja outlined three major changes she had made to the contributing documentation, including moving don’ts to a separate section and adding guidance about EIP number allocation responsibilities.
EIP Number Allocation Process Protection
The team discussed protecting EIP number allocation processes, with Jochem expressing concern about preventing unauthorized number assignments and Sam agreeing to add clarifications to the EIP template and pull request template. Pooja noted that contributing.md should include information about editor responsibilities for EIP number allocation, which requires two reviewer approvals to implement. The discussion was interrupted by a GitHub outage preventing pull requests, and Pooja mentioned waiting for an author’s approval to move EIP 7773 to review status while noting a related EIP bot check issue.
MetaEIP Process and Mascot Concerns
The team discussed concerns about the inclusion of mascots in the MetaEIP process, with Pooja highlighting that changes were made without proper documentation or approval. Jochem-brouwer advised against creating additional MetaEIPs as it would involve the team in governance processes beyond their scope. Sam expressed neutrality about continuing the Rust implementation of the rendering system project due to lack of editor support, and the team noted that no one is actively working on automating EIP numbering since the protocol support team transition. The conversation ended with an announcement about a proposed EIP Hub at DevCon, seeking programming partners for different themed days, and the next meeting was scheduled for September 16th at 1600 UTC.