Monorepo for Terra Packages
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 15%
Response Time: 3h
First Timer Success: -
terrapkg/packages has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in terrapkg/packages respond to incoming external pull requests in approximately 2.7 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 65.8 places terrapkg/packages in the A tier.
The external contributor pull request merge rate for terrapkg/packages is 14.5%, based on public PR activity from non-core contributors.
terrapkg/packages currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in terrapkg/packages 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/terrapkg/packages?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (18% approval). Large PRs (>500 lines) take ~13 hours (15% approval). Keep your diff compact for rapid review.
Full Raw Package Name (e.g. anda-0.4.14-1.fcrawhide.x86_64) flutter-3.44.2-1.fc44.x86_64 Release Version f44 Describe the Bug When you run flutter in cli as a regular user it refuses to do it because permission denied To Reproduce dnf install flutter run flutter permission denied Expected Behavior You could run flutter under a regular user not just a privileged superuser Relevant Log Output flutter /usr/share/flutter/bin/internal/update_engine_version.sh: line 71: /usr/share/flutter/bin/cache/engine.stamp.tmp.131628: Permission denied /usr/share/flutter/bin/internal/update_engine_version.sh: line 78: /usr/share/flutter/bin/cache/engine.realm: Permission denied
Please leave a comment if you, your project, or company is using Terra! A short sentence or two of how Terra is useful for you would be appreciated as well. Of key interest: Distributions/Fedora downstreams Other open source projects Companies or individuals using Terra at their workplace Anything else, don't be shy! P.S. If you represent a company or project, and would like to open a direct line with us, feel free to join and let us know on our Discord or send an email to [email protected].
These packages being in a seperate repo are bad for UX, and some of our packages depend on some of these packages. Re-packaging these for ourselves will eliminate the need to pull in the adoptium repo when building Terra packages. java-8-openjdk java-8-openjdk-portable java-11-openjdk java-11-openjdk-portable java-17-openjdk java-17-openjdk-portable java-21-openjdk >= 44 java-21-openjdk-portable >= 44 I propose adding all of these to anda/langs/java/
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 terrapkg/packages, 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 terrapkg/packages acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 14.5% were successfully merged into the primary branch.
terrapkg/packages has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 65.8 places terrapkg/packages in the Welcoming tier.
The external pull request merge rate is 14.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, terrapkg/packages currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for terrapkg/packages 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.