ssl: Add copyright #9624
ssl: Add copyright #9624
Conversation
CT Test Results 2 files 66 suites 27m 1s ⏱️ Results for commit a5d0ef6. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
lib/ssl/src/ssl_srp_primes.erl
Outdated
| @@ -1,3 +1,7 @@ | |||
| %% FROM RFC 5054 | |||
| %% Copyright (C) The IETF Trust (2007). | |||
There was a problem hiding this comment.
This is the copyright, which you should write if they were the authors of this file.
If this is the case, this file still needs a license. A copyright says who is the author, and the license grants you permission to use it.
For the license, write a SPDX identifier, e.g., SPDX-License-Identifier: Apache-2.0
There was a problem hiding this comment.
So you mean I should add our copy-write ( we wrote the file) but the content is from RFC 5054, but modified to use erlang syntax, which is IETF has the copyright to.
There was a problem hiding this comment.
The idea comes from RFC 5054, but this is our implementation.
It is nice to give them credit and point them out, but we are the copyright holders of this implementation AFAIK.
TLDR
You can add our Apache 2.0 license as you did in the last commit.
IngelaAndin
force-pushed
the
ingela/ssl/copyright
branch
from
b108011 to
a5d0ef6
Compare
No description provided.