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

EIP-1 minors edits: clarify some sections on EIP collaborators and editors, cross-links, links, grammar, etc. #1017

Closed
wants to merge 12 commits into from

Conversation

jamesray1
Copy link
Contributor

@jamesray1 jamesray1 commented Apr 21, 2018

  • Add a link for Ethereum philosophy to the section in the white paper that was originally removed and which I re-added recently.
  • Revise the format for the author header (names can be optional for anonymity).
  • History edits (link to revision history + a minor edit).
  • Add cross-links to other sections for better readability and clarity.
  • Add clarifications on approval before merging from both editors and authors.
  • Add more links for discussion channels
  • Link to other clients and eips.ethereum.org.
  • Reorder EIP editors roughly based on recent contributions.
  • Other minor edits: grammar, etc.

Link for Ethereum philosophy to the section in the white paper that was originally removed and which I re-added recently, reorder EIP editors roughly based on recent contributions and add a note to say that Nick is the lead editor, merging most EIPs, History edits (link to revision history + a minor edit).
@jamesray1 jamesray1 changed the title Clarify some sections on EIP collaborators and editors + more EIP-1 edits: Clarify some sections on EIP collaborators and editors + more Apr 21, 2018
@@ -184,27 +184,27 @@ EIPs may include auxiliary files such as diagrams. Such files must be named EIP-
Transferring EIP Ownership
--------------------------

It occasionally becomes necessary to transfer ownership of EIPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred EIP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the EIP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the EIP. We try to build consensus around an EIP, but if that's not possible, you can always submit a competing EIP.
It occasionally becomes necessary to transfer ownership of EIPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred EIP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the EIP process, or has fallen off the face of the 'net (i.e. is unreachable or isn't responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the EIP. We try to build consensus around an EIP, but if that's not possible, you can always submit a competing EIP.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

To make it easier to spot the change: isn't responding to email

@jamesray1 jamesray1 changed the title EIP-1 edits: Clarify some sections on EIP collaborators and editors + more EIP-1 edits: Clarify some sections on EIP collaborators and editors + other minor edits Apr 21, 2018
@jamesray1 jamesray1 changed the title EIP-1 edits: Clarify some sections on EIP collaborators and editors + other minor edits EIP-1 minors edits: clarify some sections on EIP collaborators and editors, cross-links, links, grammar, etc. Apr 21, 2018
@jamesray1
Copy link
Contributor Author

OK please merge this, I'm done with editing.

@jamesray1
Copy link
Contributor Author

OK I made another PR.

@jamesray1 jamesray1 closed this Apr 21, 2018
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.

2 participants