AcademySoftwareFoundation/OpenCue - Open Source PR Review Scorecard

A render management system you can deploy for visual effects and animation productions.

C-Rank Grade: A (Welcoming) - 66/100

External PR Merge Rate: 64%

Response Time: -

First Timer Success: 50%

Frequently Asked Questions

Is AcademySoftwareFoundation/OpenCue welcoming to first-time open-source contributors?

AcademySoftwareFoundation/OpenCue has a recorded first-timer success rate of 50.0%. Repositories ranked A 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 AcademySoftwareFoundation/OpenCue 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 65.8 C-Rank™ score (A 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 65.8 places AcademySoftwareFoundation/OpenCue in the A tier.

What is the external contributor pull request merge rate for AcademySoftwareFoundation/OpenCue?

The external contributor pull request merge rate for AcademySoftwareFoundation/OpenCue is 64.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in AcademySoftwareFoundation/OpenCue?

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

AcademySoftwareFoundation
AcademySoftwareFoundation/OpenCueA•Welcoming994
GitHub
Back to Explorer
AcademySoftwareFoundation

AcademySoftwareFoundation/OpenCue

994
Active (30d)A•Welcoming(66/100)Python

A render management system you can deploy for visual effects and animation productions.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
6.2/10
Patience Score
7.2/10
Nitpick Rate
55%

Strict review standards in AcademySoftwareFoundation/OpenCue. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in AcademySoftwareFoundation/OpenCue 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
  • •Add or update tests for changed behavior before requesting review
  • •Link the issue and include reproduction context in the PR

Top PR Friction Pitfalls (Don'ts)

  • •Do not ship user-facing changes without matching docs
  • •Do not leave requested test coverage unresolved
  • •Do not open context-free PRs
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
64.3%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
5 core
Small core review team
Diagnostic Health HUD
64.3%
Merge Gauge
50.0%
1st-Timer
Community Vibe41/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Describe the enhancement CueGUI recently gained a large extension to Limits. A limit can now count tokens per running frame (FRAME, the existing behavior) or per host (HOST, one token shared by all frames on a machine, for per-machine licenses such as Houdini/sesinetd, Katana or Mari), with enforcement modes (Enforced, Advisory, Disabled), a soft threshold, an external report TTL, and reconciliation against an external license server, plus per-host license holds. CueWeb has a basic Limits page (create, delete, rename, set max value) but none of the new fields, the license usage / holders view, or the host license columns. Add that parity. Expected behavior The Limits add / edit dialogs expose Type (Frame / Host), Enforcement (Enforced / Advisory / Disabled), soft threshold, and report TTL. The Limits page shows current usage and per-host holders (settled totals and which hosts hold a token). Monitor Hosts gains license columns, filtering and a license details view. The Layer and Attri

📅 Opened Sep 17, 2026💬 2 comments
Quality: 90/100Contribute

Describe the enhancement CueGUI recently added a "Shutdown If Completed" job action to the Monitor Jobs right click menu. Cuebot sometimes keeps listing a job that is actually complete because it lost the shutdown signal for it; this action lets a user clean those up. For each selected job that looks complete it calls the job's shutdownIfCompleted RPC after a yes/no confirmation, and skips jobs the user is not permitted to act on. CueWeb has no equivalent, so add the same action to the Monitor Jobs job context menu (single and multi select). Expected behavior A "Shutdown If Completed" item on the job right click menu (and for a multi-selection) that, after a confirmation, calls ShutdownIfCompleted for each selected job and shows a result toast, matching the existing job actions (Kill, Pause, Eat). Version Number https://github.com/AcademySoftwareFoundation/OpenCue/releases/tag/v1.19.1 Additional context CueGUI change: PR #2523 (commit 42f4eea). The backend already supports this; on

📅 Opened Sep 17, 2026💬 2 comments
Quality: 90/100Contribute

Describe the enhancement Per page view settings reset every time the user navigates away and comes back. For example, on Monitor Hosts: turn Auto-refresh off and set Rows per page to 25, navigate elsewhere, then return to Monitor Hosts and both settings are back to their defaults. These settings should persist per user and per page, and be restored on return, so that a user who prefers 25 rows with Auto-refresh off keeps that view. The same applies to the other view level controls on the tables. Version Number https://github.com/AcademySoftwareFoundation/OpenCue/releases/tag/v1.19.1 Additional context Today these live in component state with no persistence, for example autoRefresh is initialized to true in cueweb/app/hosts/page.tsx:120 and the "Rows per page" control in cueweb/components/ui/pagination.tsx only drives table state. CueWeb already persists other preferences in localStorage (split ratio, Attributes panel state, user colors, comment macros), so a small shared hook, keyed

📅 Opened Sep 17, 2026💬 2 comments
Quality: 90/100Contribute

Describe the enhancement In CueGUI, clicking a job, host or frame puts the name of that entity on the Linux middle click (primary) clipboard. That is heavily used in practice: names get pulled out of the cue constantly and pasted into other tools, tickets and emails when communicating about what is happening on the farm. CueWeb already covers most of this. The right click menus carry "Copy Job Name", "Copy Layer Name", "Copy Frame Name" and "Copy Log Path"; every copy raises a confirmation toast; and the Attributes panel puts a hover copy button on each attribute key and value, with a checkmark that reverts shortly after. The shared helper behind the menu items also falls back to a hidden textarea and execCommand when the Clipboard API is unavailable, so copying still works when CueWeb is reached over plain HTTP on a LAN address. What is left is the remaining coverage, so the gesture is the same everywhere: No copy item on the host menu. The host right click menu has Comments, View Pr

📅 Opened Sep 17, 2026💬 2 comments
Quality: 90/100Contribute

Describe the enhancement The list of monitored jobs being saved at the account level works well, and it supports a two window workflow: Monitor Cue in one browser window and Monitor Jobs in another. What is missing is a way to move a job between the two without leaving Monitor Cue. Add an action on Monitor Cue, for example a right click item such as "Add to Monitor Jobs" (and ideally a multi select equivalent), that appends the selected job or jobs to the saved Monitor Jobs list in place. The Monitor Jobs window should pick the new entries up on its next refresh, with no navigation away from Monitor Cue. Version Number https://github.com/AcademySoftwareFoundation/OpenCue/releases/tag/v1.19.1 Additional context Monitor Cue already has a job context menu (cueweb/components/ui/context_menus/action-context-menu.tsx), so this is mainly a matter of writing to the same saved monitored jobs list that Monitor Jobs reads, and making sure the other window notices the change. Brief visual feedba

📅 Opened Sep 17, 2026💬 2 comments
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python 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 AcademySoftwareFoundation/OpenCue

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

Frequently Asked Questions - Contributing to AcademySoftwareFoundation/OpenCue

01

Is AcademySoftwareFoundation/OpenCue welcoming to first-time open-source contributors?

AcademySoftwareFoundation/OpenCue has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming 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 65.8 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 65.8 places AcademySoftwareFoundation/OpenCue in the Welcoming tier.

04

What is the external contributor pull request merge rate for AcademySoftwareFoundation/OpenCue?

The external pull request merge rate is 64.3%. 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 AcademySoftwareFoundation/OpenCue?

Yes, AcademySoftwareFoundation/OpenCue currently has 11 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 AcademySoftwareFoundation/OpenCue 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.