icalendar parser library for Python
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 53%
Response Time: 2d
First Timer Success: 53%
collective/icalendar has a recorded first-timer success rate of 52.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in collective/icalendar respond to incoming external pull requests in approximately 54.1 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 56.9 places collective/icalendar in the A tier.
The external contributor pull request merge rate for collective/icalendar is 52.7%, based on public PR activity from non-core contributors.
collective/icalendar currently has 24 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in collective/icalendar. 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/collective/icalendar?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~35 hours (66% approval). Large PRs (>500 lines) take ~260 hours (24% approval). Keep your diff compact for rapid review.
icalendar's test suit issues some warnings. $ uv run pytest =============================================================== warnings summary ================================================================ src/icalendar/tests/rfc_7265_jcal/test_examples.py: 4 warnings src/icalendar/tests/test_equality.py: 6 warnings src/icalendar/tests/test_issue_313_globally_unique_tzid.py: 3 warnings /home/blackberry/icalendar/src/icalendar/prop/dt/types.py:107: GloballyUniqueTZIDGuessed: Timezone '/freeassociation.sourceforge.net/Europe/Berlin' is a globally unique TZID; guessing it means 'Europe/Berlin' by stripping the vendor prefix. This may be wrong. See RFC 5545 section 3.2.19. return vDatetime.from_ical(ical, timezone=timezone) src/icalendar/tests/rfc_7265_jcal/test_examples.py: 4 warnings src/icalendar/tests/test_equality.py: 6 warnings src/icalendar/tests/test_issue_313_globally_unique_tzid.py: 4 warnings /home/blackberry/icalendar/src/icalendar/prop/dt/types.py:107: GloballyUniqueT
The contributing page shows a lot if different activities that you can do to contribute. The Matrix chat should be added as a way to get in touch. https://matrix.to/#/#pycal:chat.pycal.org Also, for me, it does not flow quite right. I think, we can categorise these contributions: code contributions triage ...? financial support other ways How to contribute as a first-timer: Please have a look at other project's contributing pages and see what you like about these. This page is also for you. Please post your ideas of how to make it better for you to find what you need.
vRecur is a dictionary but we know very well which keys we have in it. In the same manner as the Components, it would be nice to have accessors for getting, setting and deleting the values. mandatory freq MUST occur. vRecur.freq: FREQ must be present. Absence raises InvalidCalendar on get invalid values raise InvalidCalendar The return type is registered in icalendar.enum cannot be deleted optional These accessors only have one value at most until -> date|datetime count interval wkst skip -> vSkip rscale -> enum Append that checklist to the PR template: ## Implementation - [ ] return type is `None` or what is specified in the `vRecur.types` - [ ] setting to None deletes the value - [ ] del deletes the value - [ ] if multiple values are given, the first one is returned - [ ] if an empty list is in there, None is returned - [ ] doc string with an example value: >>> vRecur("<...>").<...> - [ ] doc string summarizes what this property is about - [ ] doc string shows the r
PARTSTAT is one of the enums in icalendar.enums. The RFC specifies that values that are not enclosed in "" can be case-insensitive. I would like to make sure that this code works for all of our case-insensitive enums: >>> from icalendar.enums import PARTSTAT >>> PARTSTAT("needs-action") == PARTSTAT("NEEDS-ACTION") == PARTSTAT.NEEDS_ACTION True
#1135 requests support for xCal serialization. The work has started in the xCal branch. This issue is there to contribute to the work. Many classes and conversions need to be added. Classes that need conversion 3.6.1. Binary 3.6.2. Boolean 3.6.3. Calendar User Address 3.6.4. Date 3.6.5. Date-Time 3.6.6. Duration 3.6.7. Float 3.6.8. Integer 3.6.9. Period of Time 3.6.10. Recurrence Rule 3.6.11. Text 3.6.12. Time 3.6.13. URI 3.6.14. UTC Offset vDDDLists - included in the tests of the different subclasses vDDDTypes - included in the tests of the different subclasses vBroken vCategories vInline vN vOrg vUid vUnknown vURI vXmlReference Contribution Choose a class and comment below that you would like to work on it. Then, start a Pull Request. The contribution must go to the xcal branch of icalendar. Copy the test cases of structurally related class (text bases/value based/date based) Adapt them to fit that particular value type Implement xCal conversion on the cla
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 collective/icalendar, 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 collective/icalendar acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.7% were successfully merged into the primary branch.
collective/icalendar has a recorded first-timer success rate of 52.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 56.9 places collective/icalendar in the Welcoming tier.
The external pull request merge rate is 52.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, collective/icalendar currently has 24 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for collective/icalendar 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.