-
Notifications
You must be signed in to change notification settings - Fork 30
Description
Background
PILOS is currently licensed under LGPL-2.1.
This choice was originally made because both BBB and Greenlight used the same license when PILOS was started.
LGPL is primarily designed for software libraries that are linked by other applications. Its core strength is ensuring that modifications to the library itself (bug fixes, new features) remain open source when the software is distributed.
The Problem
PILOS is always used as hosted software (SaaS) and is not distributed to end users.
As a result:
- The LGPL does not require providers who modify PILOS and run it as a service to publish their changes.
- Valuable improvements can remain private, even though they are based on community work.
- This weakens collaboration and slows down innovation in the ecosystem.
In short: LGPL does not effectively protect openness for hosted software like PILOS.
Why a License Change Makes Sense
Switching to a more suitable license would:
- Ensure that bug fixes and new features remain open source, even in hosted deployments
- Strengthen fairness between community contributors and commercial operators
- Protect PILOS as a true commons, benefiting all users and contributors
- Align the license with how PILOS is actually used in practice
Contributor License Agreement (CLA)
If we are already asking current and past contributors to agree to a license change, this is also the right moment to introduce a Contributor License Agreement (CLA).
A CLA would:
- Prevent future license changes from becoming legally impossible due to fragmented copyright ownership
- Reduce legal uncertainty for maintainers and contributors
- Ensure long-term sustainability and governance of the project
Proposal
- Discuss and agree on a more appropriate license for hosted software
- Request contributor approval for the license change
- Introduce a CLA for future contributions