feat: add adopters info

[Nils98Ar]

No description provided.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[gemini-code-assist]

Summary of Changes

Hello @Nils98Ar, 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 mechanism to showcase organizations that have adopted the hosted control plane. By adding a dedicated ADOPTERS.md file and linking it from the main README.md, the project aims to foster community engagement and provide transparency regarding its real-world usage. This change makes it easier for current and potential users to see who is leveraging the technology and encourages contributions to expand this list.

Highlights

• New Adopters Documentation: Introduced a new ADOPTERS.md file to list companies utilizing the hosted control plane, providing a structured format for contributions.
• README Update: Added a new section to README.md that directs users to the newly created ADOPTERS.md file, enhancing discoverability of adopters.

Changelog

• ADOPTERS.md
  • Added a new Markdown file to serve as a directory for companies adopting the hosted control plane.
  • Included a template table for listing adopters with fields like Type, Name, Since, Website, and Use-Case.
  • Defined different adopter types: End-user, Integration, Vendor, and R&D.
• README.md
  • Inserted a new "Who is using Hosted Control Plane?" section.
  • Added a link within this new section that points to the ADOPTERS.md file.

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

The pull request introduces an ADOPTERS.md file to track organizations using the project and updates the README.md to link to it. The feedback focuses on improving grammatical accuracy, ensuring consistent terminology (HCP) and phrasing ('The organization'), and following standard file formatting practices.

[gemini-code-assist]

For consistency with the rest of the project's documentation and acronym usage, 'hcp' should be capitalized as 'HCP'.

Suggested change

	**End-user**: The organization runs hcp in production in some way.
	**Integration**: The organization has a product that integrates with hcp, but does not contain hcp.
	**Vendor**: The organization packages hcp in their product and sells it as part of their product.
	**End-user**: The organization runs HCP in production in some way.
	**Integration**: The organization has a product that integrates with HCP, but does not contain HCP.
	**Vendor**: The organization packages HCP in their product and sells it as part of their product.

[gemini-code-assist]

This line contains a grammatical error ('that exploring'), an extra space, and uses 'Company' instead of 'The organization' (which is used in the other definitions). Additionally, it is recommended to end the file with a newline character.

Suggested change

	**R&D**: Company that exploring innovative technologies and solutions for research and development purposes.
	**R&D**: The organization explores innovative technologies and solutions for research and development purposes.