Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

which lgpl version does the repo follows #112

Open
runcom opened this issue Jul 27, 2023 · 4 comments
Open

which lgpl version does the repo follows #112

runcom opened this issue Jul 27, 2023 · 4 comments

Comments

@runcom
Copy link
Member

runcom commented Jul 27, 2023

Since we don't use headers in source files, it's not clear if the project is licensed under the:

  • lgpl 2.1 or later
  • lgpl 2.1 only

The License itself doesn't change, just the headers that we don't use, but since we need to fix the License text in Fedora, we need to know exactly what is it

@nullr0ute
Copy link
Member

It's not a library, so I'm not sure why it's using LGPL at all TBH

@runcom
Copy link
Member Author

runcom commented Jul 27, 2023

It's not a library, so I'm not sure why it's using LGPL at all TBH

that became my second question too lol - @LorbusChris any idea?

@LorbusChris
Copy link
Member

I don't recall why LGPL was chosen. I'd be fine with re-licensing my contributions to this repo (including the name) too if that helps.

@LorbusChris
Copy link
Member

Let's stick to lgpl 2.1 only for now?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants