Skip to content
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

Create a FIP Editor Handbook for current and intending FIP Editors #1101

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

luckyparadise
Copy link
Collaborator

To further expand the roles, responsibilities, and expectations for FIP Editors. I have written a handbook to form an extended guide for current and intending FIP Editors.
Feedback is welcome.


For pull requests (PRs) that impact **protocol design/specifications** or include **considerations** affecting the protocol:

- FIP Editors must ensure **at least two appropriate technical reviews and approvals** have been obtained before considering the PR ready to merge.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the sole difference between these and the ones below the inclusion of "appropriate"? I thought you were going for the "technical".

I'm not sure "appropriate" is well-defined enough for this to make a difference.

- Be interested in participating in governance.
- Be skilled in using GitHub.

Continued inability to meet these requirements may lead to removal from the position. Interested candidates can apply by completing [this form]. Current FIP Editors will review membership requests.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a link to the form someone submits? Are we actually going to make and maintain a form? Given how low volume this will be, is it better to create a mailing list (e.g., [email protected]) that contacts all the FIP editors and they handle from there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants