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 58 Agenda #146

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

EIPIP Meeting 58 Agenda #146

poojaranjan opened this issue Jun 15, 2022 · 2 comments

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Jun 15, 2022

Date and Time

Wednesday, June 15, 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

New EIP editor's announcement

1. PRs need discussion

2. EIPs Discussion-to place

  • Proposals to close EIP Discussion Issues Ref: Issue
  • FEM and /or EthResearch?

3. Core EIPs in an Executable Spec World Proposal

and Discussion

4. GitPoap badges

ECH GitPOAP is live.

5. EIPs GitHub permissions & support

  • Contributor's permission to EIP GitHub repo for Sam Wilson
  • Spamming issue Ref: Discord

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

6. EIPs Insight - Monthly EIPs status reporting.

7. EIP editor apprenticeship meeting

8. Review action items from the previous meeting

Next meeting - June 29, 2022

(Anything else, please add a comment)

@timbeiko
Copy link

Note to myself, mostly, but I'd like to clarify how we use "ERC" vs. "EIP" to refer to different EIPs

@MicahZoltu
Copy link

The short answer @timbeiko (we can discuss more on the call if you want) is that the EIP's repository uses EIP-#### everywhere, regardless of the type of EIP. Calling things ERC-#### is purely a colloquialism.

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