| Summary | Adding shared calendards: mention the supported shemas |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | dpa-bugs (at) aegee (dot) org |
| Created | 08/25/2017 (2997 days ago) |
| Due | |
| Updated | 08/28/2017 (2994 days ago) |
| Assigned | |
| Resolved | 08/28/2017 (2994 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
like http/https. And like I said, as long as we support all protocols,
it's not necessary to point the user at it.
listing them?
know that webcals and webcal are valid and preferred over https/http.
State ⇒ Feedback
Version ⇒ Git master
listing them?
REMOTE calendars
REMOTE calendars
REMOTE calendars
shemes (webcal, webcals, https, http)
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Adding shared calendards: mention the supported shemas
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ New
shemes (webcal, webcals, https, http)
Regarding Ticket
#14662. emit message to the user, if there was a fallback.