Skip to content

docs: the tasks draft is now RFC 10051 - #47

Merged
tobixen merged 2 commits into
mainfrom
docs/rfc-10051
Nov 4, 2026
Merged

tobixen merged 2 commits into
mainfrom
docs/rfc-10051

Conversation

@tobixen

@tobixen tobixen commented Nov 4, 2026

Copy link
Copy Markdown
Member

Disclaimer: AI-generated code and text below the line, generated by Claude Opus 5.5 from the initial prompt:

Check https://datatracker.ietf.org/doc/html/rfc10051 and see how it affects the calendaring client. At least, all references to "the tasks draft" should probably be replaced with "RFC 10051"

After that, I discussed a bit and read up the RFC myself - first partially and then completely.

Should a "FAILED" task count as actionable when listing out open issues, or is it a final state?

In the definition of what it means when a participant marks FAILED, it's final from that participants point of view: "to-do cannot be completed".

In the definition of what it means when a task has state FAILED, it reads non-final from the definition: "[task] may need some follow-up from the "Organizer" to reschedule or cancel".

In the appendix A3, state "FAILED" comes as the last state in the task lifecycle, and should hence be interpreted as final. "Overall state set by Organizer for TASK-MODE=CLIENT or by server for AUTOMATIC-FAILURE"

Perhaps it's needed to reach out to the RFC author to get a clarification.


The iCalendar task extensions draft was published as RFC 10051 in October 2026. The docs and code comments now refer to the RFC. A comparison with draft -17 found only editorial changes, so no design decision changes.

Publication also prompted two small fixes for the new FAILED status:

  • summarize() no longer counts the estimate of a FAILED task as committed time.
  • The memory backend's TRACKER profile stores FAILED as COMPLETED, instead of losing the status.

Still open, and documented in API_DESIGN.md:

Testing: the two new tests pass and there are no new failures in the local suite. The local run had 429 failures and errors both with and without these changes, and those checked trace to an outdated caldav in the local environment (3.6.0, while 3.7 is required), so CI is the first run of this against the CalDAV test servers.

The task extensions draft was published as RFC 10051 in October 2026,
with only editorial changes from -17 on the points used here.  Refer to
the RFC throughout, and update the section 6 quote to its final wording.

Document two consequences: icalendar's Todo.status raises ValueError on
PENDING and FAILED, and section 11.1 makes a lone DURATION legal.

Prompt: Check https://datatracker.ietf.org/doc/html/rfc10051 and see how it affects the calendaring client.  At least, all references to "the tasks draft" should probably be replaced with "RFC 10051"

Assisted-By: Claude Opus 5.5
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
summarize() counted the estimate of a FAILED task as committed time,
though nobody does that work until it is rescheduled.  The tracker
profile lost STATUS on FAILED; it now stores COMPLETED, as for
CANCELLED.  Open-task search still returns FAILED, and API_DESIGN
records that RFC 10051 is unclear on whether the state is final.

Prompts (comments made inline in the document while reviewing it):
> (on excluding FAILED from the open estimates) I suppose this can be done without fixing PyCalendar/icalendar#2055 first?
> (on mapping FAILED to COMPLETED on two-state trackers) I suppose this can be done without fixing PyCalendar/icalendar#2055 first?
> (on open-task search still returning FAILED) Very unclear indeed.  9.1 indicates it's a final state, but that's for the participant. 11.2 indicates that "FAILED" is not a final state, the organizer should take action and reschedule or cancel it.  And A-3 shows that FAILED in the organizers part-stat combined with FAILED in the STATUS is a final state. Let's just document that this is very unclear.  Full support of RFC10051 is not yet part of the ROADMAP.

Assisted-By: Claude Opus 5.5
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
@tobixen
tobixen merged commit 784f144 into main Nov 4, 2026
8 checks passed
tobixen added a commit that referenced this pull request Nov 4, 2026
Move the mission statement to the top and rewrite it around one API and
one shared configuration file, and add why JMAP and iCalendar feeds do
not belong in the caldav library.  The prose is the author's own.

Rebased on the merge of PR 47, keeping its RFC 10051 wording, with typos
fixed and the placeholder link filled in.

Prompt: I've done some work now on the README.  There is a pull request #44 (IIRC) which may conflict with this work, check if it's merged and deal with the potential conflict.  Then do a full QA and /review-and-push - I'd like to push it directly to master.  Check if there are any other PRs open or if the README has been touched in any other branches, I think I've asked to replace all instances of "task draft" to "RFC 10051". [#44 is #44; the conflict was with #47; the branch is main]
Followup-Prompt: (answer) Merge #47 first
Followup-Prompt: (answer) "JCal" in the README meant JSCalendar

Assisted-By: Claude Opus 5.5
@tobixen
tobixen deleted the docs/rfc-10051 branch November 6, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant