Re: [Gendispatch] draft charter text: terminology-related WG

[Fernando Gont <[e-mail]>]

Hi, Sean,

I may have missed part of the discussion (apologies for that!). But my 
questions are:

* Why would one create a WG on terminology, rather than one on diversity?

* Is there a reason for which terminology is something that is deemed of 
utmost importance while there's no concrete effort to try to tackle many 
other aspect that affect diversity (in much more concrete ways)?


Just one effort on terminology reads to me a lot like: "let's be more 
polite in or terminology, while we essentially prevents the IETF from 
becoming a more diverse environment".


Thanks,
Fernando




On 11/2/21 17:39, Sean Turner wrote:
> Hi!,
> 
> Here is some proposed charter text to address the terminology-related WG.
> 
> Cheers,
> spt
> 
> ----------
> 
> Effective Terminology in IETF Documents (TERM)
> ----
> 
> The mission of the IETF as specified in BCP 95 is to produce high quality, relevant technical documents that influence the way people design, use, and manage the Internet. As RFC 7322 explains, "The ultimate goal of the RFC publication process is to produce documents that are readable, clear, consistent, and reasonably uniform." RFCs and Internet-drafts are most effective when they use terminology that is clear, precise, and widely accessible to readers from varying backgrounds and cultures.
> 
> In the years leading up to the chartering of this working group, there has been discussion in the IETF, in other standards organizations, and in the technology industry about the use of certain terms (such as “master/slave” and “blacklist/whitelist”) in technical documentation and whether those and other terms have effects on inclusivity. While opinions vary among IETF participants about this topic, there is general agreement that the IETF community would benefit from informational recommendations about using effective and inclusive terminology in IETF documents.
> 
> The TERM working group is therefore chartered to produce an Informational RFC containing recommendations on terminology to use in technical work produced by the IETF.
> 
> Milestones:
> 
> July 2021: Adopt draft providing informational terminology recommendations
> 


-- 
Fernando Gont
e-mail: [e-mail] || [e-mail]
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1