sorpaas
commented
7 years ago A complete ECIP for defining the whole process might be hard or take some time to reach consensus. However, I think we can start with some simple formalized processes (just to avoid the nobody-knows-what-to-do scenario).
Below I propose how an ECIP is accepted in to Draft. Note that those are mostly the process that we have already been using for working on the last several ECIPs. This process is also mostly the same as the "BIP process, revised" and ECIP-1000, except that in "BIP process, revised", the approval review is done only by "editors".
- New ECIPs are first merged into draft -- they're not necessarily reached consensus with the community yet.
- Merging a new ECIP requires one approved review from another person. That approval only means that the other person thinks that that ECIP is of good quality. The other person that approved it does not need to be in agreement or in support of that ECIP. (See also the BIP workflow about the only scenarios to reject a proposal)
- With one approved review, the author is free to merge the ECIP or continue to wait for more discussions and reviews.
I think we have a problem with general ECIP process, it was not officially accepted as ECIP active proporsal. Some datails you can read in
README.md, but it's not work. We have to accept our own process and publish it as ECIP, similar to BIP process, revised.