让 ESLint 更加包容

从一开始，ESLint 项目就致力于成为一个对每个人都热情包容的地方。我们在广泛采用行为规范之前就已经制定了行为准则（甚至在加入 jQuery 基金会，即现在的 OpenJS 基金会之前），并且该项目由来自世界各地的开发者维护，他们代表了各种族、文化和国家。尽管如此，我们理解包容性是一个需要随着学习和成长而不断调整的过程。总有一些方式可以变得更加热情包容，今天我们很高兴与大家分享我们最近的一些努力。

🌐 From its beginning, the ESLint project has sought to be a place that is welcoming and inclusive of everyone. We adopted a code of conduct before doing so was common (even before we joined the jQuery Foundation, now the OpenJS Foundation) and the project has been maintained by a group of developers from all around the world, representing a variety of ethnicities, cultures, and countries. Even so, we understand that inclusivity is a process that must be adapted as we learn and grow. There is always some way to be more welcoming, and today we’re happy to share with you some of our recent efforts.

消除有问题的术语

🌐 Eliminating problematic terminology

我们在项目中进行更改的一个字段是使用更具包容性的术语。我们最近对我们的代码库进行了审计，以查找带有负面含义的词汇。在此过程中，我们发现项目中有几个“blacklist”（黑名单）的实例，不仅在代码内部，还包括 id-blacklist 规则的名称中。

🌐 One of the areas where we’ve made changes in the project is through the use of more inclusive terminology. We recently did an audit of our codebase to look for words with negative connotations. In doing so, we discovered that we had a few instances of the word “blacklist” in the project, not just inside of code but also in the name of the id-blacklist rule.

在 v7.4.0 中，我们将 id-blacklist 规则重命名为 id-denylist，同时提供了一个回退，以确保现有的 ESLint 配置不会中断。在 v7.5.0 中，我们正式弃用了 id-blacklist 规则。我们的政策是不删除已弃用的规则，但我们将不再维护 id-blacklist 规则。任何进一步的更改将仅针对 id-denylist 规则进行。

🌐 In v7.4.0 we renamed the id-blacklist rule to id-denylist while providing a fallback so existing ESLint configs wouldn’t break. In v7.5.0 we officially deprecated the id-blacklist rule. It’s our policy not to remove deprecated rules, but we will no longer be maintaining the id-blacklist rule. Any further changes will be made only to the id-denylist rule.

今后，我们将避免使用以下术语：

🌐 Going forward, we will be avoiding the use of the following terms:

• 黑名单
• 白名单
• 大师
• 奴隶

虽然并非所有这些词都有种族主义起源，但它们都有负面含义，可能会让人感到不适并助长无意识的偏见。我们希望 ESLint 成为一个每个人都能自在参与、为之自豪并贡献的项目，而使用更具包容性的语言有助于实现这一点。

🌐 While not all of these words trace back to racist origins, they do all have negative connotations that can make people uncomfortable and perpetuate unconscious bias. We want ESLint to be a project that everyone is comfortable participating in, and proud of contributing to, and using more inclusive language helps.

主分支怎么样？

🌐 What about the master branch?

像许多开源项目一样，我们的主要开发分支被称为 master。我们正在将每个代码库逐步过渡到使用 main 作为主要开发分支。这将是一个渐进的部署过程，因为我们会从最不活跃的代码库开始，逐步过渡到 eslint，我们最活跃的代码库。我们大量的基础设施工具假设 master 是主要开发分支，因此这将需要一些时间，我们可能还需要等待 GitHub 工具 来完成这项工作。

🌐 Like many open source projects, our primary development branch is called master. We are in the process of transitioning each repository to use main as the primary development branch. This will be a gradual rollout as we work through our least active repositories towards eslint, our most active repository. A large amount of our infrastructure tooling assumes that master is the primary development branch, so it will take us some time and we may need to wait for the GitHub tooling to complete this work.

向前移动

🌐 Moving forward

我们希望每个人都能感到有能力为 ESLint 做出贡献，并且在贡献时感到受欢迎、安全和被包容。这最新的小举措只是我们持续努力的一部分，旨在让环境更具包容性，我们也希望其他开源项目能采取同样的做法。

🌐 We want everyone to feel empowered to contribute to ESLint, and to know that when they do, they feel welcome, safe, and included. This latest small action is just a part of our ongoing effort to more inclusive, and we hope other open source projects will do the same.