[Enhancement] Allow ⪆ `31.0.10` to act as a CalDAV client.

未关闭
#2,972 0 条评论 6 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
api, frontend

调研方向

首先跟踪 Calendar iCal 订阅 GUI 以及用于添加外部源的相应 Tasks GUI 流程。定义应如何添加、枚举外部 CalDAV 源并进行双向同步,然后根据所请求的 Nextcloud 和外部源用例验证最终行为。

由索引模型根据 Issue 内容生成。

描述

enhancement
What Problems This Relates To

I've two relevant desires:

  1. When I add NextCloud as a source in an external synchronisation service — utilise davx5-ose as an applicable example — I want external CalDAV sources, added via Tasks' GUI, to be available.

  2. I want to be able to access external CalDAV sources in Tasks' GUI.

One might consider davx5-ose to solve this. However:

  1. It requires an external synchronisation service (of which NC and SyncThing are examples) to synchronise its preferences. However, even that basic form of synchronisation requires periodic manual exportation and importation, which is brittle. NextCloud does not suffer from this.

  2. It's not available outside of AOSP.

  3. Utilising an external client renders NextCloud a purely backend service, which likely isn't what NC desires for its Tasks application.

Despite this, I don’t see any way to add an external CalDAV source to enumerate tasks from, like one can for iCal sources in Calendar. (Although Calendar accepts URIs to CalDAV sources, that appears to be erroneous.)

Desired Solutions

Implement a two-way equivalent to Calendar's one-way iCal subscription GUI, but for CalDAv sources.

Considered Alternatives

Utilise an external client, of which tasks/tasks is an example, with an external synchronisation service, of which davx5-ose is the best example. However, consider its (aforestated) comparative disadvantage.

Additional Context

Originally discussed at help.nextcloud.com/t/234881/4.

主要语言
JavaScript
星标
710
派生
125
平均合并
19 小时 37 分钟
30 天内合并 PR
12

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nextcloud/tasks 的其他 Issue

查看 nextcloud/tasks 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。