Update to Apache 2.0 License

[fedekunze]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• tackled an existing issue or discussed with a team member
• left instructions on how to review the changes
• targeted the main branch

Reviewers Checklist

All items are required.
Please add a note if the item is not applicable
and please add your handle next to the items reviewed
if you only reviewed selected items.

I have...

• added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• confirmed all author checklist items have been addressed
• confirmed that this PR does not change production code
• reviewed content
• tested instructions (if applicable)
• confirmed all CI checks have passed

Summary by CodeRabbit

• Chores

  • Updated the licensing terms, now adopting the Apache License Version 2.0 to offer a clearer and more permissive framework.
  • Removed an outdated FAQ section related to previous licensing details.

• Documentation

  • Streamlined public information by removing details about future roadmap plans and partnership opportunities.

[coderabbitai]

Walkthrough

This pull request updates the project licensing by replacing the Evmos Non-Commercial License with the Apache License, Version 2.0. The change restructures the license into clearly defined sections with specific definitions, rights, and conditions. Additionally, the LICENSE_FAQ.md file has been entirely removed, and the README.md file has been updated by removing the sections related to the roadmap and partnership information.

Changes

File(s)	Changes
LICENSE	Replaced the Evmos Non-Commercial License with the Apache License, Version 2.0. Introduced a structured format with clear sections, definitions, rights grants, redistribution conditions, disclaimers, and contribution terms.
LICENSE_FAQ.md	Removed the file which detailed the Evmos Non-Commercial License (ENCL-1.0), its usage limitations, and related FAQ information.
README.md	Removed sections related to the roadmap and partnership details, including future development plans and partnership onboarding information.

Suggested reviewers

• Vvaradinov
• 0xstepit

Poem

I'm just a hopping rabbit, with whiskers all a-twitch,
Celebrating changes in our docs with a joyful little glitch.
The license now blooms with clauses bold and bright,
And old FAQs have hopped away into the night.
Here's a carrot of code in a field so green and free,
Hop along with Apache — a bright new destiny!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 d2cab8a and 1eda420.

📒 Files selected for processing (3)

• LICENSE (1 hunks)
• LICENSE_FAQ.md (0 hunks)
• README.md (0 hunks)

💤 Files with no reviewable changes (2)

• LICENSE_FAQ.md
• README.md

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Summary

🔇 Additional comments (12)

LICENSE (12)

1-6: License Header and Introduction
The header correctly identifies the Apache License, Version 2.0 and provides the pertinent title, version date, and URL. The introductory text ("TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION") is also in place to properly signal the start of the license terms.

---

7-65: Definitions Section: Well-Structured and Informative
The definitions are comprehensive and clearly mirror the standard Apache 2.0 License terminology. Each term (e.g., "License," "Licensor," "Legal Entity," etc.) is clearly defined, minimizing ambiguity for future readers and ensuring full compliance with Apache standards.

---

66-72: Grant of Copyright License
This section effectively grants a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license. The phrasing is precise and adheres exactly to the Apache License requirements.

---

73-88: Grant of Patent License: Clear and Comprehensive
The patent grant is articulated in a manner consistent with the Apache License, ensuring that contributors extend a perpetual, royalty-free patent license. This protects both the licensors and users against patent litigation based on the contributions.

---

89-128: Redistribution Conditions: Clear and Complete
The redistribution clause meticulously outlines the conditions under which the work or derivative works may be distributed. Requirements such as providing a copy of the license, maintaining notices, and including a NOTICE file (when applicable) are all well-covered and align with standard expectations.

---

130-137: Submission of Contributions: Standard Practice Enforcement
This section ensures that any submitted contributions automatically fall under the Apache License, which is typical for open-source projects adopting this license. The clause is succinct and maintains consistency with common practices for open-source contribution policies.

---

138-142: Trademarks Section: Adequate Limitations
The trademarks clause correctly restricts the use of the Licensor’s names, trademarks, and related marks. This limitation is important to prevent misleading representations and is in line with the expectations of Apache License provisions.

---

143-152: Disclaimer of Warranty: Clear and Unambiguous
The disclaimer is critical in establishing that the provided software comes "AS IS," without any warranties. It clearly disclaims express and implied warranties, protecting all parties involved, which is fully consistent with the Apache License.

---

153-163: Limitation of Liability: Well-Defined Protections
This section specifies the boundaries of liability for contributors by excluding any liability for a wide range of damages. The language is thorough and mirrors the language used in the standard Apache License, ensuring adequate legal protection.

---

165-174: Accepting Warranty or Additional Liability: Appropriate Conditions
By outlining the conditions under which a fee-based acceptance of additional liability may occur, this section ensures that anyone assuming further responsibilities does so entirely on their own initiative. The verbiage here is both precise and compliant with Apache standards.

---

178-188: Appendix: Application Guidance
The appendix provides clear, actionable guidance on how to apply the Apache License to a work. This additional documentation can help ensure that any reuse or adaptation of the license includes all necessary attribution and formatting, thereby aiding compliance.

---

189-202: License Notice and Copyright
The final block includes the necessary copyright notices and reiterates the license terms. Before finalizing, please verify that the copyright statements (e.g., "Copyright Evmos Authors" and "Copyright 2025, Tharsis Labs Ltd.") accurately represent the legal entities involved.

---

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

🪧 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 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.