freebsd/poudriere - Open Source PR Review Scorecard

Port/Package build and test system

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

External PR Merge Rate: 30%

Response Time: 16h

First Timer Success: 75%

Frequently Asked Questions

Is freebsd/poudriere welcoming to first-time open-source contributors?

freebsd/poudriere has a recorded first-timer success rate of 75.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 freebsd/poudriere respond to incoming external pull requests in approximately 15.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 60.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 60.8 places freebsd/poudriere in the A tier.

What is the external contributor pull request merge rate for freebsd/poudriere?

The external contributor pull request merge rate for freebsd/poudriere is 30.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in freebsd/poudriere?

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

freebsd
freebsd/poudriereA•Welcoming447
GitHub
Back to Explorer
freebsd

freebsd/poudriere

447
Active (30d)A•Welcoming(61/100)Shell

Port/Package build and test system

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Community Mentor

Warmth Score
9.8/10
Patience Score
9.6/10
Nitpick Rate
10%

Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in freebsd/poudriere.

Top PR Submission Do's

  • •Verify all existing package test suites run cleanly
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
15 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
30.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
7 core
Highly collaborative maintainer core
Diagnostic Health HUD
30.0%
Merge Gauge
75.0%
1st-Timer
Community Vibe53/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Prerequisites [X ] Have you checked for an existing issue describing your idea? What is your proposal? I'd like to be able to limit the number of CPUs provided to a jail, either via a CPU set or some other way What is the existing behavior, if any? Currently the jails inherit the CPU set of the root cpuset, which by default is all CPUs. In systems where one has a lot of CPUs - eg the 2 socket * 10 core * 8 thread = 160 logical CPU POWER8 boxes I have here, that means that ports that will do their own parallelism may attempt to grow to use all CPUs. I verified this by jexec'ing into a jail and then checking sysconf -a for how many CPUs are considered "online". (For things that are super broken and check hw.ncpu instead of sysconf / cpuset it would be nice for the kernel to virtualise said sysctl, but that's a parallel effort to do in the kernel, not here.) (But if we do find things that use hw.ncpu then it's even more of a reason to figure out jail virtualisation for it...) What is th

📅 Opened Feb 16, 2026💬 1 comment
Quality: 70/100Contribute
Looking for more Shell beginner tasks?Explore Shell 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 freebsd/poudriere

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

Frequently Asked Questions - Contributing to freebsd/poudriere

01

Is freebsd/poudriere welcoming to first-time open-source contributors?

freebsd/poudriere has a recorded first-timer success rate of 75.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 ~15 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.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 60.8 places freebsd/poudriere in the Welcoming tier.

04

What is the external contributor pull request merge rate for freebsd/poudriere?

The external pull request merge rate is 30.0%. 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 freebsd/poudriere?

Yes, freebsd/poudriere currently has 2 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 freebsd/poudriere 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.