-
Notifications
You must be signed in to change notification settings - Fork 37
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 60 Agenda #153
Comments
Closed
I'd like to add to agenda: |
Would like to add: ethereum/EIPs#5223 |
@anettrolikova @Pandapip1 items added to agenda. |
Proposed discussion EIP template for FEM forum |
Closing in favor of #161 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Date and Time
Wednesday, July 13, 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
0. Travis CI issue. A proposal to migrate to GitHub Actions.
1. Regarding old EIPs that don't conform to current standards. Ref discussion
2. Moving proposal in absence of author. Ref: Comment
3. The future of EIP process after the merge Ref: Comment
4. From GitHub Issue
a. Include a copy of RFC 822 and RFC 2119 in EIP-1's assets folder Ref: Issue
b. EIP-4907 has inconsistencies with Requires (EIP-721), can it be updated? Ref: #156
c. Reference implementations aren't linted prior check-in or when marked as final. Ref: #157
5. License for a reference implementation discussion
6. Past meeting discussion continued
a. One-time NFT Sale of unused EIP numbers Ref: Issue
b. Clarify how to use "ERC" vs. "EIP" to refer to different EIPs
c. Meta EIP for the Executable Spec process for Core EIPs
7. EIPs Insight - Monthly EIPs status reporting.
8. EIP editor apprenticeship meeting
9. EIP bots related discussion, updates, agreement on merging PRs & closing Issues.
10. Review action items from the previous meeting
Next meeting - July 27, 2022
(Anything else, please add a comment)
The text was updated successfully, but these errors were encountered: