License: MIT to AGPL-3.0

[abdulsaheel]

Relicenses protocol from MIT to AGPL-3.0 (owner decision), with NOTICE (MIT up to the previous main commit), TRADEMARKS.md; contributions are licensed under AGPL-3.0 (no CLA).

Do not merge until contributor consent is collected (list kept privately by the owner) and a lawyer has reviewed CLA.md and TRADEMARKS.md. Earlier releases remain MIT.

🤖 Generated with Claude Code

Summary by Sourcery

Relicense OpenStrap under AGPL-3.0 while documenting contribution, historical licensing, and trademark policies.

Enhancements:

• Relicense the project from MIT to AGPL-3.0 and clarify that contributions are covered by the same terms.
• Add trademark guidance separating OpenStrap branding from the AGPL-licensed code.
• Preserve prior MIT licensing through a NOTICE file and update project documentation and contribution guidance.

Documentation:

• Document AGPL-3.0 licensing, contribution terms, trademark usage, and independent project authorship guidance.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 554dc801-f467-4eb8-8540-7ca11520a249

---

📥 Commits

Reviewing files that changed from the base of the PR and between 3ecf17e and e3876ef.

---

📒 Files selected for processing (5)

• CONTRIBUTING.md
• LICENSE
• NOTICE
• README.md
• TRADEMARKS.md

---

 __________________________________________________
< Making NVIDIA proud with all this bug detection. >
 --------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's Guide

This PR changes the project’s current licensing model to AGPL-3.0, adds historical MIT attribution for prior releases, establishes a broad contributor CLA, and documents separate trademark and fork-branding rules. Review should verify the license transition and historical scope, the consistency and enforceability of the CLA/trademark language, and completion of the stated contributor-consent and legal-review prerequisites before merging.

Flow diagram for the license transition and contribution terms

flowchart LR
    History["Earlier releases remain MIT"] --> Notice["NOTICE preserves MIT attribution through previous main commit"]
    Current["Current project"] --> AGPL["AGPL-3.0"]
    Contributor["Contributor"] --> CLA["Accept CLA in first PR"]
    CLA --> Relicense["Maintainer may relicense contributions"]
    Relicense --> AGPL
    Relicense --> Commercial["Commercial or proprietary terms"]
    Project["OpenStrap name and logo"] --> Trademarks["Separate trademark rules"]
    Fork["Modified fork"] --> Branding["Different name and branding"]
    Trademarks --> Branding

Loading

File-Level Changes

Change	Details	Files
Relicense the project from MIT to AGPL-3.0 while preserving MIT licensing for earlier releases.	Replace the license text and add historical attribution in NOTICE. Update repository license references and badges to AGPL-3.0. Document that earlier releases remain MIT.	LICENSE NOTICE README.md
Introduce contributor terms granting broad reuse, patent, and relicensing rights to the project maintainer.	Add a CLA covering contributions across OpenStrap repositories. Require contributors to affirm acceptance in their first pull request. Document the CLA requirement and third-party material restrictions.	CLA.md CONTRIBUTING.md
Separate project trademark usage from the software license and define branding requirements for forks.	Reserve the OpenStrap name and logo independently of the AGPL license. Require modified distributions to use distinct names and branding. Clarify permitted references to OpenStrap and third-party device trademarks.	TRADEMARKS.md README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Sorry @abdulsaheel, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 days and 19 hours by commenting @sourcery-ai review. Upgrade to get a review now.