You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It adds an EIP Editor Criteria section to EIP-1: a transparent process for appointing new EIP editors.
There have been discussions about adding more people as editors, but there is no PR with a process proposal in this repository, at this time.
It is a start, I expect the community and current editors to participate and improve.
My approach is:
to make the requirements somewhat strict and based on merit. I think it is better to start with "strict" and see how the process works and how many new editors are still willing to meet requirements. Afterward, the process can be updated.
start with a process that can be implemented in Github (because this is the current medium), but could eventually be decentralized
Disclaimer: I do not fit any editor category from the proposal, not now and not in the near future.
The text was updated successfully, but these errors were encountered:
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.
This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.
Proposal text can be found at: #2172
It adds an EIP Editor Criteria section to EIP-1: a transparent process for appointing new EIP editors.
There have been discussions about adding more people as editors, but there is no PR with a process proposal in this repository, at this time.
It is a start, I expect the community and current editors to participate and improve.
My approach is:
Disclaimer: I do not fit any editor category from the proposal, not now and not in the near future.
The text was updated successfully, but these errors were encountered: