A collection of GTK4-based desktop components designed for Wayfire and Wlroots desktops
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 81%
Response Time: -
First Timer Success: 83%
WayfireWM/wf-shell has a recorded first-timer success rate of 83.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WayfireWM/wf-shell respond to incoming external pull requests in approximately 0.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 65.4 places WayfireWM/wf-shell in the A tier.
The external contributor pull request merge rate for WayfireWM/wf-shell is 80.9%, based on public PR activity from non-core contributors.
WayfireWM/wf-shell currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in WayfireWM/wf-shell. Prompt code reviews with positive guidance for new contributors.
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/WayfireWM/wf-shell?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 Tuesday - Thursday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
Doing MCCS operations with ddcutil takes a bit of time, which is the reason that writing and reading operations are done on other threads. However, initialisation is done on the main thread, which causes panel startup to be quite slow if using the widget. Doing the initialisation and enumeration on another thread would be pretty nice for that situation.
Summary Currently, when certain audio categories are empty (e.g., no input devices connected or no active media streams playing), both wf-panel (Volume Mixer popup) and wf-locker (Volume widget) render empty, blank UI containers without feedback or adaptivity. Proposal & Desired Behavior 1. wf-panel Volume Mixer Popup In the Volume Mixer popup (which consists of three columns: Output Devices, Input Devices, and Audio Streams): Empty Input/Output Devices: If no input (or output) devices are available, display a clear label in the respective column: "No available output devices" / "Нет доступных устройств вывода" "No available input devices" / "Нет доступных устройств ввода" Empty Audio Streams: If no audio streams/apps are playing: Display a label like "No active playback" / "Ничего не воспроизводится". Currently, the "Input Devices" heading is shown with a completely empty box underneath, which looks b
As seen on #530, the ci (and most users) uses GCC, it would be a good idea to test for clang as well. Could also test with glibc along with musl. With #511, i am also wondering if we should have a list of supported versions that are tested for ? but that would probably be way, way too overkill
The mixer currently supports scrolling up on a control to get volumes higher than 100%, but it would be nice to have a toggle in the mixer to adapt the scales to an above-100 maximum.
This layout would put each category in it's own page of a gtk notebook. It would be particularly well adapted to devices with smaller/vertical screens.
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 WayfireWM/wf-shell, 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 WayfireWM/wf-shell acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.9% were successfully merged into the primary branch.
WayfireWM/wf-shell has a recorded first-timer success rate of 83.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 65.4 places WayfireWM/wf-shell in the Welcoming tier.
The external pull request merge rate is 80.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WayfireWM/wf-shell currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for WayfireWM/wf-shell 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.