docs(contributing): drag-and-drop rescheduling isn't rejected after all

The "Not going to happen" list carried drag-and-drop event rescheduling as
a settled no. That was a point-in-time decision from the roadmap era; the
owner confirmed it will come after all, so publishing it as rejected would
wrongly deter someone from proposing or building it.
This commit is contained in:
2026-07-30 10:36:55 +02:00
parent 03cb767f72
commit 0dfbc75844

View File

@@ -182,7 +182,6 @@ issue.
Saving you the effort: Saving you the effort:
- **Drag-and-drop event rescheduling.** Considered repeatedly, settled as a no.
- **Anything requiring `INTERNET`**, including a sync stack of our own. - **Anything requiring `INTERNET`**, including a sync stack of our own.
- **An app-side event database.** - **An app-side event database.**