Open Source API and interchange format for editorial timeline information.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 25%
Response Time: <1h
First Timer Success: -
AcademySoftwareFoundation/OpenTimelineIO 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 AcademySoftwareFoundation/OpenTimelineIO 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 53.3 places AcademySoftwareFoundation/OpenTimelineIO in the B tier.
The external contributor pull request merge rate for AcademySoftwareFoundation/OpenTimelineIO is 25.0%, based on public PR activity from non-core contributors.
AcademySoftwareFoundation/OpenTimelineIO currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in AcademySoftwareFoundation/OpenTimelineIO. Reviews community pull requests with focus on project quality.
Discussions in AcademySoftwareFoundation/OpenTimelineIO focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/AcademySoftwareFoundation/OpenTimelineIO?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (31% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
An LLM-based code review claims that there is a bug here: composable.cpp:79 — available_image_bounds writes *error_status without a null check; the parameter defaults to nullptr. gap->available_image_bounds() crashes. Could we get a volunteer to verify if this is a real bug? It sounds plausible, and could be easily verified by writing a test case and/or a test OTIO file that creates the scenario described.
An LLM-based code review claims that there are some bugs related to orphaned clips (Clip instances with a null parent). item.cpp:87-109 — range_in_parent/trimmed_range_in_parent on an orphan clip set the error then still call parent()->... on null. Same pattern in transition.cpp:58-90. composition.cpp:254-273 — _path_from_child walks current->parent() off the end for orphan/foreign children: track->range_of_child(orphan) crashes. Could we get a volunteer to verify if this is a real bug? It sounds plausible, and could be easily verified by writing a test case and/or a test OTIO file that creates the scenario described.
An LLM-based code review claims that there is a bug here: composition.cpp:397-400: missing current = parent; at the end of the loop (compare range_of_child at line 349). Stale current makes index_of_child fail with NOT_A_CHILD_OF for any timeline→track→stack→clip hierarchy. Poisons trimmed_range_in_parent, children_in_range, algo::fill. Could we get a volunteer to verify if this is a real bug? It sounds plausible, and could be easily verified by writing a test case and/or a test OTIO file that creates the scenario described.
The OTIO documentation here https://opentimelineio.readthedocs.io/ is incomplete. There are some classes, functions, and concepts that are missing documentation entirely, or need additional information. We would love for a volunteer to read/skim through the documentation as-is and make a checklist of areas that are missing. Examples: Item.1 is missing a doc string: https://opentimelineio.readthedocs.io/en/stable/tutorials/otio-serialized-schema.html#item-1 MediaReference.1 is missing a doc string: https://opentimelineio.readthedocs.io/en/stable/tutorials/otio-serialized-schema.html#mediareference-1 RationalTime.1 has docs, but they are too short and there's a math formatting problem: https://opentimelineio.readthedocs.io/en/stable/tutorials/otio-serialized-schema.html#rationaltime-1 etc. If we had a detailed checklist, then we could more easily ask people to fill in those gaps & track our progress on improving the documentation. Also: fixes/additions to the documentation content itse
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 AcademySoftwareFoundation/OpenTimelineIO, 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/OpenTimelineIO acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
AcademySoftwareFoundation/OpenTimelineIO 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 ~<1 hour. 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 53.3 places AcademySoftwareFoundation/OpenTimelineIO in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AcademySoftwareFoundation/OpenTimelineIO 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 AcademySoftwareFoundation/OpenTimelineIO 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.