Process COUNTER and DECLINECOUNTER for iTIP requests
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
The iTIP protocol used by CalDAV methods for attendees to suggest a counter proposal for a meeting time: https://www.rfc-editor.org/rfc/rfc5546.html#page-18. This is currently not supported by our implementation.
Describe the solution you'd like
Implement handling of COUNTER and DECLINECOUNTER methods, ideally upstream in Sabre.
Describe alternatives you've considered
N/a
Additional context
N/a
Contributor guide
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.
Research direction
Start with the iTIP COUNTER and DECLINECOUNTER sections of RFC 5546 and compare them with the current CalDAV implementation. Investigate whether handling belongs upstream in Sabre, as suggested by the issue. Done means both methods are supported for attendee counter-proposals and declined counter-proposals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100