License Change: LGPL-3.0-or-later

[rhizoome]

Following the license change of Caluma, we want to change the license of the Ember-Caluma, too.

Goals

The same goals we evaluated in Caluma apply to the frontend:

• 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 in the frontend, we can and want to be more permissive for the following reasons:

• Since the frontend only works with the backend and the backend is GPL, the frontend can be LGPL without compromising our goals. There is no incentive to withhold changes in public interest.

• LGPL allows tight integration with existing frontends. We want to integrate the frontend directly in existing UIs that might not be compatible with GPL.

What LGPL-3.0-or-later means for Ember-Caluma

The following summary is not legally binding, please refer to the LGPL-3.0-or-later:

You are free to modify and extend the Ember-Caluma as you wish. You can integrate the Ember-Caluma with any software you wish. If you publish or sell

• a modified or extended version of the frontend

• or an extension to frontend

you have to make the source-code of these modifications available under LGPL-3.0-or-later or a compatible license.

Comparison backend / frontend

• The GPL license of the backend does not affect integrations because it is server-side

• The LGPL license of the frontend does not affect integrations because LGPL is permissive

[rhizoome]

@anehx If you have any questions about the reuse-tool please let me know. If you want I can prepare a commit introducing reuse for you. Please put me on the reviewers list for the PR.

[czosel]

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀