Cluster API Provider for Proxmox VE (CAPMOX)
C-Rank Grade: A (Welcoming) - 55/100
External PR Merge Rate: 21%
Response Time: 2d
First Timer Success: 33%
ionos-cloud/cluster-api-provider-proxmox has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ionos-cloud/cluster-api-provider-proxmox respond to incoming external pull requests in approximately 45.9 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 55.3 places ionos-cloud/cluster-api-provider-proxmox in the A tier.
The external contributor pull request merge rate for ionos-cloud/cluster-api-provider-proxmox is 21.4%, based on public PR activity from non-core contributors.
ionos-cloud/cluster-api-provider-proxmox currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in ionos-cloud/cluster-api-provider-proxmox. Reviews community pull requests with focus on project quality.
Discussions in ionos-cloud/cluster-api-provider-proxmox focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/ionos-cloud/cluster-api-provider-proxmox?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (27% approval). Large PRs (>500 lines) take ~220 hours (15% approval). Keep your diff compact for rapid review.
Describe the solution you'd like We use go text/template to render yaml for cloudinit/netplan and then validate it through yaml parsing. This is nonsensical, we can make yaml directly and then marshal it. This approach is cleaner and more flexible. Anything else you would like to add: Depending on how deep we go, ignition can either live off of the yaml or get its own structured ini creation. Environment: Does not apply.
Since tests do not actually connect to any hosts and only check if the addresses are correctly set, it would make sense to convert the IP addresses that they use to the RFC3849 and RFC5739 documentation ranges. This would have the benefit that tests don't accidentally connect to any real hosts. It also comes up in SonarQube.
As per title. It's a larger job that might seem, will need some care to replace it with something strictly better.
The capmoxerrors package was forked from CAPI's errors package (see discussion in #639) because CAPI plans to delete the errors package along with v1beta1. When v1beta1 is deleted, we can also drop v1alpha1, at which point capmoxerrors should be removed as well. Plan: When CAPI deletes its errors package and v1beta1, we migrate away from v1alpha1 in this provider. Once v1alpha1 is removed, delete capmoxerrors (the forked package) entirely. References: #639 (discussion at #639 (comment))
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 ionos-cloud/cluster-api-provider-proxmox, 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 ionos-cloud/cluster-api-provider-proxmox acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 21.4% were successfully merged into the primary branch.
ionos-cloud/cluster-api-provider-proxmox has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 55.3 places ionos-cloud/cluster-api-provider-proxmox in the Welcoming tier.
The external pull request merge rate is 21.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ionos-cloud/cluster-api-provider-proxmox currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ionos-cloud/cluster-api-provider-proxmox 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.