[Enhancement] Relicense Schej To AGPLv3
Introduction
The open-source community relies heavily on licenses that protect the rights of developers and users alike. In the case of Schej, the current license used is a non-Affero version of the GPLv3, which has a significant loophole when it comes to network access and redistribution. This loophole allows competing entities to take Schej's source code, improve upon it, and make it available through a website without having to contribute their modified code back to the community. As Schej is a service accessed over the internet, the primary form of "redistribution" is entirely unprotected by its current license.
The Problem with the Current License
The current license used by Schej is a non-Affero version of the GPLv3, which omits important stipulations on how network access is considered redistribution. This means that a competing entity could take Schej's source code, improve upon it, make it available through a website, and not have to contribute their modified code back to the community. This is a significant issue, as it undermines the principles of open-source development and the community-driven approach that Schej is built upon.
The Benefits of the AGPLv3
The AGPLv3 is a license that protects project developers against the kind of network-distribution loophole that exists in the current license used by Schej. Section 13 of the AGPLv3 states that if you modify the program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.
Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
Compatibility with GPLv3
The AGPLv3 is totally compatible with the GPLv3, meaning that a relicense wouldn't be a complicated matter. This is stated explicitly in the license, which means that developers can rest assured that the transition to the AGPLv3 will not disrupt the existing community or cause any issues with the current codebase.
Why Relicense to AGPLv3?
Relicensing Schej to the AGPLv3 will provide several benefits to the community and developers alike. Firstly, it will protect the rights of developers by ensuring that modified code is contributed back to the community. Secondly, it will provide users with the opportunity to access the Corresponding Source of the modified code, which is essential for transparency and accountability. Finally, it will align Schej with the principles of open-source development and the community-driven approach that it is built upon.
Implementation Plan
To implement the relicense to AGPLv3, the following steps will be taken:
- Update the license: The current license will be updated to reflect the AGPLv3.
- Modify the code: The code will be modified to include the necessary provisions for the AGPLv3.
- Test the code: The code will be thoroughly tested to ensure that it meets the requirements of the AGPLv3.
- Release the updated code: The updated code will be released to the community, along with documentation and instructions on how to use the AGPLv3.
Conclusion
Relicensing Schej to the AGPLv3 is a necessary step to protect the rights of developers and users alike. The AGPLv3 provides several benefits, including protection against network-distribution loopholes and the opportunity for users to access the Corresponding Source of modified code. The compatibility with the GPLv3 means that the transition will not disrupt the existing community or cause any issues with the current codebase. By implementing the relicense to AGPLv3, Schej will align itself with the principles of open-source development and the community-driven approach that it is built upon.
Introduction
The decision to relicense Schej to the AGPLv3 has been met with excitement and curiosity from the community. To address some of the frequently asked questions, we have put together this Q&A article. Below, you will find answers to some of the most common questions about the relicense to AGPLv3.
Q: What is the AGPLv3, and why do we need it?
A: The AGPLv3 is a license that protects project developers against the kind of network-distribution loophole that exists in the current license used by Schej. It ensures that modified code is contributed back to the community and provides users with the opportunity to access the Corresponding Source of modified code.
Q: What is the current license used by Schej, and why is it a problem?
A: The current license used by Schej is a non-Affero version of the GPLv3, which omits important stipulations on how network access is considered redistribution. This means that a competing entity could take Schej's source code, improve upon it, make it available through a website, and not have to contribute their modified code back to the community.
Q: How does the AGPLv3 protect the community?
A: The AGPLv3 protects the community by ensuring that modified code is contributed back to the community. It also provides users with the opportunity to access the Corresponding Source of modified code, which is essential for transparency and accountability.
Q: Is the AGPLv3 compatible with the GPLv3?
A: Yes, the AGPLv3 is totally compatible with the GPLv3. This means that a relicense wouldn't be a complicated matter, and developers can rest assured that the transition to the AGPLv3 will not disrupt the existing community or cause any issues with the current codebase.
Q: What are the benefits of the AGPLv3?
A: The benefits of the AGPLv3 include:
- Protection against network-distribution loopholes
- Opportunity for users to access the Corresponding Source of modified code
- Alignment with the principles of open-source development and the community-driven approach that Schej is built upon
Q: How will the relicense to AGPLv3 affect existing users?
A: The relicense to AGPLv3 will not affect existing users. The AGPLv3 is designed to work seamlessly with the existing codebase, and users will not need to take any action to continue using Schej.
Q: How will the relicense to AGPLv3 affect developers?
A: The relicense to AGPLv3 will affect developers in that they will be required to contribute modified code back to the community. This will ensure that the community benefits from the contributions of developers and that the codebase remains open and transparent.
Q: What is the timeline for the relicense to AGPLv3?
A: The timeline for the relicense to AGPLv3 is as follows:
- Update the license: immediate
- Modify the code: 2-3 weeks
- Test the code: 1-2 weeks
- Release the updated code: 1-2 weeks
Q: Who should I contact if I have further questions?
A: If you have further questions about the relicense to AGPL3, please contact the Schej development team at schej-dev@lists.schej.org.
Conclusion
The relicense to AGPLv3 is an exciting development for the Schej community. By answering some of the frequently asked questions, we hope to have provided clarity and reassurance to users and developers alike. If you have any further questions, please do not hesitate to contact the Schej development team.