andrew-blake/melcloudhome - Open Source PR Review Scorecard

MELCloudHome - Home Assistant Integration

C-Rank Grade: A (Welcoming) - 69/100

External PR Merge Rate: 93%

Response Time: 2d

First Timer Success: 67%

Frequently Asked Questions

Is andrew-blake/melcloudhome welcoming to first-time open-source contributors?

andrew-blake/melcloudhome 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.

How fast can I expect code review feedback on my pull request?

Maintainers in andrew-blake/melcloudhome respond to incoming external pull requests in approximately 52.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 68.7 C-Rank™ score (A Tier) represent?

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 68.7 places andrew-blake/melcloudhome in the A tier.

What is the external contributor pull request merge rate for andrew-blake/melcloudhome?

The external contributor pull request merge rate for andrew-blake/melcloudhome is 92.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in andrew-blake/melcloudhome?

andrew-blake/melcloudhome currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

andrew-blake
andrew-blake/melcloudhomeAWelcoming133
GitHub
Back to Explorer
andrew-blake

andrew-blake/melcloudhome

133
AWelcoming(69/100)Python

MELCloudHome - Home Assistant Integration

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
35%

Highly welcoming maintainers in andrew-blake/melcloudhome. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • Ensure code complies with the project coding style
  • Keep PRs scoped to a single concern
  • Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • Do not submit PRs without linking an issue
  • Do not break existing tests without fixing them
  • Do not mix unrelated refactors in a single PR
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
92.9%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
92.9%
Merge Gauge
66.7%
1st-Timer
Community Vibe57/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for andrew-blake/melcloudhome
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/andrew-blake/melcloudhome)](https://getmerged.abhishekco.de/andrew-blake/melcloudhome?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Motivation Same core-parity gap as frost/overheat/holiday-mode (see the sibling issue in this folder) — HA core's melcloud_home integration has standby-mode binary sensors on both ATA and ATW. We have none, despite full write support already being built for ATW. Current state — ATW Fully built, completely unused: custom_components/melcloudhome/api/client_atw.py: set_standby_mode() custom_components/melcloudhome/control_client_atw.py: async_set_standby_mode() custom_components/melcloudhome/coordinator.py: async_set_standby_mode() in_standby_mode is parsed into ATWUnitData (models_atw.py) but nothing reads it. No switch, binary_sensor, or HA service calls any of the above today — it's dead code sitting behind zero UI surface. Current state — ATA Read-only: in_standby_mode field and a has_standby capability flag are parsed (models_ata.py), no write path exists in the client. Proposal ATW: add a switch entity wired to the existing coordinator.async_set_standby_mode(). Note the c

📅 Opened Jul 22, 2026💬 3 comments
Quality: 90/100Contribute

MELCloud Home now has Italian support thanks to @sginestrini. If you'd like to add your language, it's a simple contribution — no coding required. How to contribute Copy en.json to a new file named <language-code>.json (e.g. pl.json, da.json) Translate the values (leave the keys unchanged) Open a PR See the Italian translation as a reference. Status Language Code Status Czech cs 🙏 Wanted Danish da 🙏 Wanted Dutch nl ✅ v2.3.0 English en ✅ Built-in Finnish fi ✅ v2.2.3 French fr ✅ v2.3.0 German de ✅ v2.2.3 Greek el ✅ v2.3.2 Hungarian hu 🙏 Wanted Italian it ✅ v2.2.2 Norwegian nb ✅ v2.4.1 Polish pl 🙏 Wanted Portuguese pt ✅ v2.2.3 Sinhala si 🙏 Wanted Spanish es ✅ v2.2.4 Swedish sv ✅ v2.2.5 Thai th ✅ v2.2.3 Turkish tr ✅ v2.3.0 Vietnamese vi ✅ v2.3.3 Comment below to claim a language before starting — to avoid duplicate effort.

📅 Opened Apr 2, 2026💬 10 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for andrew-blake/melcloudhome

When evaluating whether to contribute to andrew-blake/melcloudhome, 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 andrew-blake/melcloudhome acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.9% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to andrew-blake/melcloudhome

01

Is andrew-blake/melcloudhome welcoming to first-time open-source contributors?

andrew-blake/melcloudhome 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 68.7 C-Rank™ score represent?

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 68.7 places andrew-blake/melcloudhome in the Welcoming tier.

04

What is the external contributor pull request merge rate for andrew-blake/melcloudhome?

The external pull request merge rate is 92.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in andrew-blake/melcloudhome?

Yes, andrew-blake/melcloudhome currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for andrew-blake/melcloudhome 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.