Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update LICENSE to LGPL per example from Sidekiq #233

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

justin808
Copy link
Member

@justin808 justin808 commented Oct 7, 2024

See examples inspiring the licensing:

  1. https://github.com/sidekiq/sidekiq/blob/main/COMM-LICENSE.txt
  2. https://github.com/sidekiq/sidekiq/blob/main/LICENSE.txt

Summary by CodeRabbit

  • New Features

    • Updated licensing terms for Control Plane Flow to LGPLv3, allowing broader usage and integration with proprietary software.
    • Added a section in the COMM-LICENSE.txt for commercial licensing inquiries and potential future offerings.
  • Documentation

    • Updated the LICENSE file to reflect the new LGPLv3 licensing terms and changes in copyright information.

Copy link

coderabbitai bot commented Oct 7, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces significant updates to the licensing documents for the Control Plane Flow project. The COMM-LICENSE.txt file now includes a section detailing the licensing terms under the GNU Lesser General Public License v3.0, emphasizing the conditions for usage and modifications. The LICENSE file has transitioned from the MIT License to the LGPLv3 License, with updates to the copyright year and holder. Both documents indicate the potential for future commercial licensing options and provide contact information for inquiries.

Changes

File Change Summary
COMM-LICENSE.txt Added section on "Control Plane Flow - Commercial Licensing" under LGPLv3, outlining terms and contact info.
LICENSE Changed license from MIT to LGPLv3, updated copyright year to 2024, and changed copyright holder to ShakaCode LLC.

Poem

In the meadow where we play,
New licenses come out to say,
"With LGPL, hop and cheer,
Open paths are now so clear!"
ShakaCode LLC leads the way,
For commercial dreams, we’ll sway! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 resolve resolve all the CodeRabbit review comments.
  • @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.

@justin808 justin808 merged commit 1abb7a8 into main Oct 7, 2024
4 of 5 checks passed
@justin808 justin808 deleted the justin808-license-update branch October 7, 2024 02:09
@justin808 justin808 changed the title Update LICENSE Update LICENSE to LGPL per example from Sidekiq Oct 7, 2024
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.

1 participant