Skip to content

Commit

Permalink
Add 'Copyright Waiver' to 'What belongs in a successful EIP?'
Browse files Browse the repository at this point in the history
  • Loading branch information
pirapira committed Dec 5, 2017
1 parent 2eb09fc commit a64d8d0
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions EIPS/eip-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,10 @@ Each EIP should have the following parts:

- Implementations - The implementations must be completed before any EIP is given status “Final”, but it need not be completed before the EIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of “rough consensus and running code” is still useful when it comes to resolving many discussions of API details.

<!-- -->

- Copyright Waiver - All EIPs must be in public domain. See the bottom of this EIP for an example copyright waiver.

EIP Formats and Templates
-------------------------

Expand Down

0 comments on commit a64d8d0

Please sign in to comment.