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

Re-license the WLED project from MIT to EUPL #4194

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Conversation

Aircoookie
Copy link
Owner

WLED is moving to the copyleft EUPL v1.2 license.

What is the difference between EUPL and MIT?
The license WLED had so far from the very first version is the MIT license - this basically allowed you to do anything with the code as long a you maintained attribution.
The EUPL is a copyleft license, which means that if you distribute WLED, you also have to release the source code.
However, it has several advantages over the GPL family of licenses - these have a viral effect in that you are locked into that GPL variant and will never be able to use that code under any other license (except if you obtain the consent of all contributors to change the license)
EUPL code on the other hand may be incorporated into projects under a number of other copyleft licenses - including the GPL, AGPL, MPL and OSL. As an added benefit, it is written with intricacies of EU law in mind and a legally binding version is available in 23 languages.

Why this change?
WLED as a project has experienced a huge growth over the last few years, thanks to every single one of you!
When I started the WLED project in 2016 and it was a one-man-show with a small code base, I didn't really care about how it would be used and didn't ever anticipate it becoming this huge!
Now that WLED is a thriving open-source project with an ever-growing number of collaborators, some have been hesistant to contribute to the project out of concern their hard work will be misappropriated by "freeloaders" profiting off of it without giving anything in return.
The amazing WLED-MoonModules fork with a plethora of delightful 2D, audio and other enhancements over the base fork had even moved to the GPLv3 license to alleviate this concern.
This had the unfortunate side effect that none of their awesome additions could be contributed back upstream to the main WLED repository - as GPL code cannot be incorporated into an MIT project (without changing the license to GPL for everything)
All the more I am delighted to announce that today, both the MoonModules and base WLED collaborators have decided together to adopt EUPL and thus free exchange between the two repos can commence again!
The EUPL license underlines reciprocity - we are delighted to gift you the codebase of this wonderful project - all we are asking is that you share your improvements back with us too.

I am using WLED at home or coded a special effect for an art installation or event. What do I have to do?
Nothing - everything will stay as it is with the added reassurance that WLED will now legally stay free forever and any published improvements will be made available to you.
Only once you start distributing your version, you'll have to release its source code.

I am using WLED or a fork derived from WLED in my product, what do I have to do?
If your product runs a version based on up to and including 0.15.0-b6, nothing yet. These versions will continue to be available under the MIT license forever.
If you want to update to a later version of WLED, you'll have to comply with the EUPL - e.g. to provide the users with the source code of the project.
If you have modified the code and want to distribute your modified version, you will need to release the source of your modifications as well.
Your hardware design fully belongs to you, you don't need to open-source it - although the community would certainly appreciate it ;)

@Aircoookie Aircoookie merged commit e9d2182 into 0_15 Oct 15, 2024
40 checks passed
@Aircoookie Aircoookie deleted the eupl-relicense branch October 15, 2024 23:15
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.

1 participant