📇 Contacts app for Nextcloud
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 63%
Response Time: 1d
First Timer Success: 40%
nextcloud/contacts has a recorded first-timer success rate of 40.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nextcloud/contacts respond to incoming external pull requests in approximately 24.6 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 58.5 places nextcloud/contacts in the A tier.
The external contributor pull request merge rate for nextcloud/contacts is 63.2%, based on public PR activity from non-core contributors.
nextcloud/contacts currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in nextcloud/contacts. Maintains strict focus on technical quality and test standards.
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/nextcloud/contacts?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday 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 (79% approval). Large PRs (>500 lines) take ~118 hours (28% approval). Keep your diff compact for rapid review.
⚠️ This issue respects the following points: ⚠️ This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum). This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!). I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels). I agree to follow Nextcloud's Code of Conduct. I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it. Bug description I have two address books A and B. A is the default. I created a new contact in address book B (using the Contacts app version 8.9.1), but Activity shows: "You have created contact XYZ in address book A". I have verified that the contact was actually created in address book B. I'm not sure whether this is a bug in contacts or server, but since the
Describe the bug The horizontal scrollbar covers the category groups in the category group input field when the groups are longer than the input field. Groups are not shown properly - only partly. The editing process is impacted. Steps to reproduce Go to a contact enable edit mode add some categories with longer names until the edit field is "full" the scrollbar appears on the bottom and covers the groups Expected behavior The height of the edit field should be adjusted - it should be a multiline edit field. Actual behavior Groups are not shown properly - only partly. Groups can not be removed Contact version 8.7.6 Operating system nextcloud AIO PHP engine version No response Web server No response Database No response Additional info No response
Is your feature request related to a problem? Please describe. See nextcloud/server#40017. For users, we can already set pronouns. But for (external) contacts, I didn't find a way. Describe the solution you'd like #4342 (comment) mentioned modern alternatives to RFC6350 that support this. So I guess implementing one of these would be a good way to resolve my issue. Describe alternatives you've considered Yes, there is a 'gender' field but sometimes I know the pronouns a contact prefers, but not what gender they identify as (e.g. does 'she/them' imply 'female'?). Just setting those to 'other' gender might loose that information. I can add it in the notes, but when writing a batch-mail to contacts, I would like to be able to programatically pick the corresponding prefered pronouns. Additional context Note that neither I want to start a debate about gender and pronouns nor do I want to engange in gender studies here. I just consider it polite to address contacts the way they prefer and wo
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 nextcloud/contacts, 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 nextcloud/contacts acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.2% were successfully merged into the primary branch.
nextcloud/contacts has a recorded first-timer success rate of 40.0%. Repositories ranked Welcoming 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 58.5 places nextcloud/contacts in the Welcoming tier.
The external pull request merge rate is 63.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nextcloud/contacts currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nextcloud/contacts 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.