Eclipse GlassFish
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 77%
Response Time: -
First Timer Success: 53%
eclipse-ee4j/glassfish has a recorded first-timer success rate of 53.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eclipse-ee4j/glassfish 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 67.5 places eclipse-ee4j/glassfish in the A tier.
The external contributor pull request merge rate for eclipse-ee4j/glassfish is 77.1%, based on public PR activity from non-core contributors.
eclipse-ee4j/glassfish does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in eclipse-ee4j/glassfish. Prompt code reviews with positive guidance for new contributors.
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/eclipse-ee4j/glassfish?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
All the tests in https://github.com/eclipse-ee4j/glassfish/tree/6cab4ce3aad9bc65b52bc761a4aa88634a2bd0aa/appserver/tests/embedded/maven-plugin directory use the old maven plugin version 5. Convert them to use the latest 8.0 version of the plugin: https://github.com/eclipse-ee4j/glassfish-maven-embedded-plugin The new version uses a different artifactId: embedded-glassfish-maven-plugin instead of the old maven-embedded-glassfish-plugin(the groupId is the same) The new version runs Embedded GlassFish in a separate JVM by default. It's OK to keep the default for most of the tests but it would be good to disable this mode for at least one test so that we test it too. For example, the simple test case, or the applicationDispatcher test case. To disable it, set in the plugin config: <configuration> <fork>false</fork> </configuration> It's possible to remove the dependencies from the plugin definition in the maven-plugin/pom.xml file and just define the configuration property <ver
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 eclipse-ee4j/glassfish, 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 eclipse-ee4j/glassfish acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.1% were successfully merged into the primary branch.
eclipse-ee4j/glassfish has a recorded first-timer success rate of 53.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.5 places eclipse-ee4j/glassfish in the Welcoming tier.
The external pull request merge rate is 77.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
eclipse-ee4j/glassfish does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for eclipse-ee4j/glassfish 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.