A trackpad-first infinite canvas Wayland compositor.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 81%
Response Time: 9d
First Timer Success: 77%
malbiruk/driftwm has a recorded first-timer success rate of 76.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in malbiruk/driftwm respond to incoming external pull requests in approximately 226.6 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 62.2 places malbiruk/driftwm in the A tier.
The external contributor pull request merge rate for malbiruk/driftwm is 80.8%, based on public PR activity from non-core contributors.
malbiruk/driftwm currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in malbiruk/driftwm. Maintains strict focus on technical quality and test standards.
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/malbiruk/driftwm?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~147 hours (96% approval). Large PRs (>500 lines) take ~1087 hours (36% approval). Keep your diff compact for rapid review.
Follow-up to #178, which lands multi-GPU (PRIME) support but skips blur on outputs driven by a secondary GPU. That's graceful degradation (secondary-output windows render without blur), documented in #178 as though smithay can't do it — but it can. This is a not-yet-implemented feature, not a structural limitation. niri implements exactly this today. Mechanism Effects run on the primary render GlesRenderer — obtained via MultiRenderer::as_mut(), exposed in-tree as as_gles_renderer() — the result is wrapped as a primary-GPU texture element, and MultiFrame::finish() PRIME-copies the composited frame to the scanout GPU. The target/scanout GPU's renderer is never touched. Already wired in #178 Cross-GPU frames composite on the primary via gpu_manager.renderer(primary, target, fmt). The Kawase blur passes already run on the primary through renderer.as_gles_renderer(). The blurred result is already inserted as GlesBridge(blur_elem), drawing via as_gles_frame() + record_bridged_damage
Hiya. The project's real cool, I appreciate ya, mate. Yet I spotted a slightly bitter thing: my second monitor doesn't work, and the HDMI port of the laptop is routed to the NVIDIA dGPU. I'm certain I set up the config right, so I don't understand what's wrong. Laptop model: Lenovo IdeaPad Gaming 3 15ARH05 GPUs: AMD Radeon Renoir iGPU + GTX 1650 Ti Mobile dGPU Monitor configs: [[outputs]] name = "eDP-1" scale = 1 transform = "normal" position = [0, 0] mode = "1920x1080@120" [[outputs]] name = "HDMI-A-1" scale = 1 transform = "normal" position = [1920, 0] mode = "1280x1024@75" ED: Seems like it can't access my dGPU, for some reason - throws the 'permission denied' error
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 malbiruk/driftwm, 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 malbiruk/driftwm acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.8% were successfully merged into the primary branch.
malbiruk/driftwm has a recorded first-timer success rate of 76.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 62.2 places malbiruk/driftwm in the Welcoming tier.
The external pull request merge rate is 80.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, malbiruk/driftwm currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for malbiruk/driftwm 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.