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 90 #271

Closed
7 tasks
poojaranjan opened this issue Sep 6, 2023 · 2 comments
Closed
7 tasks

EIPIP Meeting 90 #271

poojaranjan opened this issue Sep 6, 2023 · 2 comments

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Sep 6, 2023

Date and Time

Sep 20, 2023 at 14:00 UTC

Location

Zoom: TBA in the Discord #eip-editing channel

YouTube Live Stream/Recording: https://www.youtube.com/playlist?list=PL4cwHXAawZxpLrRIkDlBjDUUrGgF91pQw

Agenda

1. Discuss Open Issues/PRs, and other topics

Changes to Final proposals

None

2. Discussion continued or updates from past meetings

3. EIPs Insight - Monthly EIPs status reporting.

4. EIP Editing Office Hour

5. Review action items from earlier meetings

@poojaranjan
Copy link
Member Author

Summary

1. Discuss Open Issues/PRs, and other topics

ethereum/EIPs#7665 & #272

  • Most of the EIPEditors agreed to let live "Networking" & "Interface" EIPs as is and deprecate categories. It means Do NOT merge them to the list of "Core" EIPs. The PR was made by @Pandapip1, who unfortunately could not make it to the meeting.
  • @lightclient mentioned that it would be good to focus on the working group "Core" as "Core" is defined today. If in the future we receive "Interface" and "Networking" categories EIP, will consider a working group.
  • I proposed to deprecate the "Standard Track" Type and regroup "Categories - Core, ERC" as "Type". eg instead of Standard Track - Core, it will be Core. No opposition. @SamWilsn mentioned it will be easier to form different working groups on this.
  • Decision: We will wait till October 5th to make a final decision on PR-7665.

Call for Input (Multiple items) Ref:EIPIP Issues

  • @SamWilsn explained the process for Call For Input.
  • We can talk about decision items in the following EIPIP meetings.

2. Discussion continued or updates from past meetings

EIP-5069's new charter stuff.

  • Follow the proposal to learn about EIP Editors' working process.

Consider adopting a Community Specification License terms for the new ERC repo ethereum/EIPs#7482 - Anyone has any update to share? #260

  • Update from @xinbenlv "copyright license for ERCRef repo : thinking of CC0 + Apache2.0 dual license"

ethereum/EIPs#7550 - Good to merge the PR?

  • PR is good to be merged.

EIP-ERC GitHub repositories Ref. EIP-7329

  • Matt's PR needs to be rerun before merging.
  • @SamWilsn will send an invite to @lightclient, @Pandapip1 and others to work this through
  • Updates will be provided in the next meeting.

ethereum/EIPs#7230

  • @gcolvin some of my concerns are being addressed. Changes are happening in pieces in other places.
  • Decision: PR-7230 will be closed.

3. EIPs Insight - Monthly EIPs status reporting.

Check the report for details -
Hackmd
EIPsInsight.com

4. EIP Editing Office Hour

@gcolvin suggested rewording the exit process for EIP editors in EIP-5069. @SamWilsn will look into it.

@poojaranjan poojaranjan mentioned this issue Sep 20, 2023
8 tasks
@poojaranjan
Copy link
Member Author

CLosing in favor of #278

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

1 participant