From a64d8d08db4af3d90c01697807a3e9cf96dbd4dc Mon Sep 17 00:00:00 2001 From: Yoichi Hirai Date: Tue, 5 Dec 2017 12:37:32 +0100 Subject: [PATCH] Add 'Copyright Waiver' to 'What belongs in a successful EIP?' --- EIPS/eip-1.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/EIPS/eip-1.md b/EIPS/eip-1.md index eb3315e1b1794..77b7f7a77f71b 100644 --- a/EIPS/eip-1.md +++ b/EIPS/eip-1.md @@ -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 -------------------------