Apache Fluss is a streaming storage built for real-time analytics.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 56%
Response Time: -
First Timer Success: 56%
apache/fluss has a recorded first-timer success rate of 56.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/fluss 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.8 places apache/fluss in the A tier.
The external contributor pull request merge rate for apache/fluss is 56.1%, based on public PR activity from non-core contributors.
apache/fluss currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (69% critical review signals). Ensure PRs strictly follow guidelines before requesting review in apache/fluss.
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/apache/fluss?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (70% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
Search before asking I searched in the issues and found nothing similar. Description Summary The Fluss project currently lacks a formalized process and clear guidelines for submitting and reviewing Fluss Improvement Proposals. New contributors and community members often struggle to understand the proposal lifecycle, required format, and review criteria. This issue tracks the creation of comprehensive documentation to streamline FIP contributions. Willingness to contribute I'm willing to submit a PR!
Search before asking I searched in the issues and found nothing similar. Description https://github.com/apache/fluss/actions/runs/24150938424/job/70477440445?pr=2934 Warning: Docusaurus found broken anchors! Please check the pages of your site in the list below, and make sure you don't reference any anchor that does not exist. Note: it's possible to ignore broken anchors with the 'onBrokenAnchors' Docusaurus configuration, and let the build pass. Exhaustive list of all broken anchors found: - Broken anchor on source page path = /docs/0.5/engine-flink/getting-started/: -> linking to /downloads/#fluss-connector - Broken anchor on source page path = /docs/0.6/engine-flink/getting-started/: -> linking to /downloads/#fluss-connector - Broken anchor on source page path = /docs/next/engine-flink/getting-started/: -> linking to /docs/next/engine-flink/ddl/#procedures - Broken anchor on source page path = /docs/engine-flink/getting-started/: -> linking to /docs/engine-flink/dd
Search before asking I searched in the issues and found nothing similar. Description See comment: #2464 (comment) Willingness to contribute I'm willing to submit a PR!
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 apache/fluss, 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 apache/fluss acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.1% were successfully merged into the primary branch.
apache/fluss has a recorded first-timer success rate of 56.1%. 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.8 places apache/fluss in the Welcoming tier.
The external pull request merge rate is 56.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/fluss 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 apache/fluss 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.