Added new section

Author: malfisya

content/blog/2026/05/clearing-up-the-fog/index.md

@@ -64,7 +64,13 @@ That doesn't mean we can just apply the license to the package repository: we ne
 - By commenting on [this GitHub issue](https://github.com/getsolus/packages/issues/7815), which also details the rest of the plan.
 - By consenting to the change in the next contribution to the packages repository.
 - By replying to an email that we will send in the future.
+  
+## Should I do anything?
 
+- For contributors: You can consent to the license change by the methods mentioned above. We need your consent for this change to happens.
+- For regular users and non-contributors: You **don't** have to do anything. This project doesn't affect your daily use of Solus.
+
+## Conclusion
 In short, we want to clear up the “fog” around the licensing situation that surfaced through our migrations so everything is unambiguous going forward. Relicensing under MPL-2.0 gives us that clarity. It ensures that our work remains open, contributions are properly defined, and collaboration can happen with confidence.
 
 If you have contributed in the past, we appreciate your work and your patience as we resolve this. And if you are considering contributing, we hope this change makes it easier to do so with certainty. With new license in place, we’ve got a clear path forward for contributions and collaboration.