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 99 #310

Closed
3 tasks done
poojaranjan opened this issue Jan 18, 2024 · 8 comments
Closed
3 tasks done

EIPIP Meeting 99 #310

poojaranjan opened this issue Jan 18, 2024 · 8 comments

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Jan 18, 2024

Date and Time

Jan 31, 2024 at 17:30 UTC

Location

Zoom: TBA in the Discord #eip-editing channel

YouTube Recording: EIPIP Meetings

Agenda

1. EIP Process Standardization

  • RIP process documentation
  • Web Page Rendering to include EIPs, ERCs, RIPs

2. Discuss Open Issues/PRs, and other topics

Call for Input

Call For Input Status Result Comments
#306 Open Deadline Feb 07, 2024
#308 Open Deadline Feb 08, 2024

3. Other discussions continued or updates from past meetings

other proposals

4. EIPs Insight - Monthly EIPs status reporting.

5. EIP Editing Office Hour

  • Agenda [Meeting 31]

6. Review action items from earlier meetings

Next Meeting date & time

Feb 14, 2024 at 17:30 UTC

@poojaranjan poojaranjan mentioned this issue Jan 18, 2024
4 tasks
@vittominacori
Copy link

I wish this PR ethereum/ERCs#213 could be discussed as it is a simple return statement missing for no reason.

@tina1998612
Copy link

Hope to discuss ERC7007’s (AIGC token standard) new integration of opml in the next meeting. Thanks:)

@poojaranjan
Copy link
Member Author

@tina1998612

Generally, a PR related to a Final proposal is discussed in EIPIP meeting and ERC-7007 seems to be a new proposal. Could you tell me what you want to talk about?

@poojaranjan
Copy link
Member Author

Summary

1. EIP Process Standardization

RIP process documentation

  • No one from the RIP working group joined the call.
  • Juan Caballero got a chance to talk to the author of RIP-7212. The author is active in the community, but not part of the RIP working group.
  • The community may use some RIP process documentation.

Web Page Rendering to include EIPs, ERCs, RIPs

  • @SamWilsn updated that @Pandapip1 has stepped down from the EIP Editors role.
  • He further updated with a progress update on working group-based page rendering.
  • Still need a decision if this is the official way of page rendering
  • @SamWilsn mentioned that he had a chat with Ansgar and they seem pretty interested in seeing RIP as a working group rendering.
  • @gcolvin shared his support for the working group rendering.
  • Juan mentioned that Ullas (author of RIP-7212) at the time, didn't seem to know about the roles and responsibilities of the working group. People are already committing to other conversations.
  • He shared links to "what working group meant".
  • @SamWilsn shared a high-level overview of a working group. More can be found here and here
  • @gcolvin shared concerns over some of the existing policies like "external link policy"
  • @SamWilsn demoed the working group page

2. Discuss Open Issues/PRs, and other topics

ethereum/ERCs#213

Call for Input

#306
  • Deadline Feb 07, 2024
  • @g11tech it can become a spam vector or maybe an issue to allow a new EIP to say that it supersedes or updates a particular EIPs
  • Juan mentioned that there are multiple extensions of ERC-20 already.
  • @g11tech will hesitate to pop these links on ERC-20 page.
  • @SamWilsn suggested having a UI to showcase how the forward links will look like.
  • @poojaranjan thinks of proceeding with another proposal similar to ERC-233, to update the security vulnerability found in 1271 and educate the community about that. Updating a Final EIP may not be needed.
  • Lot of back-and-forth argument, no decision.
  • Editors please add your comments to come up with a decision by the end of the deadline.
#308
  • Final EIP where the existing author wants to add a new author.
  • @gcolvin perhaps the authorship wasn't acknowledged when it should have been, if so - errata
  • @g11tech thinks that EIP authorship is not a credit-giving system. The Final EIP does not require any further editing, so no need to update.
  • @gcolvin thinks it adds value to individual resumes. However, @g11tech thinks it may open a Pandora's box of such cases of updating authors later on.
  • No decision, editors may add their comments.

Call For Input #291 & #293 can be closed.

4. EIPs Insight - Monthly EIPs status reporting.

EIPsInsight.com
Hackmd

Next Meeting date & time

Feb 14, 2024 at 17:30 UTC

@vittominacori
Copy link

Hi @poojaranjan @SamWilsn @g11tech so will the ethereum/ERCs#213 be merged? Thanks.

@poojaranjan poojaranjan mentioned this issue Feb 7, 2024
5 tasks
@poojaranjan
Copy link
Member Author

Closing in favor of #312

@vittominacori
Copy link

vittominacori commented Feb 7, 2024

@poojaranjan sorry to bother you, I can't understand if that PR ethereum/ERCs#213 will be merged or not.

It says

PR can be merged at the end of the day.

but it is still open.

@poojaranjan
Copy link
Member Author

@vittominacori
There was no objection on the call for it to be merged. I have pinged EIP editors for the same on the EIP-editor channel on ECH Discord.

Aleneth added a commit that referenced this issue Feb 12, 2024
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

3 participants