Collaborative, local-first GTK text editor
C-Rank Grade: B (Solid) - 58/100
External PR Merge Rate: 100%
Response Time: 1d
First Timer Success: 100%
p2panda/reflection has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in p2panda/reflection respond to incoming external pull requests in approximately 24.9 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 57.9 places p2panda/reflection in the B tier.
The external contributor pull request merge rate for p2panda/reflection is 100.0%, based on public PR activity from non-core contributors.
p2panda/reflection currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in p2panda/reflection 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/p2panda/reflection?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~120 hours (45% approval). Keep your diff compact for rapid review.
This entails two different kinds of export: In the primary menu on the overview, an option like "Export All Pads...", to get a folder with .md files for all your pads On each individual pad, the option to "Export to File...", to save the pad as a .md file
When taking notes there are a few autocomplete features that'd be really useful to have, in particular auto-completing new lines with the right prefix when writing lists of checkboxes. We already follow the indentation level of the previous lines for new lines, it'd be nice to do the same for bullet lists, ordered lists, and lists with checkboxes (Gitlab/Github do all of the above, I'd follow their behavior).
Ideally text lines should not be wider than about 70-100 characters. It'd be nice to do something similar to Apostrophe, and limit the maximum width independently of the window size.
When hovering other users' cursors, it'd be nice to show a tooltip with their name, and maybe their avatar as well.
When in a collaborative session with content that fills the entire height of the editor, it's annoying that there is no margin at the bottom, so that whatever is being typed is on the very last line, and any new lines appear beyond the viewport. To keep up to date I have to constantly scroll down. It would be nice to have some buffer to keep the next new lines in view.
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 p2panda/reflection, 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 p2panda/reflection acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
p2panda/reflection has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 57.9 places p2panda/reflection in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, p2panda/reflection currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for p2panda/reflection 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.