On Mar 4, 2025, at 12:34 AM, Lee Calcote <lee.c...@layer5.io> wrote:Hi All,In the past, Meshery has been referred to as a service mesh manager, however, that is only a small component of what Meshery does. Any longer, outside of its long list of service mesh-centric adapters, Meshery offers no special consideration to service meshes than it does the other 300+ technologies with which it integrates.While blog “Meshery is not a Service Mesh Manager" offers additional context, suffice to say that many people still perceive Meshery with a service mesh-centric connotation. This has long plagued the project, undercutting its much larger value offering to would-be users that otherwise skip past Meshery because of this misperception.While “service mesh” as a term has been stripped and replaced with “cloud native infrastructure” in nearly all aspects of the project, the fact that 12 of the 33 repositories in the project are service mesh-related doesn’t help.Meshery extensions come in a number of different forms. Maintenance of Meshery adapters as a specific extension type have fallen to the wayside in the v0.7.x development timeframe with all of them currently being dysfunctional in one manner or another, leaving a bad taste in the mouths of users, who choose to deploy these optional extensions.The “meshery” GitHub organization currently has 33 repositories. The proposed GitHub organization is https://github.com/meshery-extensions. Each of the following 15 considered extensions and are proposed to be transferred to be moved to the extensions organization:
- meshery-cilium
- meshery-istio
- meshery-kuma
- meshery-nginx-sm
- meshery-consul
- meshery-nighthawk
- meshery-cpx
- meshery-app-mesh
- meshery-nsm
- meshery-tanzu-sm
- meshery-octarine
- meshery-osm
- helm-kanvas-snapshot
- kubectl-kanvas-snapshot
- kubectl-meshsync-snapshot
This organization and all of its repositories are to be donated to the CNCF; they are to be considered a direct part of the Meshery project, governed and stewarded in the same fashion that they are today, but as a separate organization, the hope is that:1. Users will not see Meshery as service mesh-centric.2. Contributors will see the greater opportunity (less daunting with a little more freedom) to extend Meshery as a platform with new adapters, plugins and so forth.This should not disrupt Meshery’s standing at the 9th highest velocity in the CNCF as the same statistics should continue to be accounted for under the same project umbrella even though the project is proposed to be split across two orgs.There are additional considerations to ponder and clarify under this proposed change, like whether all extensions should be kept in this separate organization, what criteria the project defines as extension adoption requirements (when someone/organization wants to donate a repo or requests that a new repo be created). There is soon to be a new section of the MAINTAINERS.md that identifies Meshery Extensions Maintainers.Even though all considerations aren’t accounted for in this initial proposal, I wanted to set the discussion in motion and begin soliciting your input as assuming that there is enough support for this proposal, we will eventually put it to a vote.Thank you for given this some thought. This will be a point of discussion in this week’s Meshery Development meeting. As you ponder this topic, here are two other project examples in which extensions are explicitly managed in orgs separate from the main project org: https://github.com/kubernetes-sigs and https://github.com/crossplane-contrib.Regards,Lee
+1 bindingI recommend waiting until post-KubeCon EU to relocate the adapter repos (assuming this proposal passes vote).- Lee
On Tuesday, March 25, 2025 at 5:28:14 PM UTC-5 Mia Grenell wrote:
Hi All,
I voted just a bit earlier today, but received rejected messages from
the mailing lists, so I'm resending my vote as a mail forward in the
hopes that whatever caused my other message not to go through isn't an
issue now.
My vote: +1 binding
I understand the reasoning behind this proposal and I am all for it. I agree.
Best,
Mia
_._,_._,_
Links:You receive all messages sent to this group.
View/Reply Online (#631) | Reply to Group | Reply to Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [lee.c...@layer5.io]
_._,_._,_
+1 Non BindingOn Wed, Mar 26, 2025 at 11:15 AM Aditya Raj <adityara...@gmail.com> wrote:+1 Non Binding 🚀
On Wed, 26 Mar, 2025, 1:11 pm Falgun Patel, <falgunmp...@gmail.com> wrote:+1 non-bindingOn Wednesday, 26 March 2025 at 10:16:35 UTC+5:30 Sangram Rath wrote:+1 binding
On Wednesday, March 26, 2025 at 7:31:07 AM UTC+5:30 lee.c...@layer5.io wrote:+1 bindingI recommend waiting until post-KubeCon EU to relocate the adapter repos (assuming this proposal passes vote).- LeeOn Tuesday, March 25, 2025 at 5:28:14 PM UTC-5 Mia Grenell wrote:Hi All,
I voted just a bit earlier today, but received rejected messages from
the mailing lists, so I'm resending my vote as a mail forward in the
hopes that whatever caused my other message not to go through isn't an
issue now.
My vote: +1 binding
I understand the reasoning behind this proposal and I am all for it. I agree.
Best,
Mia
----
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/5cf5d682-1ca5-4c6e-a639-39aed20250c1n%40meshery.io.
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.--To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAFJSahO1rUuFbYuK-5BnUyMmTfFpNGPaLRazPUyi4F9xiF8utA%40mail.gmail.com.
Visit and engage with the Meshery community in the forum at http://discuss.meshery.io or in Slack at https://slack.meshery.io.
---
You received this message because you are subscribed to the Google Groups "Meshery Maintainers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maintainers...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/maintainers/CADiAyJuNCgwhP2o9r72ysswb6F%2BLY%3DADHnX6vRSsVS%3DYOMK_VA%40mail.gmail.com.
+1 Non Binding 🚀
+1 non-binding
On Wednesday, 26 March 2025 at 10:16:35 UTC+5:30 Sangram Rath wrote:
+1 binding
On Wednesday, March 26, 2025 at 7:31:07 AM UTC+5:30 lee.c...@layer5.io wrote:
+1 bindingI recommend waiting until post-KubeCon EU to relocate the adapter repos (assuming this proposal passes vote).- LeeOn Tuesday, March 25, 2025 at 5:28:14 PM UTC-5 Mia Grenell wrote:Hi All,
I voted just a bit earlier today, but received rejected messages from
the mailing lists, so I'm resending my vote as a mail forward in the
hopes that whatever caused my other message not to go through isn't an
issue now.
My vote: +1 binding
I understand the reasoning behind this proposal and I am all for it. I agree.
Best,
Mia
--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/5cf5d682-1ca5-4c6e-a639-39aed20250c1n%40meshery.io.
+1 non-binding
I understand the reason why we are going to split meshery github org, even It can help in lot of ways . I totally agree upon on this.
- Deepak Reddy
+1 BindingBest,- Yash
On Wednesday, March 26, 2025 at 2:15:30 PM UTC+5:30 Daley Tinga wrote:
+1 Non Binding
On Wed, Mar 26, 2025 at 11:15 AM Aditya Raj <adityara...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/a6874a3b-d38e-4534-a7a6-32a84e96524cn%40meshery.io.
+1
+1 binding
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CANz7%2BQdpA-B-oVNVGSXndFUtdqYJRQZn94Hwsd1dGJqWFGj%3Dww%40mail.gmail.com.
+1
+1 binding
+1
+1 binding
--
Visit and engage with the Meshery community in the forum at https://discuss.layer5.io or in Slack at https://slack.layer5.io.
If you don't wish to receive emails, unsubscribe here - https://layer5.io/unsubscribe
---
You received this message because you are subscribed to the Google Groups "Meshery Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to community+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/community/CANS%3DiU9ESCqaR5rYZQHxfudq%3DqgG-0QG%2BV75brFS5S-ANso%2BfQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAGDeGGdS0ksotm_4hcS%3D%2BunmR%2BENX8jvzxj29H3LfYqZVV%2Bjqg%40mail.gmail.com.
--
Visit and engage with the Meshery community in the forum at http://discuss.meshery.io or in Slack at https://slack.meshery.io.
---
You received this message because you are subscribed to the Google Groups "Meshery Maintainers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maintainers...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/maintainers/CAGDeGGdS0ksotm_4hcS%3D%2BunmR%2BENX8jvzxj29H3LfYqZVV%2Bjqg%40mail.gmail.com.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/maintainers/CA%2BcBL2ixyB63uT3VmRy33U21CpNHZrgOwhBS7O-wZ1B8pDPeJw%40mail.gmail.com.
+1 binding
+1