Roadmap Updates
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python
调研方向
This is a roadmap continuation of #474, not a single implementation task. Start by reading the listed issues for the 3.0 and 3.2 milestones and their linked discussions to identify a specific, unclaimed task. Done depends on the scope of that individual issue; this roadmap spans multiple releases and work areas.
由索引模型根据 Issue 内容生成。
描述
This is a contination of #474.
There are two remaining items on the old road map, Async/API changes and the JMAP project. Async is ongoing work and will be released in 3.0, hopefully to be released in the end of January. I've looked through the list of outstanding issues, and found some more issues I'd like to get closed while releasing 3.0, that gives an extra 23 hours.
While working on the "server hints project", I did lots of development on a caldav-server-tester package, but it's needed with more QA and polishing and then make a proper release of the project. It would be very useful if people that experience problems with their private caldav servers are able to run the tester by themselves. It's also useful for generating configuration. I estimate 40h on this task, including documentation.
I think JMAP will be the next. The estimate was set to 40h, it's a very optimistic estimate for getting full-blown support for a completely different protocol - but 40h should be enough to get started with JMAP, set up something that covers the very basic save/load/search-methods, but no corner cases or extras supported. Research should also be done to see if there are existing JMAP libraries out there - but keep in mind tha JMAP is primarliy an email protocol, so whatever exists may not be optimized for calendaring usage. My idea now is to split out a new Calendar Client package which should have a fairly consistent API no matter if one will communicate with a CalDAV server or a JMAP server. The bulk of the work will be done outside the CalDAV library, but I expect that there will be a 3.1-release of CalDAV.
The scheduling support is under-tested, under-developed and needs more work, I'd like to release improved scheduling in version 3.2. The scheduling seems to be in demand, it's not much documented, but people still manage to find the methods and figure out that they don't work.
Rough time estimates
- ASync + API improvements - 50h (as before)
- Fixing/closing more issues for the v3.0 release - 23h
- Documentation updates v2.0 -> v3.0 - 12h
- Polishing and releasing the caldav-server-tester utility, including documentation - 40h
- Basic JMAP support - 40h (as before)
- Basic JMAP documentation - 8h
- Fixing/closing issues related with scheduling in 3.2 - 40h
- Rethinking JMAP and make a roadmap for full JMAP support - 8h
So it's 90 hours from the original road map and 95 hours extra.
Those issues will probably keep me busy until the summer, but I've also tagged up milestones 3.x / 3.x-google / 4.x in GitHub (with time estimates entered in the comments for some of those tasks), as well as my plann command line interface project.
Issue listings
Issues slated for 3.0:
- 4h - #590
- 4h - #589
- 4h - #586
- 5h - #580
- 2h - #564
- 5h - #518
- 4h - #509
- 6h - #482
This sums up to 30 hours. Realistically I expect to close around 75% of those issues, giving an estimate of 23 hours.
Most of the issues are about improving the quality of the project and removing technical debt. I think some of those things should be prioritized as it's good to get it done when releasing a major version.
Issues slated for 3.2 - 38 hours, all of them should be completed:
- 12h - #596
- 4h - #595
- 8h - #544
- 6h - #524
- 8h - #399
- 主要语言
- Python
- 星标
- 412
- 派生
- 113
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 41
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
python-caldav/caldav 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
python-caldav/caldav#687 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
python-caldav/caldav#774 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
python-caldav/caldav#769 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 50/100
python-caldav/caldav#765 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
python-caldav/caldav#763 ·
维护者通常 1 天内回复
查看 python-caldav/caldav 的全部 Issue
相似的 Issue
-
md/asciidoc/csv: an explicit `encoding="utf-8"` keeps a leading BOM, the auto-detect path drops it未关闭
难度 2/5 1-3 小时 新手友好度 82/100
docling-project/docling#4846 ·
维护者通常 1 天内回复
-
area/sessions comp/dashboard comp/desktop comp/gateway comp/tui duplicate P2 sweeper:risk-session-state type/bug
难度 2/5 1-3 小时 新手友好度 78/100
NousResearch/hermes-agent#138914 · 1 条评论 ·
维护者通常 1 天内回复
-
bot-triaged module: activation checkpointing module: inductor oncall: pt2 triaged
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
[oblt-aw][autodoc] Update PR Actions Detective E2E prerequisites and fix dashboard-format table typo未关闭documentation
难度 2/5 1-3 小时 新手友好度 75/100
elastic/oblt-aw#2382 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复