The Rare Time Changing Software License Is Good!

Summary

Forgejo, a Git service similar to GitHub and GitLab, has transitioned from the MIT license to the copyleft GPL v3, aligning with its core values and Git's license. This change primarily impacts distributors, requiring them to provide source code under the same terms. Despite initial community concerns, the license shift aims to protect user freedoms and prevent vendor lock-in, reflecting a significant and deliberate decision after extensive discussions.

Takeaways

• 🔄 **Re-licensing to Copyleft**: The project Forgejo, similar to Git, has re-licensed from a permissive MIT license to the copyleft GPL v3 or later.
• 🌐 **Platform Overview**: Forgejo is a self-hosted Git service, akin to GitHub or GitLab, used for managing and collaborating on Git repositories.
• 📢 **Origin of Forgejo**: Forgejo originated in 2022 as a fork from Gitea due to disagreements over the project's direction and domain transfer to a for-profit entity.
• 👥 **Impact on Users**: For most users, especially developers hosting their source code, the license change will have no practical impact on their use of Forgejo.
• 📦 **Distribution Requirements**: Distributors of Forgejo are now required to provide full source code under the same GPL terms if they redistribute binaries or modified versions.
• 💼 **Business Implications**: Businesses can continue to sell Forgejo services without major adjustments, as long as they respect the license and uphold the project's values.
• 🔗 **Dependency and Compatibility**: Forgejo's dependency on Git, a copyleft software, and the discovery of incompatible non-free dependencies influenced the decision to switch to a copyleft license.
• 🔄 **License Flexibility**: The license change from MIT to GPL demonstrates the project's adaptability to protect its core values and user freedoms.
• 🤝 **Community Values**: The shift to a copyleft license aligns with the community's values, ensuring that contributions and the project itself remain open and free.
• 📝 **Ongoing Discussions**: There are ongoing debates within the community about license compatibility and the implications of the change, reflecting the complexity of open-source licensing.

Q & A

What is the significance of a project changing its license from permissive to copyleft?

Changing a project's license from permissive (like MIT) to copyleft (like GPL) is significant because it shifts the terms under which the software can be used and distributed. It ensures that derivative works also remain open-source, which aligns with the project's core values of promoting software freedom and community collaboration.

What is Forgejo and how does it relate to Gitea?

Forgejo is a source forage platform similar to GitHub and GitLab, which allows users to host and manage Git repositories. It was forked from the Gitea project in 2022 after a community election led to the transfer of Gitea's domains and trademarks to a for-profit company, sparking a community-driven fork resulting in Forgejo.

How does the license change affect the average user of Forgejo?

For the average user who simply hosts and manages their source code with Forgejo, the license change from MIT to GPL does not affect them directly. They can continue to use Forgejo without any changes to their workflow or rights.

What are the new requirements for distributors of Forgejo under the GPL license?

Under the GPL license, distributors of Forgejo are now required to provide the full source code of their Forgejo variant, including any modifications, under the same license terms as Forgejo itself. This ensures that the freedom to modify and distribute the software is preserved.

How does the license change impact the distribution of Forgejo in Linux distributions?

For Linux distributions, the license change to GPL may require them to provide the source code for Forgejo alongside the binaries, which is a common practice for many open-source projects. Most distros already offer source code for their packages, so this change may not significantly impact their distribution practices.

Can you sell services based on Forgejo after the license change?

Yes, you can sell Forgejo services, including hosting for others, after the license change. As long as you respect the GPL license terms and ensure users receive the freedoms granted by Forgejo, there should be no need to adjust your business practices.

Why did Forgejo decide to change its license to GPL?

Forgejo decided to change its license to GPL to align with its core values of promoting software freedom and to accept contributions under copyleft licenses. This change also makes it easier to reuse other copyleft software and ensures that users of Forgejo are not subjected to restrictive business practices that could lead to vendor lock-in.

What is the compatibility of Forgejo with Git, and how does the license change affect this?

Forgejo is designed to work with Git, which is licensed under GNU GPLv2. The license change to GPL does not affect the compatibility between Forgejo and Git, as both licenses are copyleft and compatible with each other, allowing for the combination of the two software projects.

What are the implications of the license change for companies that avoid copyleft software?

For companies that avoid copyleft software, the license change to GPL may require them to reconsider their stance on using Forgejo, especially if they bundle it with other software or distribute it. They will need to ensure compliance with the GPL license terms, which could involve providing source code or making adjustments to their distribution practices.

How does the license change affect contributions to Forgejo?

The license change to GPL means that contributions to Forgejo must also be under GPL or a compatible license. This ensures that all contributions align with the copyleft philosophy and that the project remains open-source with the freedom to use, modify, and distribute the software.