- From: Andrew Kirkpatrick <andrew.kirkpatrick@evinced.com>
- Date: Fri, 12 Sep 2025 13:58:03 +0000
- To: Gregg Vanderheiden <gregg@vanderheiden.us>, Hidde de Vries <hidde@hiddedevries.nl>
- CC: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
- Message-ID: <BYAPR05MB4006593D981B4346CDD685A6F508A@BYAPR05MB4006.namprd05.prod.outlook.com>
I think that it is worth being deliberate about defining specific conditions where this is expected and where it is not. The WCAG 2 TF defines some of these condition here: https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process For example, chairs can close an issue if it is “response-only” or duplicative or “ignored for > 12 months” - those are easy, but what else? Are we expecting that the chairs declare that they feel that consensus has been reached and a decision is made? Is this different for changes to techniques/understanding vs. published specs vs. drafts vs. other? If I were a chair I would definitely want the comfort of knowing that there is a framework for decisions that I could point out to people when complaints inevitably arise. Andrew From: Gregg Vanderheiden <gregg@vanderheiden.us> Date: Friday, September 12, 2025 at 03:36 To: Hidde de Vries <hidde@hiddedevries.nl> Cc: w3c-waI-gl@w3. org <w3c-wai-gl@w3.org> Subject: Re: Re closing of issues and WG support On Sep 11, 2025, at 6:47 AM, Hidde de Vries <hidde@hiddedevries.nl> wrote: On 10 Sep 2025, at 19:16, Gregg Vanderheiden <gregg@vanderheiden.us> wrote: if you mean chairs should be empowered to close issues unilaterally using their own judgement when they feel the issue is closed, without having to bring each item up for WG vote — I would agree. Yes I do! I would say however that it would be good to ping the person who brought the issue forward as part of the process though so they are aware that their suggestion had been accepted/modified/rejected. G Good point, yes I'd say that would be good courtesy to do. Possibly GitHub's default behaviour of emailing the issue-opener for each comment (which includes the closing one unless user changed settings) would suffice? If the commenter put the issue into GitHub directly - yes. but that is sort of after the fact but if there is a comment on why - when it is closed - if it is not obvious - yes Again I leave that to the Chairs judgement Best, Hidde
Received on Friday, 12 September 2025 13:59:09 UTC