New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP: ERC/EIP Repository split #7329
Conversation
An EIP giving motivation, rational, alternatives, and objections to the EIP/ERC split proposal.
✅ All reviewers have approved. |
The commit f9dffa9 (as a parent of f3bf83e) contains errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kudos for the structure and the great summary of the current pain points of which we spoke during the last office hour meeting. Nothing to add, except that maybe stack might be replaced by chain/ecosystem (line 23, line 28, etc.)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text in this PR satisfied the requirement to be merged as a Draft status
There was a problem hiding this 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...
title: ERC/EIP Repository split | ||
description: Split the ERC specifications out of the EIP repository into a new repository, so that only core protocol EIPs remain | ||
author: Lightclient (@lightclient), Danno Ferrin (@shemnon) | ||
discussions-to: https://ethereum-magicians.org/t/eip-erc-repo-split/15053 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional: feel free to consider use existing EIP/ERC split FEM thread https://ethereum-magicians.org/t/proposal-forking-ercs-from-eips-repository/12804
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That didn't show up on my searches. Thanks.
This is merging to “draft”, doesn’t mean it is being adopted.
I personally still hold my reservation of the content of the proposal, but
I think procedure-wise, the text satisfy to be publish as an EIP Draft.
IIIUC, An Meta EIP being proposed and published as Draft or Review does not
mean it being adopted.
Only moving to Final means the adoption of the proposed EIP, which is what
you (@gcolvin) are blocking.
Since I am objecting the proposal, I feel that it’s more appropriate for me to approve it to publish as a draft to show to friendly collaborative spirit in this debate.
…On Sat, Jul 15, 2023 at 08:22 Greg Colvin ***@***.***> wrote:
This got merged despite my block? Or am I misunderstanding?
—
Reply to this email directly, view it on GitHub
<#7329 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE4KRMH7SURY7EE63F4UPLXQKYUVANCNFSM6AAAAAA2JZW754>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
5. Create a unified document for editors to assign EIP/ERC numbers. EIPs and | ||
ERCs will no longer be based on an initial PR number but on a number | ||
incremented by the EIP editors of their respective repositories. EIPs will be | ||
assigned even numbers and ERCs will be assigned odd numbers. The exact |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: need to continue this sentence
An EIP giving motivation, rational, alternatives, and objections to the EIP/ERC split proposal.