Add Elastic License 2.0 with commercial exceptions

[dgellow]

Adds ELv2 license, allowing self-hosting and modifications. Includes commercial exceptions for Stainless Software Ltd and the author (Samuel El-Borai).

[gemini-code-assist]

Summary of Changes

Hello @dgellow, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new licensing framework for the mcp-front project by implementing the Elastic License 2.0 (ELv2). The core intent is to protect the software from being offered as a competing hosted service by cloud providers, while still enabling self-hosting, modifications, and internal commercial use. The update also includes explicit commercial exceptions for key contributors, ensuring a balanced approach to openness and sustainability.

Highlights

• New Licensing Model: The project now adopts the Elastic License 2.0 (ELv2) to govern its usage and distribution.
• Protection Against Hosted Services: The ELv2 specifically prevents third-party cloud providers from offering mcp-front as a hosted or managed service.
• Permitted Usage: Users are still allowed to self-host, modify, and use the software for their internal commercial purposes.
• Commercial Exceptions: Specific entities, Stainless Software Ltd and the author Samuel El-Borai, are granted full commercial rights without the limitations imposed by the ELv2.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces the Elastic License 2.0 with commercial exceptions for the project. The changes include adding the new LICENSE file, updating the README, and adding a new license page to the documentation site. The implementation is straightforward and aligns with the PR's goal. My review focuses on improving the consistency of the copyright notices across the modified files to ensure legal clarity.

[dgellow]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces the Elastic License 2.0 for the project, along with commercial exceptions for specific parties. The changes include adding the LICENSE file, updating the README.md, and adding a new license page to the documentation site. The changes are well-structured and clearly communicate the new licensing terms. I've made a couple of suggestions to improve consistency across the different files where the license is mentioned, specifically regarding the commercial exceptions.