Add EIP-5069: EIP editor handbook in EIP form

[Pandapip1]

CC: @poojaranjan

I've heavily modified https://hackmd.io/@poojaranjan/EIP-ERC-Editor-handbook to suit the EIP format and to make the document more formal, specific, inclusive, and easier to understand.

Notes to EIP-1 and the README are added to increase awareness.

Items that need discussion:

• Threshold for terminal stagnant status (arbitrarily chosen as 6 months pending further discussion)
• Determine whether the EIP should be Meta or Informational
• Permission to use external links to @SamWilsn's PRs as examples
• Permission to use external links to the EIPIP repository
• Does this EIP really need security considerations and a backward compatibility section?
• Can this be merged as "Living"?

Fixes #5048

[eth-bot]

Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s):

---

(fail) eip-1.md

classification
updateEIP

• Changes to EIP 1 require at least 2 unique approvals from editors; there's currently 0 approvals; the remaining editors are @lightclient, @axic, @SamWilsn, @MicahZoltu, @gcolvin

(fail) eip-5069.md

classification
newEIPFile

• File with name EIPS/eip-5069.md is new and new files must be reviewed
• This PR requires review from one of [@lightclient, @axic, @gcolvin, @SamWilsn]

(fail) README.md

classification
ambiguous

• 'README.md' must be in eip-###.md format; this error will be overwritten upon relevant editor approval

[poojaranjan]

Thanks for adding this to EIPIP meeting agenda. Hope to hear thoughts of EIP editors.

[Pandapip1]

Thank you!

[Pandapip1]

CC'ing @MicahZoltu as the primary "No External Links" enforcer. Which of the following am I allowed to link to?

• Sam's editor PR
• EIPIP repository
• (maybe) EIP insights
• (maybe) PEEPanEIP

[lightclient]

I think this is a good idea. I feel like the framing might be slightly wrong here though -- this is really an EIP Editors handbook, with a section on how to become an editor. Much of the content is just best practices for being an editor. I think it would be useful to contemplate how to structure this so that it is more i) more like a guide to what/how and EIP Editor edits ii) avoid duplication with EIP-1. I still think EIP-1 should stand on it's own as a document that explains exactly how an EIP should be structure, so we need to be careful to not have "special rules" in this EIP.

[lightclient]

I think it's best to drop the "apprentice" term from the EIP and focus on this EIP being a guide to being an editor in general. E.g. how one becomes and editor, certain stylistic rules editors try to enforce to meet EIP-1, etc.

[Pandapip1]

That was my original intent. I'll do that now.

[SamWilsn]

Overall I think this is a good idea, but I don't think it should follow the format laid out in EIP-1. It just doesn't really make sense to write this as a specification...

[Pandapip1]

Moving this PR into draft in case it auto-merges now.

[SamWilsn]

I like where this is going, and would be happy to see it evolve over time. 👍 to merge.

---

After we get the initial version in, I think we can loosen up the format since it really isn't a specification.

[lightclient]

Cool, LGTM.

[lightclient]

test

[lightclient]

LGMT