- From: Philippe Le Hegaret <notifications@github.com>
- Date: Wed, 19 Feb 2025 09:23:07 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/editing/issues/480/2669290472@github.com>
plehegar left a comment (w3c/editing#480) Here are my two cents, so far: 1. The work item falls into the [scope of the working group](https://www.w3.org/2023/09/webediting-charter-2023.html#scope): "The scope of Web Editing WG covers all aspects of text editing on the web, which may include [...]" 2. It's not clear to me that the Group ever adopted this work item in the first place. While a Group is entitled to adopt new proposals within its scope, it seems to me that this work predates the formation of the Working Group (EditContextAPI is listed in the [original 2021 charter](https://www.w3.org/2021/06/web-editing-wg-charter.html). 3. Once adopted, whether a new work item appears as a separate document or a new section of a specification is up to the group. We do strongly encourage to only adopt new work items that have gone through incubation first but we also try to stay away from micro-managing how new features appear across specifications. 4. I wonder about the potential for creating confusion out there if this gets published on w3.org. Why publish it at all if we don't want the community to look at it? Maybe the repo should be updated to point to where things are now happening and then the repo should be archived. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/480#issuecomment-2669290472 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/480/2669290472@github.com>
Received on Wednesday, 19 February 2025 17:23:11 UTC