Comments (8)
Should EIP discussion issues be closed when EIP is final?
I am in favor of having EIP related discussion on the Fellowship of Ethereum Magician and NOT in the EIP repo issue or elsewhere. Encouraging discussions at EthMagician will eventually become a standard practice, which will provide the flexibility to keep a discussion open even after the EIP is Final and the Pull request is closed.
However, for 'discussion issues' created so far, closing the issue should be helpful.
For some reason, if an author wants to keep the discussion open, he/she may open a discussion thread at Fellowship at Eth Magician and link it to the proposal.
from eipip.
Updated with Explicit arrows between States as decided on the call.
from eipip.
Should EIP discussion issues be closed when EIP is final? Author of EIP-2309 thought so, and while I have re-opened it since we historically have not done that I DO like the idea of closing discussion issues once an EIP is final.
from eipip.
Here are some things we can discuss this meeting:
- Should EIP authors create a reference implementation in a client as a requirement?
- Should a tagging system (maybe a header) be added to organize EIPs?
- Should EIPs include a list of use cases?
- Should EIPs include a list of pros and cons?
from eipip.
To get a jump start on things by sharing my thoughts on the above:
Should EIP authors create a reference implementation in a client as a requirement?
No, while reference implementations are useful for a spec, and encouraged as part of the specification process as it can help tease out subtleties, I don't think it is a requirement for a pure technical specification to be valid and complete.
What is a "tagging header"?
While I definitely think that people should have use cases for their EIPs and mentioning them in the motivation seems prudent, I don't think it is a requirement for something to be technically valid.
I'm not a fan of PROs/CONs. Motivation section may include some reasons why someone should implement the EIP somewhere, and the security considerations may include gotchas to look out for, but I don't think EIPs are the right place to argue in favor/against an EIP.
from eipip.
On the network upgrade process, I'd like to revisit the Pull Request (which is updated with the Eth1.0-spec repo) and EthMagician to understand the next step for the documentation/proposal.
Also, discuss how the EIP process and the network upgrade process can be linked together. I picture it like this 👇
The above core EIP process is also proposed here.
from eipip.
@axic's EIP overhaul document doesn't seem to be up to speed with opinions from the EIPIP meeting (not to say he has to be aware or even agree with whatever decisions come from the meeting, but it would be nice to all get on the same page).
https://hackmd.io/@axic/eip-overhaul
from eipip.
Closing in favor of #34
from eipip.
Related Issues (20)
- EIP Editing Office Hour Meeting 33 HOT 4
- Call for Input: Allow Links to CAIP HOT 6
- Call for Input: Update ERC-6492 (Final) Reference Implementation HOT 7
- EIP Editing Office Hour Meeting 34 HOT 6
- Call for Input: Update Author's Username in EIP-1193 HOT 24
- EIPIP Meeting 102 HOT 1
- Call for Input: Change Solidity in Final ERC-7201 HOT 4
- EIP Editing Office Hour Meeting 35 HOT 4
- Call for Input: how should we decide whether a PR updating author list of a Final EIP/ERC/RIP be merged or rejected? HOT 4
- EIP Editing Office Hour Meeting 36 HOT 2
- Call for Input: Change Author Username in ERC-6672 HOT 11
- Call For Input: Should we entertain the typo correction PRs HOT 4
- Call for Input: Change Author Username in ERC-5585 HOT 7
- EIPIP Meeting 103 HOT 2
- EIP Editing Office Hour Meeting 37 HOT 8
- EIPIP Meeting 104 HOT 2
- EIPIP Meeting 105 HOT 2
- EIP Editing Office Hour Meeting 38 HOT 4
- EIPIP Meeting 106 HOT 6
- EIP Editing Office Hour Meeting 39 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eipip.