Skip to content

Feat: Change license from MIT to GNU GPL v3#190

Merged
mariocandela merged 1 commit intomainfrom
189-feat-change-licenze-from-mit-to-gnu-gpl-v3
Mar 31, 2025
Merged

Feat: Change license from MIT to GNU GPL v3#190
mariocandela merged 1 commit intomainfrom
189-feat-change-licenze-from-mit-to-gnu-gpl-v3

Conversation

@mariocandela
Copy link
Copy Markdown
Contributor

@mariocandela mariocandela commented Mar 31, 2025

Hello everyone,

In this merge request, we are making a fundamental change to our project: switching from the MIT license to GNU GPL v3. Recently, we have noticed that some companies are cloning and reselling Beelzebub, which not only jeopardizes the economic value of our work but also the core open source principles we hold dear.

The GNU GPL v3 provides us with a much stronger legal protection compared to the MIT license, ensuring that all modifications and distributions of our software remain free and open, in full respect of the community’s values. In particular, this license:

Ensures software freedom: All users will be required to share any modifications, thereby preventing commercial appropriation without acknowledgment.

Protects contributors: Companies will no longer be able to take our code, modify it, and resell it as their own, ensuring that our work remains accessible to the entire community.

Promotes a collaborative ecosystem: With GPL v3, every improvement made to the project will be made available to everyone, reinforcing transparency and collaboration.

We are confident that this change will not only safeguard our work from commercial exploitation attempts but also help maintain the true spirit of open source, fostering an environment of sharing and collective growth.

Thank you for your continued support and for being an integral part of this journey.

@bryannolen @t3chn0m4g3 @yaleman @eltociear

Best regards,

Mario

Summary by CodeRabbit

  • Chore
    • Updated the software’s licensing terms to GNU GPL Version 3, introducing revised permissions and responsibilities for usage, modification, and distribution.

Change from MIT to GNU GPL V3

Signed-off-by: Mario Candela <mario.candela.personal@gmail.com>
@mariocandela mariocandela linked an issue Mar 31, 2025 that may be closed by this pull request
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 31, 2025

Walkthrough

This pull request replaces the existing MIT License in the repository with the GNU General Public License Version 3. The update involves removing the previous license text with its associated permissions and conditions, and introducing the GPL’s more comprehensive terms. The change is also reflected in the declarations of exported or public entities to ensure consistency across the project.

Changes

File Change Summary
LICENSE Replaced the MIT License text with GNU GPL v3 content, including definitions, permissions, modification and distribution requirements, and warranty disclaimers.

Possibly related issues

Poem

I’m hopping through the code with glee,
A new license blooms for all to see,
From MIT’s ease to GPL’s might,
I dance in lines of legal light,
A bunny’s cheer in code so free!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 74cf64f and 32432d4.

📒 Files selected for processing (1)
  • LICENSE (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (9)
LICENSE (9)

1-7: License Header and Basic Permissions
The header clearly identifies the GNU GPL Version 3 and includes the permission notice for verbatim copying and distribution. Ensure that the exact formatting (whitespace, capitalization, etc.) matches the official GPL text to guarantee legal validity.


8-20: Preamble Introduction
The preamble effectively introduces the intent behind the GNU GPL v3—emphasizing free software and the copyleft nature of the license. It accurately describes that the license is intended to preserve user freedoms while applying to software and related works.


22-38: Freedom and Responsibilities Clause
These lines describe the freedoms granted (e.g., the right to copy, distribute, and modify) and outline the corresponding responsibilities required when redistributing the software. The language here faithfully reproduces the GPL’s intent.


40-48: Developer Protection and No Warranty Clause
This segment details both the protection afforded to developers (by clarifying that modified versions must bear notices of change) and the disclaimer of warranties. Given its legal importance, please verify the text matches the official GPL version to avoid any misinterpretation.


50-59: Device Restriction Protection
The section addressing devices that might block or restrict user modifications is critical for ensuring the software remains free. It is appropriately included as per the GPL v3 standard; however, it is worth double-checking that the reproduction is precise with respect to the official document.


61-67: Software Patent Provision
This portion covers the issues of software patents, emphasizing that patents cannot be used to render the program proprietary. The language here is crucial in protecting both users’ and contributors’ rights and appears accurately transcribed from the official GPL v3.


68-70: Transition to Detailed Terms
These brief lines signal the start of the detailed “Terms and Conditions” section. Their concise presentation is appropriate for clearly demarcating the continuation of the legal text.


71-622: Terms and Conditions Section
This comprehensive block covers the definitions, rights, obligations, termination clauses, and other critical legal details of the GPL v3. Given its extensive nature and legal significance, please verify that every subsection matches the official wording and formatting. Any deviation—even minor—could have legal ramifications.


623-675: Application of Terms and Project Attribution
The final section explains how to apply the GPL terms to new programs and includes custom notices for the project (e.g., “Beelzebub a honeypot framework low code” and associated copyright details). Ensure that these custom elements do not conflict with GPL guidelines and that the contact instructions are clear and compliant.


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@mariocandela mariocandela changed the title Feat: Change licenze from MIT to GNU GPL v3 #189 Feat: Change licenze from MIT to GNU GPL v3 Mar 31, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 31, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.66%. Comparing base (74cf64f) to head (32432d4).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #190   +/-   ##
=======================================
  Coverage   82.66%   82.66%           
=======================================
  Files           7        7           
  Lines         421      421           
=======================================
  Hits          348      348           
  Misses         63       63           
  Partials       10       10           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mariocandela mariocandela merged commit 8f1075b into main Mar 31, 2025
6 of 8 checks passed
@mariocandela mariocandela deleted the 189-feat-change-licenze-from-mit-to-gnu-gpl-v3 branch March 31, 2025 19:44
@mariocandela mariocandela changed the title Feat: Change licenze from MIT to GNU GPL v3 Feat: Change license from MIT to GNU GPL v3 Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feat: Change license from MIT to GNU GPL v3

1 participant