Dynamically provision Stateful Persistent Replicated Cluster-wide Fabric Volumes & Filesystems for Kubernetes that is provisioned from an optimized NVME SPDK backend data storage stack.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 76%
Response Time: 11h
First Timer Success: 67%
openebs/mayastor has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openebs/mayastor respond to incoming external pull requests in approximately 11.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.8 places openebs/mayastor in the A tier.
The external contributor pull request merge rate for openebs/mayastor is 76.0%, based on public PR activity from non-core contributors.
openebs/mayastor currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/openebs/mayastor?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Is your feature request related to a problem? Please describe. The helm chart today deploys a single io-engine daemonset. This means the configuration is shared across all nodes. I've seen in the wild folks modify the chart to deploy separate daemonsets, which is far from ideal and error prone, potentially. Why is this a problem? Let's think about cpu binding - currently all nodes in the daemonset would inherit the same exact configuration, meaning you'd only be able to set all the nodes to bind to the same. Describe the solution you'd like I'd like to see a way to configure different sets of nodes, in a flexible way to allow fully changing all node attributes. Describe alternatives you've considered We could achieve some parts of this by using a configmap for example, and having a per-node or per-group key containing all the configuration. This solves part of the problem, but doesn't allow for having custom options for huge page type or amount of resource limits/requests. Additional c
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to openebs/mayastor, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of openebs/mayastor acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.0% were successfully merged into the primary branch.
openebs/mayastor has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.8 places openebs/mayastor in the Welcoming tier.
The external pull request merge rate is 76.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openebs/mayastor currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for openebs/mayastor are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.