Update LICENSE - #113
Conversation
All source files have headers designating them as Apache-2.0-licensed. The `LICENSE` file however contains the text of the LGPL 3. This causes e.g. Github to declare the project as being LGPL licensed and also causes problems for packagers who need to figure out the project's license. Since the `LICENSE` file seems to be a remnant of a distant past, update it to contain the Apache license, which seems to be what the project is intended to be licensed under. Signed-off-by: Conrad Hoffmann <ch@bitfehler.net>
|
I think we're going to need @Sheridan to approve this. |
|
Thanks. In the meantime, could you clarify what your current understanding of the license situation is? |
|
When we adopted this exporter, we didn't notice the existing LICENSE file. We added the Apache headers without considering what the original license was. |
|
Okay. While we are at it: it was pointed out to me that the ebuild contained in this repo declares the project to be GPL licensed (not LGPL). |
|
Yup, unfortunately, I think we need the original author's permission to clean this up. |
@Sheridan could you kindly take a look into this? There are more and more contributions coming in, would be awesome to not run into any licensing issues. |
|
I put an official ebuild, written from scratch into the Gentoo repository. So you can clean up the outdated ebuild bundled inside the smartctl_exporter repo. At that point, there is no file that contains a license tag other than Apache-2.0, leaving only @Sheridan's permission to change the license. |
|
Thanks @Sheridan! |
|
Thank you @Sheridan! |
There was some confusion amongst the maintainers about the license for this project, but they have now agreed to Apache 2.0. See prometheus-community/smartctl_exporter#113
6 participants
All source files have headers designating them as Apache-2.0-licensed. The
LICENSEfile however contains the text of the LGPL 3. This causes e.g. Github to declare the project as being LGPL licensed and also causes problems for packagers who need to figure out the project's license.Since the
LICENSEfile seems to be a remnant of a distant past, update it to contain the Apache license, which seems to be what the project is intended to be licensed under.