-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Proposals to close EIP Discussion Issues #5127
Comments
I'll keep track of the relevant issues here. Isn't a discussion-to link (either just a proposal with no EIP, or the discussion-to was migrated):
Final EIPs:
Withdrawn EIPs :
Stagnant EIPs:
Last Call:
Draft EIPs:
Review EIPs:
|
I am weakly in favor of no. 1. I think that attaching a link to the (closed) GitHub issue is sufficient to continue the discussion. I propose that to avoid EIP editor work, it should be the responsibility of the EIP authors to migrate the links. However, I can see how this might be inconvenient, so if it could be determined that the inconvenience of migrating the discussion link is greater than the inconvenience/confusion caused by the presence of the issues, I am weakly in favor of no. 2, as the discussions-to links aren't even up to date. Most discussion-to links aren't marked as such (and #4431 is marked as discussions-to despite the real discussions-to link being migrated to Ethereum magicians). However, I am weakly against the stale bot in general. I feel that every issue should be manually determined to be stale (and if the number of issues moves down to one page when no. 3 is implemented, this is very feasible). I am strongly in favor of no. 3. Closing Final and Withdrawn EIPs is a no-brainer; they aren't going to be changed, so there's no discussion to be had. All discussion should be for a new EIP that fixes/improves the older one. Stagnant EIPs should also be closed, as the links can always be re-opened if/when said EIP moves out of stagnant. |
Inviting EIP editors to weigh in |
I suspect that (3) will likely be the least contentious and so I suggest we focus on that in the short term. Migrating from GitHub to Ethereum Magicians is unlikely to go smoothly. Some discussions-to links have a lot of discussion, and just copy/pasting that into the body of a single message will make it much harder to read and link compared to current discussions. The common case is that an issue receives a lot of discussion while it is actively being edited, but that eventually dies out. I think if we simply close those issues (via (2) or (3)) the negative effects of this problem will go away and we won't have to do a bunch of work. |
In strong favour of 3., writing bot and solving for that is just extra work and it can be rather quickly done manually! Since @Pandapip1 has already created a list to start with, we can focus on that and find the rest async and keep updating the list here in the comments itself. Wdyt? |
I would like to get additional feedback from other editors before moving forward with 3, but so far it does seem like the popular choice. |
3 is fine by me. The author can re-open if need be. |
3 is also fine with me. |
I have closed the discussions-to for the Stagnant and Final EIPs listed by @Pandapip1. |
While you're at it, you should close all the issues in the first list, as they aren't discussion-to links. |
I would also like to add another option:
|
Done. |
I'm good with 2) and 3). |
I think the consensus is 3? |
I believe we have completed (3) at this point. There will be stragglers over time as grandfathered EIPs enter final/stagnant/withdrawn but there should be relatively few at this point. Do you feel this issue is resolved enough to warrant closing it @Pandapip1? |
Sure. I'm not sure if there is consensus over (1) and (2), but manual closings should be fine. |
Closing as per rough consensus in favor of option 3. |
In the EIPIP meeting 57, the group briefly discussed options for closing EIP discussions open Issues.
Please respond with your recommendation to design a bot or take manual actions accordingly.
Final
,Stagnant
,Withdrawn
statusThe text was updated successfully, but these errors were encountered: