Vitruvian is the human-centric Operating System.
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 22%
Response Time: -
First Timer Success: -
VitruvianOS/Vitruvian has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in VitruvianOS/Vitruvian 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 52.3 places VitruvianOS/Vitruvian in the B tier.
The external contributor pull request merge rate for VitruvianOS/Vitruvian is 22.2%, based on public PR activity from non-core contributors.
VitruvianOS/Vitruvian currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in VitruvianOS/Vitruvian 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/VitruvianOS/Vitruvian?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (28% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
The cppunit testing framework we inherited from Haiku is...dubious at best, bogus on average, garbage in many cases. There's definitely stuff to save, but, considering our changes and adaptions we almost certaily want to rewrite half of them and rework the other half. It's probably better to have less of them but good quality tests so I'd propose to just start from scratch.
the storage layer should be already designed to support NFS volumes natively in Tracker just like they were local partitions, but, can't bet there are no surprises. So it needs some testing at some point.
But we need the haiku fork though: https://github.com/haiku/buildtools/tree/master/jam We'll probably be putting it in src/tools/ I guess
The BONE update to BeOS R5 had a nice preflet that allowed to setup services on the machine (mini http server, ssh, ftp etc). With systemd it should be trivial to build something like that.
If I'm not wrong (but double check that) on linux the cp command and potentially other binutils don't copy xattrs. This is a bit of a problem as BeOS does that. The command (cp) can however copy attrs if a flag is passed. We have two options Patch binutils (seems too much work for the gain, unless you have a good reason to do so) Define a cp alias (and check for other binutils that might need it) so that the flag to copy attributes is passed.
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 VitruvianOS/Vitruvian, 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 VitruvianOS/Vitruvian acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 22.2% were successfully merged into the primary branch.
VitruvianOS/Vitruvian has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 52.3 places VitruvianOS/Vitruvian in the Solid tier.
The external pull request merge rate is 22.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, VitruvianOS/Vitruvian 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 VitruvianOS/Vitruvian 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.