Home Assistant integration framework for (garbage collection) schedules
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 64%
Response Time: 4h
First Timer Success: 58%
mampfes/hacs_waste_collection_schedule has a recorded first-timer success rate of 58.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mampfes/hacs_waste_collection_schedule respond to incoming external pull requests in approximately 4.5 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 70.7 places mampfes/hacs_waste_collection_schedule in the S tier.
The external contributor pull request merge rate for mampfes/hacs_waste_collection_schedule is 64.1%, based on public PR activity from non-core contributors.
mampfes/hacs_waste_collection_schedule currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in mampfes/hacs_waste_collection_schedule welcoming community pull requests and bug fixes.
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/mampfes/hacs_waste_collection_schedule?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (80% approval). Large PRs (>500 lines) take ~21 hours (29% approval). Keep your diff compact for rapid review.
Follow-up to #6519, which added Dutch (nl) to the translation/howto generation pipeline. That PR only wired nl through the pipeline. The Dutch content itself is still a placeholder and needs a proper translation: default_translations.py: DEFAULT_PARAM_TRANSLATIONS["nl"] and DEFAULT_PARAM_DESCRIPTIONS["nl"] are initialized from the English defaults. custom_components/waste_collection_schedule/translations/nl.json: hand-maintained parts (e.g. options.step.init) and the config-flow strings need review by a native speaker. The args_* sections are generated by update_docu_links.py. Sources with Dutch users can add nl keys to their PARAM_TRANSLATIONS, PARAM_DESCRIPTIONS and HOW_TO_GET_ARGUMENTS_DESCRIPTION. To do Translate DEFAULT_PARAM_TRANSLATIONS["nl"] and DEFAULT_PARAM_DESCRIPTIONS["nl"] into Dutch Review and translate translations/nl.json (hand-maintained sections) Add nl translations to sources where useful (especially Dutch providers) Help from native Dutch speakers is very wel
Municipality / Region Spain, Andalusia Collection Calendar Webpage https://transparencia.epremasa.es/wp-content/uploads/2026/03/Datos-web-area-gestion-Usurarios-actualizados-ejerc-2026.pdf Example Address Test street 00, Piconcillo, Spain Data Format PDF download only Known Platform (if any) Not sure / Unknown Additional Information I cannot find a normal calendar, but it is pretty simple to understand it if we would find some.... Checklist I have searched the source list and my provider is not already supported I have provided a working example address (not my own) for testing I have tried to implement this myself (or with a free coding agent like Claude or Copilot, following AGENTS.md)
Municipality / Region San Martino di Lupari, Padova, Italy Collection Calendar Webpage https://www.etraspa.it/sites/etraspa.it/files/SMartinoLupariA4_2Z_2026.pdf Example Address zone B Data Format Other (describe in additional information) Known Platform (if any) Other known platform (describe in additional information) Additional Information Website has a PDF, while you can get the schedule on EtraRifiuti app: municipality and "zone" must be input to get the right schedule. Thanks! Checklist I have searched the source list and my provider is not already supported I have provided a working example address (not my own) for testing
Municipality / Region Otterburn park, QC, CANADA Collection Calendar Webpage https://www.mrcvr.ca/wp-content/uploads/2026/03/Calendrier_collectes_2026_Otterburn_Park.pdf Example Address 601, chemin Ozias-Leduc Otterburn Park, Québec J3H 2M6 Data Format PDF download only Known Platform (if any) Not sure / Unknown Additional Information No response Checklist I have searched the source list and my provider is not already supported I have provided a working example address (not my own) for testing
Municipality / Region Switzerland Collection Calendar Webpage https://www.bremgarten.ch/_docn/6394274/Recycling-_und_Terminkalender_2026.pdf Example Address Am Bogen 10, 5620 Bremgarten Data Format PDF download only Known Platform (if any) Not sure / Unknown Additional Information No response Checklist I have searched the source list and my provider is not already supported I have provided a working example address (not my own) for testing
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 mampfes/hacs_waste_collection_schedule, 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 mampfes/hacs_waste_collection_schedule acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.1% were successfully merged into the primary branch.
mampfes/hacs_waste_collection_schedule has a recorded first-timer success rate of 58.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 70.7 places mampfes/hacs_waste_collection_schedule in the Elite tier.
The external pull request merge rate is 64.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mampfes/hacs_waste_collection_schedule currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for mampfes/hacs_waste_collection_schedule 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.