IETF Logo Mail Archive

Re: [quicwg/base-drafts] Solidarity bot: Invalid (Issue #4965)

Martin Thomson <notifications@github.com> Wed, 16 March 2022 00:23 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237343A0E12 for <quic-issues@ietfa.amsl.com>; Tue, 15 Mar 2022 17:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hud2Z2OpoFBH for <quic-issues@ietfa.amsl.com>; Tue, 15 Mar 2022 17:23:17 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96E943A0D76 for <quic-issues@ietf.org>; Tue, 15 Mar 2022 17:23:17 -0700 (PDT)
Received: from github-lowworker-89f3697.ash1-iad.github.net (github-lowworker-89f3697.ash1-iad.github.net [10.56.116.64]) by smtp.github.com (Postfix) with ESMTP id A6BAB6009FC for <quic-issues@ietf.org>; Tue, 15 Mar 2022 17:23:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1647390196; bh=UbQQ43LmkyLVXGvpUA98C6+qAqbFTUAcEfuCwHeUFv0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uxxdIID6/x3a3WzGIa2Wb8swIpbt8+fCZaMASUC1d1Yog01quN/8GK462ApfuxjNV 7r/bF0z33Oi/AZM22jY9V4HM00TjIXllSpKVj5Ejs8hKHajLfK/iBH7KoRqjBYZBee Gjdzbxx5vNzJb2yfH09cdKiJcFtYNTNoSaU7nMKM=
Date: Tue, 15 Mar 2022 17:23:16 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2PTNNAZFR3TXWM2POAHZQHJEVBNHHELKL5CE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4965/1068597195@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4965@github.com>
References: <quicwg/base-drafts/issues/4965@github.com>
Subject: Re: [quicwg/base-drafts] Solidarity bot: Invalid (Issue #4965)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_62312df49877b_585bc6fc135943"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/szk1ZQPNmgLtQGM-jILwTe0oHag>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2022 00:23:19 -0000

I suspect that this is taking an interpretation that this is ableist, but I don't know if this particular usage meets that standard. I pronounce the two words differently even if they share a spelling.

That might be a poor assessment, so I won't insist that it is right. We probably can do better in future, but your conservative position here seems like it is best. Changing carries risks and without a clear signal that this needs to be fixed, doing nothing here is sensible.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4965#issuecomment-1068597195
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4965/1068597195@github.com>

v2.8.7 | Report a Bug | By Email