Skip to content
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

EIPIP Meeting 10 Agenda #19

Closed
poojaranjan opened this issue Jun 5, 2020 · 5 comments
Closed

EIPIP Meeting 10 Agenda #19

poojaranjan opened this issue Jun 5, 2020 · 5 comments

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Jun 5, 2020

Date

June 17, 2020, at 15:00 UTC

Location

Zoom: The link will be shared in the telegram group.
YouTube Live Stream/Recording Link

Agenda

  1. An EIP number registry process.
  2. Separation of EIP process and hard-fork coordination
  3. EIPIP roadmap
  4. ZIPs reference
    • Keywords
  5. How to deal with non-normative edits to existing EIPs, ensure the responsiveness of editors on actually merging PRs and split EIPs into multiple repositories.
  6. Discuss the EIP-1 Brainstorming Document.
    • Goals Outcomes
    • What we are not doing.
    • EIPs TODO
  7. Clarifications for how a precompile address is decided.
  8. Review action items from previous meeting

Next Call - July 1, 2020.

@poojaranjan
Copy link
Member Author

  1. An EIP number registry process.

Feedback by @gcolvin at Gitter.

@poojaranjan
Copy link
Member Author

  1. Separation of EIP process and hard-fork coordination

A suggestion from @scherrey at Gitter.

"I'll toss out the term "InProgress" as an alternative to "Active/Living" as a potential clarifying submission."

@MicahZoltu
Copy link

MicahZoltu commented Jun 6, 2020

Requested Agenda Items:

  1. How to deal with non-normative edits (clarifications, wording improvements, etc.) to existing EIPs when the authors are non-responsive. Examples: Adds clarifying text to the EIP-155 specification. ethereum/EIPs#2272 Changes reference to sha3 to keccak256. ethereum/EIPs#2316
  2. How can we improve responsiveness of editors on actually merging PRs (like initial draft merge and move to final). Example: Moving EIP-600 to last call. ethereum/EIPs#2072 Moves EIP 601 to Last Call. ethereum/EIPs#2073
  3. Split EIPs into multiple repositories. As a reviewer, I don't want to see/review ERCs but I do want to see/review Core EIPs. A protocol dev may not want to see/review Interface EIPs. By splitting Core, Interface, and ERC EIPs into separate repositories people can subscribe to one or more rather than having to drink the entire firehose of EIPs or simply check out. Sadly, I have opted to "check out" because the thousands of ERCs became too much spam in my inbox, but I am finding I'm missing out on a lot of discussions re: Core and Interface EIPs.

@poojaranjan
Copy link
Member Author

Requested Agenda Items:

@MicahZoltu items added to the agenda.

@poojaranjan
Copy link
Member Author

Closing in favor of #21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants