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 59 Agenda #152

Closed
poojaranjan opened this issue Jun 29, 2022 · 2 comments
Closed

EIPIP Meeting 59 Agenda #152

poojaranjan opened this issue Jun 29, 2022 · 2 comments

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Jun 29, 2022

Date and Time

Wednesday, June 29, 2022, 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. Clarify how to use "ERC" vs. "EIP" to refer to different EIPs Ref: Comment

2. Meta EIP for the Executable Spec process for Core EIPs

3. EIP bots related discussion, updates, agreement on merging PRs & closing Issues.

4. EIPs Insight - Monthly EIPs status reporting.

5. EIP editor apprenticeship meeting

6. Review action items from the previous meeting

  • Contributor's permission to EIP GitHub repo for Sam Wilson
  • Pooja will collect feedback regarding one time NFT sale of unused EIP numbers.
  • Sam Wilson and Tim Beiko will create a Meta EIP for the Executable Spec process before showing the proposal to the core devs
  • Remaining EIP editors to give their view on using the executable spec in the EIP process

Next meeting - July 13, 2022

(Anything else, please add a comment)

@SamWilsn
Copy link
Collaborator

Contributor's permission to EIP GitHub repo for Sam Wilson

With great power comes great responsibility, and I want neither.

@poojaranjan
Copy link
Member Author

Closing in favor of #153

This issue was closed.
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