-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
EIP-1: Stronger rules for discussion-url #2967
Comments
I have wondered this myself on many occasions. I would support a change that makes the discussion URL go away at final. This would be similar to RFCs where the final RFC doesn't include a link to historical discussions. If people really wanted to find the historical discussion, they can dig through git history so it isn't like we are purging it from the internet. This policy would also, importantly, let us eventually close GitHub issue discussions so we don't have an ever growing list of open issues. |
I am in favor of this also. However, my preference would be to disallow |
@axic and @MicahZoltu were asking: “what is the goal of the discussion url?” This should be obvious, and is already partially stated in EIP 1: “The EIP author is responsible for building consensus within the community and documenting dissenting opinions.” FYI all this and so much more can be rigorously done with the canonizer.com dynamic petition system. |
Consensus building is separate from the EIP process (it is part of the hard fork coordination process), so I don't think that alone is a good reason to keep the discussions-to URL around, especially after the EIP is final. |
@MicahZoltu So you are saying the current statement "The EIP author is responsible for building consensus withing the community and document dissenting opinions" isn't relevant to the EIP process? |
IMO, Fellowship of Ethereum Magicians is one of the best places for discussing any proposal. I suppose this is already a recommendation and in one of the EIPIP meetings, the group agreed to make it more than a recommendation and push it as a good practice for future proposals. I have been suggesting authors (of new proposals) to create a doscussion thread at FEM in PEEPanEIP. |
The Magician's is highly encouraged, but I think authors should be able to point anywhere they like that is publicly accessible. If the URL goes dead it is the author's problem, as champion. The EIP itself should stand on its own. |
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
Still an unsolved question. |
The effective rule at the moment I believe is that discussions-to url should be |
#5340 is a revisit of this question |
This is sparked by EIP-1046 and EIP-1047 linking to reddit threads:
Both of those now display this:
That means their discussion urls are read-only, which defeats the purpose.
I do not have a clear proposal here, but only a conversation starter. Likely allowing the following makes the most sense based on past experience:
https://github.com/ethereum/EIPs/issues/*
https://ethereum-magicians.org/*
https://ethresear.ch/*
The other currently used URLs are:
t.me
(telegram)https://discuss.ens.domains/t/new-standard-proposal-ens-multicoin-support/1148
https://gitter.im/ethereum/topics/topic/5ac4d974109bb043328911ce/eip-969-discussion
https://gitter.im/ethereum/EIPs
https://gitter.im/ethereum/AllCoreDevs
github.com/<username>/issues/<n>
We already disallow
https://github.com/ethereum/EIPs/pull/*
(as an archaic decision), we could perhaps just disallow reddit as well?Probably we need to ask the question here: what is the goal of the discussion url? Is it for ephemeral discussions only? Is it something which is important after something becomes Final? If so, should it be removed after it became Final?
The text was updated successfully, but these errors were encountered: