Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 26 minutes and 26 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
This PR updates the project's license from the GNU General Public License v3.0 (GPLv3) to the GNU Affero General Public License v3.0 (AGPLv3).
Why are we making this change?
Under the standard GPLv3, the copyleft provisions are only triggered upon distribution of the software. This creates a known loophole (often called the "SaaS loophole" or "ASP loophole"): a company can take our code, modify it extensively, and offer it to users as a web service without ever actually "distributing" the binaries. Consequently, they are not obligated to share their improvements back with the community.
The AGPLv3 was specifically designed to close this loophole. It contains the same robust copyleft conditions as the GPLv3, but adds a crucial provision (Section 13: Remote Network Interaction). This section requires that if you modify the program and let others interact with it remotely through a computer network, you must make the source code of your modifications available to those users.
By moving to the AGPLv3, we are:
Protecting the open-source ecosystem: Ensuring that any entity benefiting from hosting our software and modifying it gives those modifications back to the community.
Securing project sustainability: Preventing bad actors or large cloud providers from silently forking our project, wrapping it in a proprietary service, and starving the core project of contributions.
Impact and what this means for our users:
For individual users & internal company use: If you are using or modifying the software strictly for internal use and not exposing it externally as a service, nothing changes for you.
For contributors: No change. Your contributions will simply be licensed under AGPLv3 going forward.
For SaaS providers & Commercial hosts: If you modify our software and allow users to interact with it over a network, you must now provide a way for those users to access the modified source code under the AGPLv3.