System Software for Z80/Z180/Z280 Computers
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 92%
Response Time: 2h
First Timer Success: 100%
wwarthen/RomWBW has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in wwarthen/RomWBW respond to incoming external pull requests in approximately 1.8 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 67.3 places wwarthen/RomWBW in the A tier.
The external contributor pull request merge rate for wwarthen/RomWBW is 91.7%, based on public PR activity from non-core contributors.
wwarthen/RomWBW currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
System Software for Z80/Z180/Z280 Computers
Active maintainer team in wwarthen/RomWBW 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/wwarthen/RomWBW?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 Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (41% approval). Keep your diff compact for rapid review.
I have been investigating an issue with the UCSD p-System IV.0 distribution included with RomWBW, using a ZETA V2 system. The standard p-System boots and operates correctly. While adding original UCSD BASIC and FORTRAN IV.0 compilers, I found that both compilers successfully generate code, but even trivial compiled programs fail immediately at runtime with: Unimplemented instruction Segment REALOPS Proc# 14 Offset# 73 This occurs even with a BASIC program containing only: 10 END A minimal FORTRAN program produces the same REALOPS error. We investigated the RomWBW p-System distribution and found that SYSTEM.INTERP is based on INTERP.Z.CODE. The distribution contains INTERP.Z.CODE, RSP.CODE, BIOS.CRP.CODE, INTER.X.CODE and TERTBOOT.CODE, but no FP0.CODE, FP2.Z.CODE or FP4.CODE. According to the SofTech p-System IV.0 adaptable-system documentation, floating-point support is supplied separately when configuring the interpreter. For a Z80 system using four-word REALs, the expected configura
Here is a debug from zsid (register E is set with 53, but the line got cut off) B=01, C=00, E=53 #ta ----I A=53 B=0053 D=0053 H=1780 S=0EB2 P=175F ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD C,00 ----I A=53 B=0000 D=0053 H=1780 S=0EB2 P=1761 ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD B,01 ----I A=53 B=0100 D=0053 H=1780 S=0EB2 P=1763 ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 CALL FFF0 ----I A=53 B=0100 D=0053 H=1780 S=0EB0 P=FFF0 ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 JP FE04 ----I A=53 B=0100 D=0053 H=1780 S=0EB0 P=FE04 ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD (FE28),SP ----I A=53 B=0100 D=0053 H=1780 S=0EB0 P=FE08 ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD SP,FFE0 ----I A=53 B=0100 D=0053 H=1780 S=FFE0 P=FE0B ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD A,(FFE0) ----I A=8E B=0100 D=0053 H=1780 S=FFE0 P=FE0E ----- A'00 B'0000 D'0000 H'0000 X=0000 Y=0000 LD (FFE1),A ----I A=8E B=0100 D=0053 H=1780 S=FFE0 P=FE11 ---
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 wwarthen/RomWBW, 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 wwarthen/RomWBW acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.7% were successfully merged into the primary branch.
wwarthen/RomWBW has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 67.3 places wwarthen/RomWBW in the Welcoming tier.
The external pull request merge rate is 91.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, wwarthen/RomWBW currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for wwarthen/RomWBW 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.