-
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 42 Agenda #87
Comments
Summary on guidelines to change the status from "Stagnant":
It's up to the author starting from
The pull request by the author should be auto merged. eip-bot will enable auto-merge for such PRs.
Let it sit in
An EIP champion can be added to the proposal as co-author, it could be an 'EIP editor apprentice' or any community volunteer willing to work with the editors to push the proposal through. Alternatively, a new EIP with the same text of the earlier proposal and author as co-author(s) can be created to move the proposal to the |
Date and Time
Wednesday, Oct 20, 2021, at 15:00 UTC
Location
Zoom: TBA in the Discord #eip-editing channel
YouTube Live Stream/Recording: https://www.youtube.com/playlist?list=PL4cwHXAawZxpLrRIkDlBjDUUrGgF91pQw
Agenda
1. Post-merge will core cover execution and consensus, or do we plan to categorize EIPs based on what they touch? ref: Discord
2. Remove updated from EIP-1 Ref: Issue
3. Progress update on moving to
Stagnant
by bot. Ref: eip-bot4.. EIPs Insight - Monthly EIPs status reporting
5. The future of "EIP merge bot" - Is it safe to turn it down?
6. Admin access to EIP repo to EIP editors?
7. Review action items from the previous meetings
(Anything else, please add a comment)
The text was updated successfully, but these errors were encountered: