jdolan/quetoo - Open Source PR Review Scorecard

Quetoo ("Q2") is a free first person shooter based on id Tech2. GPL v2 license.

C-Rank Grade: S (Elite) - 68/100

External PR Merge Rate: 91%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is jdolan/quetoo welcoming to first-time open-source contributors?

jdolan/quetoo has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in jdolan/quetoo 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.

What does the 68.1 C-Rank™ score (S Tier) represent?

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 68.1 places jdolan/quetoo in the S tier.

What is the external contributor pull request merge rate for jdolan/quetoo?

The external contributor pull request merge rate for jdolan/quetoo is 90.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in jdolan/quetoo?

jdolan/quetoo currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

jdolan
jdolan/quetooS•Elite338
GitHub
Back to Explorer
jdolan

jdolan/quetoo

338
Active (30d)S•Elite(68/100)C

Quetoo ("Q2") is a free first person shooter based on id Tech2. GPL v2 license.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.2/10
Patience Score
8.0/10
Nitpick Rate
25%

Strict review standards in jdolan/quetoo. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in jdolan/quetoo focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Update docs or README when behavior changes
  • •Run the repository formatter and linter locally
  • •Keep PRs small and focused on one change

Top PR Friction Pitfalls (Don'ts)

  • •Do not ship user-facing changes without matching docs
  • •Do not submit formatting-only noise with feature changes
  • •Do not mix unrelated refactors with feature work
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
90.8%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
6 core
Highly collaborative maintainer core
Diagnostic Health HUD
90.8%
Merge Gauge
100.0%
1st-Timer
Community Vibe66/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for jdolan/quetoo
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/jdolan/quetoo)](https://getmerged.abhishekco.de/jdolan/quetoo?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

Description Bots fall into the water and lava, then drown and burn to death. I don't have a screenshot or way to reproduce, but if you play a few games with bots on lava/water maps, you just have to wait a little. It's bound to happen. Quite regularly actually.

📅 Opened Jun 12, 2026💬 13 comments
Quality: 65/100Contribute

Might be kinda nice to give players a visual cue as to how much longer intermission is. We could show a (backwards?) progress bar at the bottom of the screen with the next map name communicated via config string.

📅 Opened Jun 9, 2026💬 0 comments
Quality: 65/100Contribute

Summary I'd like to have a cvar for changing whether the map timer counts up or down Motivation I learned how to time items in quake by adding time to the map clock in my head

📅 Opened May 26, 2026💬 8 comments
Quality: 55/100Contribute
Looking for more C beginner tasks?Explore C GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for jdolan/quetoo

When evaluating whether to contribute to jdolan/quetoo, 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 jdolan/quetoo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.8% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to jdolan/quetoo

01

Is jdolan/quetoo welcoming to first-time open-source contributors?

jdolan/quetoo has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 68.1 C-Rank™ score represent?

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 68.1 places jdolan/quetoo in the Elite tier.

04

What is the external contributor pull request merge rate for jdolan/quetoo?

The external pull request merge rate is 90.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in jdolan/quetoo?

Yes, jdolan/quetoo currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for jdolan/quetoo 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.