Linuxiac reports that Solus has begun contacting past contributors to secure approval for relicensing its package repository under MPL-2.0, a step it says is needed before it can share package recipes with aerynOS. Solus explained in May that its package.yml recipes were once kept in a single repository under GPL-2.0-or-later, but their license files were not carried over when development moved to a self-hosted Phabricator instance and the missing terms were never restored when the packages were consolidated into the current getsolus/packages repository on GitHub, leaving the licensing of the public recipes and of contributions made without an explicit license unclear. MPL-2.0 was chosen because it applies file-level copyleft while allowing covered files to be combined with differently licensed code, and because aerynOS already uses it. Solus has been adopting aerynOS packaging tools and intends to convert its recipes to the aerynOS format so the two projects can reuse packaging work instead of maintaining definitions for the same software separately, but says the licensing questions must be resolved first.
Solus moves to relicense its package recipes under MPL-2.0 for aerynOS collaboration
Linuxiac reports that Solus has begun contacting past contributors to secure approval for relicensing its package repository under MPL-2.0, a step it says is needed before it can share package recipes with aerynOS. Solus explained in May that its package.yml recipes were once kept in a single repository under GPL-2.0-or-later, but their license files were not carried over when development moved to a self-hosted Phabricator instance and the missing terms were never restored when the packages were consolidated into the current getsolus/packages repository on GitHub, leaving the licensing of the public recipes and of contributions made without an explicit license unclear. MPL-2.0 was chosen because it applies file-level copyleft while allowing covered files to be combined with differently licensed code, and because aerynOS already uses it. Solus has been adopting aerynOS packaging tools and intends to convert its recipes to the aerynOS format so the two projects can reuse packaging work instead of maintaining definitions for the same software separately, but says the licensing questions must be resolved first.
Source: Linuxiac