From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8D15541FD1; Wed, 30 Aug 2023 18:49:20 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 28E474027D; Wed, 30 Aug 2023 18:49:20 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 314F34027C for ; Wed, 30 Aug 2023 18:49:19 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 4E5513200933; Wed, 30 Aug 2023 12:49:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 30 Aug 2023 12:49:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1693414156; x=1693500556; bh=pC4iRJwq5nyFI9Jdk6b31eXPsLoEgOpJj+q RF+LHnpg=; b=IgUspyNE75Cz4IcZa7nQHfwFNgYZVBgtcJfo+weRcU2R+XAb4Ui U3Eme3k7gdmNKBT/YwyAGk7w6l08FNQ63aS6qCdh5O9YLTxTSxiCRALYQ5XaPClY A7AnuUnl+4koUSn5IySQAoWOALIRqZ0XTD3Fnxkh49JaWg0un76aLA8g5djnZ4in RuZRc89+0AbKWt84slTDyhEznby7scm3OF+BPakpghF3tLpNnJ70Ux2G/NtVaE60 PZn2YJtyXZTIfbNWi9IpgeVaF6VK54i5Y2U39rUE2ue6od0inx5HUQXOi/gs7g54 rf5RrAB86Kl0kn3mXUqaxfC+a7xj4e1sjzQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693414156; x=1693500556; bh=pC4iRJwq5nyFI9Jdk6b31eXPsLoEgOpJj+q RF+LHnpg=; b=v5+OBKFD5/nuCR8jtQKB3NyACqXMCF2EKgiyN1UV7p5Kf2Y0Q9c pDEiQY2TszjR0FDz0pz9mRrKdZAuFp4L7HXFz/0vyAyyV41m9/aoGqar7Kpp3aOQ ha6p80RXyOGR1n2KTVAfAfpLY6AS3XfbxsWCET7SrHYaAfEsJwj3uj+nPK95xC9K zQBWF+LfgG/h1U8/lW8hfQlSCLAJgf++AG7+LEW01ZZ+LoA0uUXWmrJH9h2p1yq+ XL4aMWDTzmQA41fch2F7+pef9x/ySBFJKJxfR4EprkO9lVFk35MSlOJm3uagYeTj GX2sTniPkVFVwFiEQgqD5m0LCsAK2gzFh3A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudefkedguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnhepieekueevhffghffhffdvteeftefgleeiudejfeekkefgkeek kefhfedukeejvdelnecuffhomhgrihhnpehinhgtlhhushhivhgvnhgrmhhinhhgrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 30 Aug 2023 12:49:15 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org Subject: Re: [PATCH v2 00/13] Replace us of term abort Date: Wed, 30 Aug 2023 18:49:14 +0200 Message-ID: <846708806.0ifERbkFSE@thomas> In-Reply-To: <20230818174537.290222-1-stephen@networkplumber.org> References: <20230818025249.33994-1-stephen@networkplumber.org> <20230818174537.290222-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 18/08/2023 19:45, Stephen Hemminger: > The term 'abort' is on the inclusive namin Tier 1 word list > as replace when possible. It is possible to do this across > DPDK except the few places that directly call the lib C abort() > function. >=20 > v2 - drop changes to sfc since requires changes to base driver > - cleanup some checkpatch and missing spots >=20 > Rationale (from https://inclusivenaming.org/word-lists/tier-1/abort/) >=20 > The term =E2=80=9Cabort=E2=80=9D frequently appeared in Inclusive Lan= guage > Initiative surveys and standards reviews. Multiple organizations felt > that usage of the word posed an issue worth addressing in their > individual companies and projects. Given this widespread interest, the > INI has decided to offer its own guidance. >=20 > INI recommends replacing =E2=80=9Cabort=E2=80=9D wherever possible. I= n accordance with > the INI=E2=80=99s language framework, the term does not necessarily c= onstitute > a first-order concern. However, because it is such a charged term > outside of computing, =E2=80=9Cabort=E2=80=9D fails to provide a clea= r description of > the action being taken, and serves primarily to distract. There are > numerous other words in the English language that can serve the same > purpose in computing without invoking the emotionally charged cultural > context of =E2=80=9Cabort.=E2=80=9D >=20 > Although the INI debated whether the word =E2=80=9Cabort=E2=80=9D its= elf or the > procedure commonly associated with it (=E2=80=9Cabortion=E2=80=9D) ca= used the > aforementioned distractions, the etymology of the word has a direct > and unambiguous link to the termination of a pregnancy. Alternative > uses of the word =E2=80=9Cabort=E2=80=9D are in use today, such as in > rocketry. However, the INI concluded that the term itself was > insufficiently distanced from its original meaning for those > alternative definitions to be its primary association. >=20 > All this being said, the INI does not advocate for a blanket > replacement of the term. =E2=80=9CAbort=E2=80=9D appears in many stan= dards > organization documents, and is deeply embedded in some operating > systems. As such, the INI acknowledges that the term may need to > be retained in certain contexts to remain in compliance with those > standards, or to preserve accurate documentation for bedrock > functions and processes that are too fundamental to be changed. >=20 > Some organizations have noted that using =E2=80=9Cabort=E2=80=9D in c= ontexts other > than the medical or political serves to de-stigmatize the term, > thereby promoting reproductive rights and bodily autonomy. Conversely, > discouraging the term could be interpreted as accepting a framing that > denies a pregnant person=E2=80=99s right to control their body. The j= udgment > of the INI is that the term causes discomfort or offense without > providing a necessary degree of technical clarity, and therefore it > should be avoided. At some future point, because language changes over > time, =E2=80=9Cabort=E2=80=9D may become a less contentious term; at = that juncture, > the appropriateness of the term may be revisited. I don't feel the rationale should be followed here. If there are better terms, why not. But really, "abort" is not only medical. And banning this word may be felt as a political position, which is not what we want. I am OK to replace if there is a better word in some contexts, but we should not make it forbidden.