This ECIP describes a Phoenix hard-fork which would replace Azltan#263
Conversation
|
ECIP Editors: @soc1c @YazzyYaz @meowsbits @sorpaas @BelfordZ: |
…ddition to attestation and thanks higher up.
|
@sorpaas Is this blocked from merging purely on your review? Please can you unblock and merge please? Thank you. |
|
|
||
| ## Copyright | ||
|
|
||
| This work is licensed under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0). The author, Bob Summerwill, attests to his sole authorship of this work, and that he is able to contribute this work to the ECIP process under the Apache 2.0 licence. |
There was a problem hiding this comment.
The author, Bob Summerwill, attests to his sole authorship of this work, and that he is able to contribute this work to the ECIP process under the Apache 2.0 licence.
I think you need to remove this line. I don't think this sentence is true.
|
You are quite right. It is Boilerplate from my earlier ECIPs. Please suggest appropriate language and I am happy to update. Exact same for the 3 ECIPs. |
|
It was “filling in” for the DCO language we are still lacking, but sole authorship is obviously misleading here. I was the sole author of this ECIP but obviously not to the content of much of the text or protocol design. |
sorpaas
left a comment
sorpaas
left a comment
There was a problem hiding this comment.
Potential copyright violation. It's inappropriate to claim "sole authorship" when the specification clearly has texts directly copied from Core Paper project.
…from earlier ECIP. It was inappropriate in this example.
|
@sorpaas Updated. How is this now? |
5 participants
No description provided.