Skip to content

Conversation

@lightclient
Copy link
Member

The biggest complaint I hear about the EIP process is how slow it can be to move through the process, get editor attention, etc. It would be great to bring more contributors into the fold, but as it stands today, EIP editors are in a very high trust position. We are tasked with governing the EIP process in a way that is effective and sustainable for the long term. Although we now have a better forcing function with Keeper, I still think adding more full EIP editors is not something we should do lightly.

With that said, I still want to address the timeliness of the EIP process and that's where I think Associate EIP Editors can come in. They will have the same powers and responsibilities that EIP Editors have for executing the day-to-day processes. They just won't be eligible for formally voting on governance matters. I think this strikes a good balance between opening up editing to allow for more contributors without putting the process in unnecessary risk.

@lightclient lightclient requested a review from eth-bot as a code owner January 6, 2026 19:38
@github-actions github-actions bot added c-update Modifies an existing proposal t-process labels Jan 6, 2026
@eth-bot
Copy link
Collaborator

eth-bot commented Jan 6, 2026

✅ All reviewers have approved.

@eth-bot eth-bot changed the title 5069: add concept of associate editors Update EIP-5069: add concept of associate editors Jan 6, 2026
@eth-bot eth-bot enabled auto-merge (squash) January 6, 2026 19:39
Copy link
Collaborator

@eth-bot eth-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Reviewers Have Approved; Performing Automatic Merge...

@abcoathup
Copy link
Contributor

@poojaranjan gave me the title of associate editor that I have been using when assigning numbers.
(I've assigned 2/3 of numbers since the EIP/ERC split).

Do I need a new title or do I need to become an associate editor if I want to keep assigning numbers?
Ideally I don't want to assign numbers but I want it done quickly, and the quickest way is to do it myself (until it is automated away).

@poojaranjan
Copy link
Contributor

Adding more people to support the process is a good idea. While we cannot avoid onboarding new EIP editors over time, I agree that a high level of trust is essential before bringing someone in. We can update an onboarding process to share with the community in the “Membership” section in EIP-5069.

In January 2025, the concept of an "EIP Reviewer" was introduced with a similar goal, but with greater emphasis on subject-matter expertise, keeping them more aligned to the Ethereum ecosystem. While EIP editors focus primarily on editorial consistency and process enforcement, EIP Reviewers can also contribute technical or domain expertise to add value. Notably, we have successfully onboarded an EIP editor using this pathway.

We have now completed a full cycle from contributing as EIP Reviewers to EIP editor. I would support documenting this well-tested and proven in practice process within EIP-5069, rather than introducing a new mechanism altogether.

I would also prefer to keep the “Associate EIP Editor” role unchanged to avoid confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c-update Modifies an existing proposal t-process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants