Upcoming Release: New Licensing Approach for Core and Core Plugins

December 18, 2024

In our upcoming WLP V2 release, a new licensing approach will be introduced to streamline how we distribute and license the core software and core plugins. This strategy provides greater flexibility for developers while keeping the core open-source under the GPL.

Key Changes

1. Core Software (GPL):
   • The core software will remain under the GPL, ensuring it stays open-source. Modifications to the core code will still require redistribution under the GPL.
2. Core Plugins:
   • We are moving essential functionality from the core code into core plugins, which will now be distributed separately. Some of these plugins will remain under the GPL, while others can be licensed independently. This gives us more flexibility with how we handle core plugin licensing in the future.
3. Custom Zip Assembly:
   • To facilitate the process for users, we will introduce a dynamic download system. Users will be able to select the core and core plugins they need, and a custom zip generator will package them together for easy download and integration.

Why This Matters

• For Core Developers: By separating core code into core plugins, we provide flexibility in how new core plugins and features are licensed. While core plugins that are mostly based on the existing GPL code will remain under the GPL, we can license new core plugins differently, allowing for a broader range of licensing options.
• For Users: The core and core plugins will be distributed separately. The custom zip assembly will allow users to choose the core and plugins they wish to use, making integration seamless.
• For Core Plugin Developers: New core plugins developed for additional features will have the flexibility to be licensed under different terms. This allows developers to choose their own license.

How It Works

• Core Software: The core software will continue to be licensed under the GPL, with any modifications needing to be released under the same license if redistributed.
• Core Plugins: The essential functionality of the core will be split into core plugins, which may be licensed independently from the core. Existing mostly copied core code that is moved into plugins will remain under the GPL, while new core plugin functionality can be licensed more freely.
• Custom Packaging: Users will be able to select the core and desired core plugins through the custom zip assembly system, ensuring an easy and compliant integration.

Examples in practice

• If you fork or modify the core software, you are required to release your modifications under the GPL.
• If you move core code functionality into a core plugin, it may remain under the GPL (if it’s mostly based on the core code)
• If you write a new core plugin from scratch you can license it under any license you want, such as Apache 2.0 or even more permissive to protect your hard work from falling in the hands of big corporations for free.

Neil

Lead dev @ WLP (WhiteLabelPress)