status-im
/
EIPs
mirror of https://github.com/status-im/EIPs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add 'Copyright Waiver' to 'What belongs in a successful EIP?'

This commit is contained in:
Yoichi Hirai 2017-12-05 12:37:32 +01:00
parent 2eb09fcae0
commit a64d8d08db
No known key found for this signature in database
GPG Key ID: E7B75D080FCF7992
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
EIPS/eip-1.md
View File

@ -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. - 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 EIP Formats and Templates
------------------------- -------------------------