New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KAFKA-12625: Fix the NOTICE file #10693
Conversation
Adds new NOTICE-binary file and packages it in the binary release
|
I would highly appreciate any hint on how to proceed for the dependencies that do not include a notice file in their jar files but might include them in their source code repositories. |
| @@ -243,7 +243,6 @@ netty-handler-4.1.59.Final | |||
| netty-resolver-4.1.59.Final | |||
| netty-transport-4.1.59.Final | |||
| netty-transport-native-epoll-4.1.59.Final | |||
| netty-transport-native-epoll-4.1.59.Final | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this line from LICENSE-binary as it was a duplicate one
|
@vvcephei As you were the last one touching that area, would you like to review this PR? |
|
Hi @ableegoldman as you reviewed the last change in that area (fix license files) do you think you can review this one? Thanks in advance! |
|
Hey @jlprat , can you elaborate on (a) the motivation behind adding this I'll extend the same disclaimer, make no assumption that I know what I'm talking about |
|
Thanks for looking at it @ableegoldman , a) I added a NOTICE-binary file following the same pattern done for the LICENSE patch. The purpose of the NOTICE-binary is to be included in the distribution file only. I looked at https://github.com/apache/hadoop and attempted to use the same approach. On short, NOTICE contains Kafka's notices while NOTICE-binary contains Kafka's and its dependencies' notices so it can be packaged in our distribution files. |
|
Thanks. We just went through a large cleanup of the licensing and notices for the 2.8.0 release, which is how we ended up in the current state of things. It was my understanding that we had reached a place in which all the necessary pieces were being included in the correct place, which is why I was asking what the motivation for making further changes was. I'll let @vvcephei chime in from here |
|
Thanks @ableegoldman for your comments. As far as I can tell after reading https://issues.apache.org/jira/browse/KAFKA-12625, mostly the copyright files were worked on, but NOTICE file was still not done yet. Or at least not completely. |
Hey, all, sorry I was so slow in responding.
IIRC, what happened in 2.8 was that we invested a ton of time into fixing the license and copyright notices, and decided that the notice files weren't to the same level of urgency to continue blocking the ongoing releases. To be honest, I meant to follow up on the notice files myself, but lost the thread. Thanks to @jlprat for picking it up!
Adds new NOTICE-binary file and packages it in the binary release
|
Thanks @vvcephei for the review! |
Adds new NOTICE-binary file and packages it in the binary release
Adds new NOTICE-binary file and packages it in the binary release
This follows up the #10474 pull where LICENSE was fix.
Similarly as in that PR, I do not know if this is correct, and I would add the same disclaimer @vvcephei did: "Please make no assumption that I know what I'm doing and let me know if anything seems wrong."
I went through all jar files within the distribution file and copied the content of any existing NOTICE file.
Notes:
Committer Checklist (excluded from commit message)
The text was updated successfully, but these errors were encountered: