Blog: Meshery Umbrella Expands #2139
Conversation
Signed-off-by: Lee Calcote <[email protected]>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @leecalcote, I'm Gemini Code Assist1! 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!
Summary of Changes
This pull request introduces a new blog post titled "Meshery Ecosystem Expansion". The post explains the purpose of the meshery-extensions GitHub organization, which is to host and manage community-contributed components related to the Meshery ecosystem, separate from the core Meshery project. It details the rationale behind this separation, including community ownership, scope and focus, provider ecosystem growth, incubation and experimentation, clearer support expectations, and governance.
Highlights
- New Blog Post: Adds a blog post explaining the purpose and rationale behind the
meshery-extensionsGitHub organization. - Community Focus: Highlights the importance of community contributions and maintenance within the Meshery ecosystem.
- Ecosystem Expansion: Explains how
meshery-extensionsfacilitates the growth of the Meshery ecosystem by providing a space for community-driven extensions and integrations.
Changelog
- collections/_posts/2025/04/18/2025-04-18-meshery-extensions-org.md
- Added a new blog post detailing the purpose of the
meshery-extensionsGitHub organization. - The blog post covers community ownership and maintenance of Meshery extensions.
- Explains the separation of concerns between the core Meshery project and community contributions.
- Discusses the role of
meshery-extensionsin fostering provider ecosystem growth. - Highlights the incubation and experimentation aspects of the
meshery-extensionsorganization. - Clarifies support expectations for community-contributed projects.
- Mentions the potential for different governance models within
meshery-extensions.
- Added a new blog post detailing the purpose of the
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 is currently in preview and 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 to provide feedback.
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.
In realms of code, where projects bloom,
Extensions rise, dispelling gloom.
A space to share,
Beyond compare,
Meshery's reach, escaping its room.
Footnotes
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request introduces a new blog post detailing the purpose and rationale behind the meshery-extensions GitHub organization. The post effectively communicates the separation of community-contributed extensions from the core Meshery project. The content is well-structured and informative.
Merge Readiness
The blog post is well-written and provides valuable information about the Meshery ecosystem. I recommend merging this pull request as it is. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.
✅ Deploy Preview for mesheryio-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…ation strategy, including rationale for repository partitioning, governance structure, and support expectations. Adjusted publication date from April 18 to April 17, 2025. Signed-off-by: Lee Calcote <[email protected]>
Signed-off-by: Lee Calcote <[email protected]>
…ory partitioning and adding a section on project architecture, emphasizing the extensibility of the platform. Signed-off-by: Lee Calcote <[email protected]>
…larity in the Ecosystem Growth section, and adding a new section on reflections regarding other CNCF projects, emphasizing the benefits of repository separation and autonomy for extension teams. Signed-off-by: Lee Calcote <[email protected]>
ritzorama
requested review from
a team,
MarioArriaga92,
Revolyssup and
nebula-aac
and removed request for
a team
|
|
||
| ### Scalability | ||
|
|
||
| As Meshery supports over 300 integrations and continues to grow, the number of extensions is expected to increase. Managing these within a single organization could become unwieldy. A separate organization for extensions simplifies permission management, contribution processes, and release cycles, making the ecosystem more scalable. **Community Ownership and Maintenance:** Projects within `meshery-extensions` are generally initiated, developed, and maintained by members of the wider Meshery community, rather than the core Meshery maintainers. This allows the ecosystem to scale beyond what the core team can directly support. **Clearer Support Expectations:** Separating community contributions makes it clearer that projects in `meshery-extensions` might have different maintenance levels, release cadences, and support guarantees compared to the core Meshery components. Users understand they are relying on community support for these specific integrations. |
There was a problem hiding this comment.
As Meshery supports over 300 integrations and continues to grow, the number of extensions is expected to increase. Managing these within a single organization could become unwieldy. A separate organization for extensions simplifies permission management, contribution processes, and release cycles, making the ecosystem more scalable.
Community Ownership and Maintenance: Projects within meshery-extensions are generally initiated, developed, and maintained by members of the wider Meshery community, rather than the core Meshery maintainers. This allows the ecosystem to scale beyond what the core team can directly support.
Clearer Support Expectations: Separating community contributions makes it clearer that projects in meshery-extensions might have different maintenance levels, release cadences, and support guarantees compared to the core Meshery components. Users understand they are relying on community support for these specific integrations.
|
|
||
| ### Crossplane | ||
|
|
||
| Crossplane’s separation of github.com/crossplane and github.com/crossplane-contrib facilitates a clear distinction between the core platform and community contributions. Providers and functions in the contrib organization allow third-party developers to extend Crossplane’s capabilities without impacting core stability. This model supports Meshery’s approach by demonstrating how a separate organization can foster innovation while maintaining a reliable core. |
There was a problem hiding this comment.
Crossplane’s separation of github.com/crossplane and github.com/crossplane-contrib facilitates a clear distinction between the core platform and community contributions. Providers and functions in the contrib organization allow third-party developers to extend Crossplane’s capabilities without impacting core stability. This model supports Meshery’s approach by demonstrating how a separate organization can foster innovation while maintaining a reliable core.
|
|
||
| ### Kubernetes | ||
|
|
||
| Kubernetes’ use of github.com/kubernetes for core components and github.com/kubernetes-sigs for SIGs provides a robust model for decentralized governance. Each SIG operates as a mini-community with its own charter, leadership, and processes, yet aligns with overarching project goals (Kubernetes SIGs). Meshery’s extension organization can adopt a similar approach, allowing extension teams to function autonomously within defined guidelines. |
There was a problem hiding this comment.
Kubernetes’ use of github.com/kubernetes for core components and github.com/kubernetes-sigs for SIGs provides a robust model for decentralized governance. Each SIG operates as a mini-community with its own charter, leadership, and processes, yet aligns with overarching project goals (Kubernetes SIGs). Meshery’s extension organization can adopt a similar approach, allowing extension teams to function autonomously within defined guidelines.
|
|
||
| ## Reflections on Other Projects | ||
|
|
||
| Meshery's expansion strategy mirrors successful models in other CNCF projects. BuildPacks and Argo https://github.com/argoproj-labs. Crossplane uses github.com/crossplane for its core platform and github.com/crossplane-contrib for community-contributed providers and functions. Similarly, Kubernetes maintains github.com/kubernetes for core components and github.com/kubernetes-sigs for Special Interest Groups (SIGs). These separations enable focused development, decentralized governance, and easier contribution, which Meshery aims to emulate. |
There was a problem hiding this comment.
This part appears repeated, we have the same below as well.
Signed-off-by: Lee Calcote [email protected]
Preview: https://deploy-preview-2139--mesheryio-preview.netlify.app/blog/2025/meshery-ecosystem-expansion