From 0dfbc75844a1b8e02d233086d410b2b5eab9c33a Mon Sep 17 00:00:00 2001 From: Jean-Luc Makiola Date: Thu, 30 Jul 2026 10:36:55 +0200 Subject: [PATCH] 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. --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4e69a13..43237f7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -182,7 +182,6 @@ issue. 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. - **An app-side event database.**