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

Create LICENSE.md #10

Merged
merged 1 commit into from
Oct 27, 2024
Merged

Create LICENSE.md #10

merged 1 commit into from
Oct 27, 2024

Conversation

0xF6
Copy link
Member

@0xF6 0xF6 commented Oct 26, 2024

Summary by CodeRabbit

  • New Features

    • Introduced the Business Source License 1.1, detailing usage rights and restrictions for the Argon voice chat server software.
    • Added a copyright notice acknowledging the authors and contributors.
    • Defined terms for "Licensor," "Licensed Work," and "Additional Use Grant" to clarify usage parameters.
  • Documentation

    • Updated the LICENSE.md file to include comprehensive licensing terms and conditions.

Signed-off-by: Yuuki Wesp <[email protected]>
@0xF6 0xF6 requested a review from urumo October 26, 2024 18:26
@0xF6 0xF6 self-assigned this Oct 26, 2024
Copy link

coderabbitai bot commented Oct 26, 2024

Walkthrough

The LICENSE.md file has been updated to incorporate the Business Source License 1.1, outlining the usage terms for the Argon voice chat server software. This includes a copyright notice listing authors and contributors, definitions of key terms, and guidelines for acceptable use. The license allows production use with restrictions against competitive offerings and specifies a transition to the Mozilla Public License (MPL) 2.0 after nine years. The document also includes disclaimers regarding the software's provision and compliance requirements.

Changes

File Change Summary
LICENSE.md Updated to include Business Source License 1.1, copyright notice, definitions, and usage terms.

Poem

In a meadow where bunnies play,
A new license brightens the day.
With terms that are clear and fair,
Argon’s voice chat fills the air.
Hops of joy, we celebrate,
For rules that help us innovate! 🐇✨


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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
LICENSE.md (2)

29-29: Format the email address as a proper markdown link.

The email address should be formatted as a proper markdown link to maintain consistency and improve accessibility.

-please contact [email protected].
+please contact [[email protected]](mailto:[email protected]).
🧰 Tools
🪛 Markdownlint

29-29: null
Bare URL used

(MD034, no-bare-urls)


15-15: Consider simplifying the Additional Use Grant language.

The current phrase "in order to compete with" could be simplified to "to compete with" while maintaining its legal meaning.

-Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with any paid version(s)
+Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis to compete with any paid version(s)
🧰 Tools
🪛 LanguageTool

[style] ~15-~15: Consider a shorter alternative to avoid wordiness.
Context: ...d parties on a hosted or embedded basis in order to compete with any paid version(s) of the...

(IN_ORDER_TO_PREMIUM)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d130a83 and b208174.

📒 Files selected for processing (1)
  • LICENSE.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
LICENSE.md

[style] ~15-~15: Consider a shorter alternative to avoid wordiness.
Context: ...d parties on a hosted or embedded basis in order to compete with any paid version(s) of the...

(IN_ORDER_TO_PREMIUM)

🪛 Markdownlint
LICENSE.md

29-29: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (3)
LICENSE.md (3)

1-8: LGTM! Copyright notice and basic license information are properly structured.


29-29: Verify the contact email address.

Please confirm that [email protected] is the correct contact email address for licensing inquiries and that the domain is properly set up to handle these emails.

🧰 Tools
🪛 Markdownlint

29-29: null
Bare URL used

(MD034, no-bare-urls)


1-51: The Business Source License implementation looks solid and complete.

The license properly balances commercial interests with open-source principles, including:

  • Clear copyright attribution
  • Well-defined terms for commercial and non-commercial use
  • Appropriate transition period and change license
  • Comprehensive definitions of competitive offerings
🧰 Tools
🪛 LanguageTool

[style] ~15-~15: Consider a shorter alternative to avoid wordiness.
Context: ...d parties on a hosted or embedded basis in order to compete with any paid version(s) of the...

(IN_ORDER_TO_PREMIUM)

🪛 Markdownlint

29-29: null
Bare URL used

(MD034, no-bare-urls)

@0xF6 0xF6 merged commit 3227f97 into master Oct 27, 2024
2 checks passed
@0xF6 0xF6 deleted the license branch October 27, 2024 10:12
@argon-chat argon-chat locked and limited conversation to collaborators Oct 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants