Skip to content
An Update to Licensing Change Project

An Update to Licensing Change Project

October 10, 2026·Muhammad Alfi Syahrin
Muhammad Alfi Syahrin

Modified Solus logo with license iconography on blue gradient background

Hello everyone! We have an update to the relicensing project progress. We just sent the first email to the contributors that have not yet provided their consent. If you have contributed to Solus packages repository, please check your inboxes (and your spam folder) for the email!

This email (see below) is a reminder for contributors to provide their consent to the license change. We will re-send this email in 30 days in case this one is lost or forgotten, unless you unsubscribe from our emails. This email will also not be sent again if we receive a reply from you.

We hope all contributors are willing to provide their consent. Please reply to the email or leave a comment on the GitHub issue to confirm your consent.

That is all for today. Thank you, and cheers!

Email Content

Solus needs your help for licensing changes

Hello YourName!

You are receiving this message because you have contributed to the Solus packages repository. This email will be sent again in 30 days in case this one is lost or forgotten, unless you unsubscribe from our emails. This email will also not be sent again if we receive a reply from you.

We (Solus) are in the process of clarifying the license for our packages repository and we need your help. You can read our reasoning in full on the blogpost but the TL;DR :

  • The problem: Solus packages repository (which now lives at getsolus/packages) does not have clear licensing terms.
  • Effects:
    • It creates ambiguity whether or not our package recipes are actually open-source.
    • Our current situation introduces uncertainty about whether contributed code has been properly licensed.
    • If the current licensing situation remains unresolved, it will block us from sharing recipes with AerynOS.
  • The Solution: Re-license our packages repository under the Mozilla Public License, version 2.0 (MPL-2.0). We chose this license because it strikes a good balance between so-called ‘copyleft’ protections, and permissibility, and it allows us to share code between Solus and AerynOS

We need contributors to explicitly agree to the change which can be done in the following ways, whichever you prefer:

  • By replying to this email.
  • By commenting on this GitHub issue, which also details the rest of the plan.

Comment or reply with this following statement:

I agree to license all my previous contributions to this repository under the terms of the Mozilla Public License version 2.0 (MPL-2.0).

Thank you for your time and have a good day. Cheers!

Solus Staff