Skip to content
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

chore(license): switch main license to GPL-3.0-or-later #767

Merged
merged 4 commits into from
Nov 4, 2019
Merged

chore(license): switch main license to GPL-3.0-or-later #767

merged 4 commits into from
Nov 4, 2019

Conversation

rhizoome
Copy link

@rhizoome rhizoome commented Oct 30, 2019

Based on the discussion in issue #751, we reevaluated our goals. We want

  • diverse uses and integration of Caluma
  • Caluma to remain public as Free Software
  • an active community
  • to guarantee mutual benefit to our contributors

We found that the definitions in AGPL aren't as clearcut as we wished; therefore, we want to switch to GPL-3.0-or-later. GPL will support all of our goals, with a minor draw-back: Not every last modification is guaranteed to end up in public. Which isn't that bad and it resolves all discussion about configuration.

@rhizoome rhizoome requested a review from winged October 30, 2019 15:22
Copy link
Contributor

@winged winged left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Just one suggestion: Instead of a short summary in the README, consider putting the main reasons for the choice, or a reference/link to the issue where it was discussed (#751).

README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@czosel czosel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!

Copy link
Member

@open-dynaMIX open-dynaMIX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@anehx
Copy link
Contributor

anehx commented Oct 31, 2019

Looks good, there's only one unanswered question: what exact license are we using for the frontend packages?

Copy link
Contributor

@anehx anehx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The notation is a bit confusing, we should decide which one of those we use:

  • GPL-3.0-or-later
  • GPLv3+
  • GPL-3.0

@rhizoome
Copy link
Author

The notation is a bit confusing, we should decide which one of those we use:

  • GPL-3.0-or-later
  • GPLv3+
  • GPL-3.0

@anehx GPL-3.0-or-later is the only correct one. Its the official SPDX identifier. I can't change that pypi doesn't use the correct one and that the license text itself isn't consistent. I changed the badge, though. Let me know if I missed an occurrence.

@rhizoome
Copy link
Author

And GitHub does everything wrong, when it comes to licenses:

  1. They use the wrong identifiers
  2. They don't accept the SPDX license texts
  3. They don't scan the right files

Many people opened issues, for some reason, they don't want to fix the problem.

@rhizoome rhizoome marked this pull request as ready for review November 4, 2019 10:21
@rhizoome rhizoome merged commit dfba2b2 into projectcaluma:master Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants