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 42 Agenda #87

Closed
poojaranjan opened this issue Sep 22, 2021 · 1 comment
Closed

EIPIP Meeting 42 Agenda #87

poojaranjan opened this issue Sep 22, 2021 · 1 comment

Comments

@poojaranjan
Copy link
Member

poojaranjan commented Sep 22, 2021

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-bot

  • Guidelines to change the status from "Stagnant"
    • could it be the last status from which it moved to "Stagnant" or it has to be either "Draft" or "Review"?
    • if the author makes a PR to change the status, would it require editors' permission?
    • if moving the proposal is impossible for any reason. eg. EIP-3403: Partial removal of refunds
    • if moving proposal is a necessity but EIP author(s) or champion isn't actively involved?

4.. 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

  • Updating the EIP editors list

(Anything else, please add a comment)

@poojaranjan
Copy link
Member Author

Summary on guidelines to change the status from "Stagnant":

could it be the last status from which it moved to "Stagnant" or it has to be either "Draft" or "Review"?

It's up to the author starting from Draft but it could be the original status from where it was moved to Stagnant.

if the author makes a PR to change the status, would it require editors' permission?

The pull request by the author should be auto merged. eip-bot will enable auto-merge for such PRs.

if moving the proposal is impossible for any reason. eg. EIP-3403: Partial removal of refunds

Let it sit in Stagnant forever. EIP-1 be updated to make the Stagnant an alternate "terminal" status.

if moving proposal is a necessity but EIP author(s) or champion isn't actively involved?

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 Final status.

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

1 participant