Should we drop support for RFC 2445?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reading icalrestriction_check() and the DTSTART entry in ical-restrictions.csv, then compare their behavior with the RFC requirements described in the issue. Work out and agree on the intended handling of VEVENTs without DTSTART before changing support; done means the project has a clear decision on RFC 2445 compatibility and the corresponding restriction behavior.
Written by the indexing model from the issue text.
Description
RFC 5545 is over 16 years old and fixed a lot of warts in RFC 2445. Namely, DTSTART, UID, and DTSTAMP were made mandatory in VEVENT.
I assumed that the icalrestriction_check() would reject a VEVENT with no DTSTART, but it doesn't. And the reason is because ical-restrictions.csv lists DTSTART as ZEROORONE, per RFC 2445.
What are the logical semantics of a VEVENT with no DTSTART, DTEND/DURATION? How would you display this on a calendar? The only viable use for such a VEVENT that I can think of is to just be a dumb container for a VALARM with a TRIGGER having a DATE-TIME value.
In any case, can we put a stake in the ground and standardize on RFC 5545 only?
- Dominant language
- C
- Stars
- 366
- Forks
- 127
- Avg merge
- 16h 47m
- Merged PRs (30d)
- 33
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libical/libical
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Line-buffer ownership documentation disagrees with icalparser_add_line() and icalparser_get_line()Open
Difficulty 3/5 Half a day Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libical/libical#1438 · 5 comments ·
Maintainers usually reply within 1 day
-
Fuzz: timeout in vcardtextlist_new_from_string()Possibly taken @rsto claimed this 24 days ago. Open
libical/libical#1415 · 2 comments · 2 assignees ·
Maintainers usually reply within 1 day
Similar issues
-
docs: AGENTS.md has no rule against running deploy scripts into the owner's game installPossibly taken @thesprockee claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
EchoTools/nevr-runtime#524 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Genymobile/scrcpy#7097 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
type: feature
Difficulty 1/5 Under an hour Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day