meshery/meshery-operator
Meshery Operator is a Kubernetes Operator that deploys and manages the lifecycle of two Meshery components critical to Meshery's operations of Kubernetes clusters
In plain words
Outside PRs: 8 in 10 merged. First reply usually within 13 days.
Outside PRs merged
75%
9 merged, 3 closed, 1 still open
Higher than 31% of 565 other measured repositories
First human reply
13 days
median of 13 outside PRs, 5 unanswered
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's forum, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. A first reply here usually takes 13 days; until then, silence is normal.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders13100%
- Got a human reply862%
- Merged969%
Time to first reply
After 2 days, 31% of outside PRs had a reply from a person. After a week, 46%. Bots do not count.
The last 52 weeks
Outside pull requests opened each week, and how many of them have been merged.
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
No open issue carries a beginner label.
Issue replies: first human reply in 2.5 days (median of 18 issues).
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 10:00 and 13:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 0 |
| 01:00 | 0 |
| 02:00 | 0 |
| 03:00 | 0 |
| 04:00 | 1 |
| 05:00 | 1 |
| 06:00 | 0 |
| 07:00 | 0 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 2 |
| 11:00 | 2 |
| 12:00 | 1 |
| 13:00 | 0 |
| 14:00 | 0 |
| 15:00 | 0 |
| 16:00 | 0 |
| 17:00 | 0 |
| 18:00 | 0 |
| 19:00 | 0 |
| 20:00 | 0 |
| 21:00 | 0 |
| 22:00 | 0 |
| 23:00 | 0 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 89
- Releases, 12 months
- 6
- Active maintainers
- 12
- Last push
- 21 Sep 2026
Stack
Badge and feed
Two ways to use these figures outside this page.
For maintainers: a README badge
Shows newcomers how quickly this project answers and how often it merges. Paste the line into your README; the badge updates with the index.
[](https://contributable.vercel.app/repo/meshery/meshery-operator)[](https://contributable.vercel.app/repo/meshery/meshery-operator)For contributors: follow new issues
Add the feed to a feed reader (Feedly, Inoreader, Thunderbird) and you hear about new free starter issues here without checking the site.
https://contributable.vercel.app/feed/repo/meshery/meshery-operatorFor developers: every figure on this page as JSON at /api/v1/repos/meshery/meshery-operator.
Similar repositories
Same main language (Go), most shared frameworks and topics first, then the faster reply.
Common microservices framework for Meshery components
- First reply
- 3.2 days
