├── .devcontainer ├── Dockerfile ├── README.md └── devcontainer.json ├── .editorconfig ├── .github ├── CODEOWNERS ├── ISSUE_TEMPLATE │ └── media_mention.yml └── settings.yml ├── .gitignore ├── .hugo_build.lock ├── LICENSE ├── Makefile ├── README.md ├── SECURITY.md ├── archetypes └── webinar.md ├── assets ├── css │ └── main.css └── js │ └── app.js ├── config.toml ├── content ├── _index.md ├── about.md ├── blog │ ├── _index.md │ ├── ali-siddiqui-bmc-interview.md │ ├── bridging-borders-korea.md │ ├── inclusion-good-for-business.md │ ├── inclusive-infra.md │ ├── kickoff-post.md │ ├── mark-miller-llnl-interview.md │ ├── monique-umphrey-hcc-interview.md │ ├── power-of-words.md │ └── voices-of-the-world-cultural-diversity.md ├── calendar.md ├── code-of-conduct.md ├── faqs.md ├── handbook │ ├── _index.md │ ├── evaluation-framework.md │ ├── how-we-work.md │ └── implementation-path.md ├── media-mentions.md ├── organizations.md ├── outreach.md ├── participate.md ├── related-projects.md ├── sponsor.md ├── webinar │ ├── _index.md │ └── building-equitable-digital-world.md └── word-lists │ ├── _index.md │ ├── no-change │ ├── _index.md │ ├── blackbox.md │ ├── blackout.md │ ├── disable.md │ ├── fair-hiring-practice.md │ ├── fellow.md │ ├── master-inventor.md │ ├── mastermind.md │ ├── parent-child.md │ ├── red-team.md │ ├── whitebox.md │ └── whitelabel.md │ ├── template.md │ ├── tier-1 │ ├── _cripple.md │ ├── _index.md │ ├── _master-slave.md │ ├── _master.md │ ├── abort.md │ ├── blackhat-whitehat.md │ ├── grandfathered.md │ ├── tribe.md │ └── whitelist.md │ ├── tier-2 │ ├── _index.md │ └── sanity-check.md │ └── tier-3 │ ├── _index.md │ ├── blast-radius.md │ ├── end-of-life.md │ ├── evangelist.md │ ├── hallucinate.md │ ├── man-hour.md │ ├── man-in-middle.md │ ├── segregate.md │ └── totem-pole.md ├── generateDocFormats.sh ├── index.pdf ├── layouts ├── _default │ ├── _markup │ │ ├── render-heading.html │ │ └── render-link.html │ ├── baseof.html │ ├── list.html │ ├── section.html │ └── single.html ├── blog │ ├── list.html │ └── single.html ├── index.html ├── partials │ ├── blog │ │ ├── content.html │ │ ├── hero.html │ │ └── post-list.html │ ├── breadcrumb.html │ ├── css.html │ ├── docs │ │ ├── content.html │ │ ├── content_wordlist.html │ │ ├── section-nav_wordlist.html │ │ └── section-wordlist.html │ ├── favicon.html │ ├── footer.html │ ├── functions │ │ └── convertTime.html │ ├── github-edit.html │ ├── home │ │ ├── content.html │ │ └── hero.html │ ├── javascript.html │ ├── menu-loop.html │ ├── navbar.html │ ├── pagination.html │ ├── section-nav.html │ ├── sidebar.html │ ├── social-buttons.html │ └── wordlist │ │ ├── download-section.html │ │ └── terms-list.html ├── shortcodes │ ├── button.html │ ├── calendar.html │ ├── cta.html │ ├── jumbotron.html │ ├── leadership.html │ ├── localize.html │ ├── logos.html │ └── media-mentions.html ├── webinar │ ├── list.html │ └── single.html ├── word-lists │ ├── list.html │ ├── single.html │ └── wordlists.html └── wordlist │ ├── 404.json │ ├── baseof.custom │ ├── baseof.html │ ├── baseof.json.json │ ├── item.json.json │ ├── list.json.json │ ├── section.custom │ ├── section.html │ ├── single.custom │ ├── single.html │ └── single.json.json ├── netlify.toml ├── package.json ├── postcss.config.js ├── static ├── .DS_Store ├── _redirects ├── favicon.png ├── img │ ├── headshots │ │ ├── .DS_Store │ │ ├── abubakar.png │ │ ├── apellet.jpg │ │ ├── bill.png │ │ ├── celeste.png │ │ ├── dale.jpg │ │ ├── ewarnicke.png │ │ ├── jbrooks.jpg │ │ ├── jlee.jpg │ │ ├── jstleger.jpg │ │ ├── lkunz.jpg │ │ ├── mrush.jpg │ │ ├── mschnoor.jpg │ │ ├── priyanka.jpg │ │ ├── stephen.png │ │ └── taylor-waggoner.png │ ├── icons │ │ └── json-file-tiny.png │ ├── layout │ │ ├── hero-bg-compressed.jpg │ │ ├── hero-bg.jpg │ │ ├── hero-bg.png │ │ ├── hero-bg.svg │ │ └── sidebar-bg.svg │ ├── logos │ │ ├── inclusive-naming-logo-black.svg │ │ ├── inclusive-naming-logo.svg │ │ └── sponsors │ │ │ ├── BMC.png │ │ │ ├── Splunk.png │ │ │ ├── Splunk_logo.svg │ │ │ ├── akamai.png │ │ │ ├── canonical-group-limited.svg │ │ │ ├── cdf.svg │ │ │ ├── cisco.svg │ │ │ ├── cncf-color.png │ │ │ ├── cncf-color.svg │ │ │ ├── cncf-white.png │ │ │ ├── extreme-networks-inc.svg │ │ │ ├── geek-zone.svg │ │ │ ├── ibm.svg │ │ │ ├── intel.svg │ │ │ ├── lf-color.png │ │ │ ├── redhat-color.svg │ │ │ ├── sddi-color.svg │ │ │ └── vmware.png │ ├── media-mentions │ │ ├── cncf-stacked-color.svg │ │ ├── joinup.png │ │ ├── nytimes.png │ │ ├── the-register.png │ │ ├── the-register.svg │ │ ├── theCube.png │ │ └── theserverside.png │ └── test │ │ └── architecture.png └── json │ └── dci-lint-config-recommended-v1.json └── tailwind.config.js /.devcontainer/Dockerfile: -------------------------------------------------------------------------------- 1 | # Update the NODE_VERSION arg in docker-compose.yml to pick a Node version: 10, 12, 14 2 | ARG NODE_VERSION=14 3 | FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:${NODE_VERSION} 4 | 5 | # VARIANT can be either 'hugo' for the standard version or 'hugo_extended' for the extended version. 6 | ARG VARIANT=hugo 7 | # VERSION can be either 'latest' or a specific version number 8 | ARG VERSION=latest 9 | 10 | # Download Hugo 11 | RUN apt-get update && apt-get install -y ca-certificates openssl git curl && \ 12 | rm -rf /var/lib/apt/lists/* && \ 13 | case ${VERSION} in \ 14 | latest) \ 15 | export VERSION=$(curl -s https://api.github.com/repos/gohugoio/hugo/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4)}') ;;\ 16 | esac && \ 17 | echo ${VERSION} && \ 18 | wget -O ${VERSION}.tar.gz https://github.com/gohugoio/hugo/releases/download/v${VERSION}/${VARIANT}_${VERSION}_Linux-64bit.tar.gz && \ 19 | tar xf ${VERSION}.tar.gz && \ 20 | mv hugo /usr/bin/hugo 21 | 22 | # Hugo dev server port 23 | EXPOSE 1313 24 | 25 | # [Optional] Uncomment this section to install additional OS packages you may want. 26 | # 27 | # RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ 28 | # && apt-get -y install --no-install-recommends 29 | 30 | # [Optional] Uncomment if you want to install more global node packages 31 | # RUN sudo -u node npm install -g 32 | -------------------------------------------------------------------------------- /.devcontainer/README.md: -------------------------------------------------------------------------------- 1 | # Inclusive Naming Initiative Website Development Container 2 | 3 | ## What is a Development Container? 4 | 5 | * Learn more about [using a Docker container as a development environment in VS Code](https://code.visualstudio.com/docs/remote/containers). 6 | * Learn more about [using a Docker container as a development environment with GitHub Codespaces](https://docs.github.com/en/codespaces/developing-in-codespaces/creating-a-codespace). 7 | 8 | ## Contents 9 | 10 | Based on the [Hugo dev container template](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/hugo) from the `vscode-dev-containers` GitHub repository. 11 | -------------------------------------------------------------------------------- /.devcontainer/devcontainer.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "Hugo (Community)", 3 | "build": { 4 | "dockerfile": "Dockerfile", 5 | "args": { 6 | // Update VARIANT to pick hugo variant. 7 | // Example variants: hugo, hugo_extended 8 | // Rebuild the container if it already exists to update. 9 | "VARIANT": "hugo_extended", 10 | // Update VERSION to pick a specific hugo version. 11 | // Example versions: latest, 0.73.0, 0,71.1 12 | // Rebuild the container if it already exists to update. 13 | "VERSION": "latest", 14 | // Update NODE_VERSION to pick the Node.js version: 12, 14 15 | "NODE_VERSION": "14", 16 | } 17 | }, 18 | 19 | // Set *default* container specific settings.json values on container create. 20 | "settings": {}, 21 | 22 | // Add the IDs of extensions you want installed when the container is created. 23 | "extensions": [ 24 | "bungcip.better-toml", 25 | "davidanson.vscode-markdownlint" 26 | ], 27 | 28 | // Use 'forwardPorts' to make a list of ports inside the container available locally. 29 | "forwardPorts": [ 30 | 1313 31 | ], 32 | 33 | // Use 'postCreateCommand' to run commands after the container is created. 34 | // "postCreateCommand": "uname -a", 35 | 36 | // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. 37 | "remoteUser": "node" 38 | } 39 | -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | end_of_line = lf 5 | insert_final_newline = true 6 | 7 | [Makefile] 8 | indent_style = tab 9 | 10 | [*.{html,js,json,md,sass,yaml}] 11 | indent_style = space 12 | indent_size = 2 13 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # CODEOWNERS reference: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners 2 | 3 | # These owners will be the default owners for everything in 4 | # the repo. Unless a later match takes precedence, 5 | # the following users/teams will be requested for 6 | # review when someone opens a pull request. 7 | * @inclusivenaming/website-maintainers 8 | 9 | # Enforces admin protections for repo configuration via probot settings app. 10 | # ref: https://github.com/probot/settings#security-implications 11 | .github/settings.yml @inclusivenaming/infra 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/media_mention.yml: -------------------------------------------------------------------------------- 1 | name: Media Mentions 2 | description: Create an issue to add Inclusive Naming Initiative media mentions 3 | title: "[Media Mentions] Issue Title" 4 | labels: [documentation] 5 | assignees: 6 | - gkarthiks 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thanks for taking the time to let us know about a media mention of Inclusive Naming Initiative. This helps us in keeping the website up-to-date. 12 | 13 | - type: textarea 14 | id: media 15 | attributes: 16 | label: What's the name of the site/media that mentioned Inclusive Naming Initiative? 17 | description: For example `New York Times`. 18 | validations: 19 | required: true 20 | 21 | - type: input 22 | id: media-link 23 | attributes: 24 | label: What is the URL to the article that mentioned/featured INI? 25 | placeholder: Copy paste the entire URL from the browser tab that has the article opened. 26 | validations: 27 | required: true 28 | -------------------------------------------------------------------------------- /.github/settings.yml: -------------------------------------------------------------------------------- 1 | repository: 2 | # See https://developer.github.com/v3/repos/#edit for all available settings. 3 | 4 | # The name of the repository. Changing this will rename the repository 5 | name: website 6 | 7 | # A short description of the repository that will show up on GitHub 8 | description: Website for the Inclusive Naming Initiative 9 | 10 | # A URL with more information about the repository 11 | homepage: https://inclusivenaming.org/ 12 | 13 | # See https://docs.github.com/en/rest/reference/teams#add-or-update-team-repository-permissions for available options 14 | teams: 15 | # Admin 16 | - name: infra 17 | # The permission to grant the team. Can be one of: 18 | # * `pull` - can pull, but not push to or administer this repository. 19 | # * `push` - can pull and push, but not administer this repository. 20 | # * `admin` - can pull, push and administer this repository. 21 | # * `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. 22 | permission: admin 23 | 24 | # Maintain 25 | - name: website-maintainers 26 | permission: maintain 27 | 28 | # Collaborators: give specific users access to this repository. 29 | # See https://docs.github.com/en/rest/reference/collaborators for available options 30 | collaborators: [] 31 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Hugo-generated assets 2 | public/ 3 | resources/ 4 | 5 | # npm assets 6 | node_modules/ 7 | 8 | # files 9 | package-lock.json 10 | yarn.lock 11 | 12 | .idea 13 | .DS_Store 14 | .gitconfig -------------------------------------------------------------------------------- /.hugo_build.lock: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/.hugo_build.lock -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | yarn: 2 | yarn 3 | 4 | serve: yarn 5 | hugo server \ 6 | --buildDrafts \ 7 | --buildFuture \ 8 | --disableFastRender 9 | 10 | production-build: 11 | hugo \ 12 | --minify 13 | 14 | preview-build: 15 | hugo \ 16 | --baseURL $(DEPLOY_PRIME_URL) \ 17 | --buildDrafts \ 18 | --buildFuture \ 19 | --minify 20 | 21 | open: 22 | open https://cncf-hugo-starter.netlify.com 23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Inclusive Naming Initiative 2 | 3 | This repository is a [Hugo](https://gohugo.io/) website for the Inclusive Naming Initiative. 4 | 5 | ## Using this repository 6 | 7 | This repository uses: 8 | 9 | * **[Hugo](https://gohugo.io/)** as a static site generator. Hugo is [Golang](https://golang.org)-based, so you'll need that as well. 10 | * **[Bootstrap 4.5.x](https://getbootstrap.com/docs/4.5/getting-started/introduction/)** as a CSS framework 11 | * **[Netlify](https://www.netlify.com/)** for building, hosting, and DNS management 12 | 13 | ## Running locally 14 | 15 | Make sure you have [Hugo website engine](https://gohugo.io/getting-started/installing/), [npm](https://www.npmjs.com/) and [yarn](https://yarnpkg.com/) installed. Clone this repository and run the following two commands in its directory: 16 | 17 | ```shell 18 | # Install npm assets 19 | yarn 20 | 21 | # Run the server locally 22 | make serve 23 | ``` 24 | 25 | ## Running on Netlify 26 | 27 | Netlify is a CI/CD build tool and hosting solution for (among other things) static sites. We **strongly** recommend using Netlify unless you have a good reason not to. 28 | 29 | This repository comes with a pre-configured [`netlify.toml`](https://github.com/cncf/hugo-netlify-starter/blob/master/netlify.toml) file. To build to Netlify: 30 | 31 | 1. Go to [netlify.com](https://netlify.com) and sign up. We recommend signing up using a GitHub account. 32 | 2. Click **New Site from Git**, and give Netlify access to your GitHub account. 33 | > **Note:** For projects with lots of contributors, it can be handy to create a general/bot account instead of granting access with a personal account. 34 | 35 | 3. Install Netlify with access to your documentation site repository. 36 | 4. Leave all other settings as default and click **Deploy Site**. 37 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | This repository holds the content for the 4 | Inclusive Naming Initiative [website](https://inclusivenaming.org). 5 | 6 | Is is a static site built with 7 | [Hugo](https://gohugo.io/) framework for building out the content, 8 | and 9 | [Bootstrap](https://getbootstrap.com/docs/4.5/getting-started/introduction/) 10 | as the CSS (styling) framework. 11 | 12 | It is unlikely you have found security-related bug in the content in this 13 | repository, as opposed to the frameworks listed above. But if you have, 14 | please [open an issue](https://github.com/inclusivenaming/org/issues). 15 | -------------------------------------------------------------------------------- /archetypes/webinar.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "{{ replace .Name "-" " " | title }}" 3 | date: {{ .Date }} 4 | draft: true 5 | description: "" 6 | registration_link: "" 7 | utc_datetime: "" # Use format like "2024-08-15T14:00:00Z" 8 | 9 | # Manually add formatted time strings for display 10 | time_los_angeles: "" 11 | time_new_york: "" 12 | time_london: "" 13 | time_amsterdam: "" 14 | time_mumbai: "" 15 | time_sydney: "" 16 | 17 | recording_link: "" # Link to video recording if available 18 | 19 | presenters: [] # List of presenter names 20 | --- 21 | 22 | Add the main content/details of the webinar here. -------------------------------------------------------------------------------- /assets/js/app.js: -------------------------------------------------------------------------------- 1 | // Mobile menu toggle 2 | const setupMobileMenu = () => { 3 | const mobileMenuButton = document.getElementById('mobile-menu-button'); 4 | const mobileMenu = document.getElementById('mobile-menu'); 5 | 6 | if (mobileMenuButton && mobileMenu) { 7 | mobileMenuButton.addEventListener('click', () => { 8 | mobileMenu.classList.toggle('hidden'); 9 | }); 10 | } 11 | }; 12 | 13 | // Smooth scrolling 14 | const smoothScroll = () => { 15 | document.querySelectorAll('a[href^="#"]').forEach(anchor => { 16 | anchor.addEventListener('click', function (e) { 17 | const href = this.getAttribute('href'); 18 | 19 | if (href !== '#' && href !== '#0') { 20 | const target = document.querySelector(href); 21 | 22 | if (target) { 23 | e.preventDefault(); 24 | 25 | target.scrollIntoView({ 26 | behavior: 'smooth', 27 | block: 'start' 28 | }); 29 | } 30 | } 31 | }); 32 | }); 33 | }; 34 | 35 | // Fade in elements as they come into view 36 | const setupFadeInElements = () => { 37 | // Add fade-in class to elements EXCEPT headers 38 | document.querySelectorAll('.card, .section, .feature, .image-container').forEach(el => { 39 | el.classList.add('fade-in'); 40 | }); 41 | 42 | const fadeInElements = document.querySelectorAll('.fade-in'); 43 | 44 | const checkFadeInElements = () => { 45 | fadeInElements.forEach(element => { 46 | const elementTop = element.getBoundingClientRect().top; 47 | const elementHeight = element.offsetHeight; 48 | const windowHeight = window.innerHeight; 49 | 50 | if (elementTop < windowHeight - elementHeight / 2) { 51 | element.classList.add('visible'); 52 | } 53 | }); 54 | }; 55 | 56 | // Check elements on load and scroll 57 | checkFadeInElements(); 58 | window.addEventListener('scroll', checkFadeInElements); 59 | }; 60 | 61 | // Initialize everything when the DOM is ready 62 | document.addEventListener('DOMContentLoaded', () => { 63 | console.log("Welcome to the Hugo + Tailwind starter"); 64 | 65 | setupMobileMenu(); 66 | smoothScroll(); 67 | setupFadeInElements(); 68 | }); 69 | -------------------------------------------------------------------------------- /config.toml: -------------------------------------------------------------------------------- 1 | baseURL = "https://inclusivenaming.org" 2 | title = "Inclusive Naming Initiative" 3 | disableKinds = ["taxonomy", "taxonomyTerm"] 4 | copyright = "The Inclusive Naming Initiative authors and collaborating organizations" 5 | enableGitInfo = true 6 | summaryLength = 20 7 | 8 | buildFuture = true 9 | 10 | [mediaTypes] 11 | [mediaTypes.'text/html'] 12 | suffixes = ['custom'] 13 | 14 | [outputFormats] 15 | [outputFormats.custom] 16 | mediaType = 'text/html' 17 | 18 | [markup.highlight] 19 | style = "paraiso-dark" 20 | 21 | [blackfriday] 22 | extensions = ["hardLineBreak"] 23 | 24 | [params] 25 | font_awesome_version = "5.12.0" 26 | description = "Helping projects and companies make consistent, responsible choices to remove harmful language" 27 | favicon = "favicon.png" 28 | repositoryUrl = "https://github.com/inclusivenaming" 29 | contentDir = "/content/" 30 | [params.logos] 31 | navbar = "inclusive-naming-logo.svg" 32 | 33 | [[params.social]] 34 | name = "Twitter" 35 | url = "https://twitter.com/inclusivenaming" 36 | icon = "fab fa-twitter" 37 | 38 | [[params.social]] 39 | name = "YouTube" 40 | url = "https://www.youtube.com/channel/UCP1oEIxHSl77RCWRPwRjdiQ" 41 | icon = "fab fa-youtube" 42 | 43 | [[params.social]] 44 | name = "GitHub" 45 | url = "https://github.com/inclusivenaming" 46 | icon = "fab fa-github" 47 | 48 | [[params.social]] 49 | name = "LinkedIn" 50 | url = "https://www.linkedin.com/company/inclusive-naming/" 51 | icon = "fab fa-linkedin-in" 52 | 53 | [[params.social]] 54 | name = "Mailing list" 55 | url = "https://groups.google.com/g/inclusivenaming" 56 | icon = "fas fa-envelope" 57 | 58 | [[params.social]] 59 | name = "Slack Invite" 60 | url = "https://communityinviter.com/apps/inclusive-naming/invite" 61 | icon = "fab fa-slack" 62 | 63 | [[params.fonts]] 64 | name = "Cairo" 65 | sizes = [300, 400, 600, 700, 900] 66 | type = "sans_serif" 67 | 68 | [[params.fonts]] 69 | name = "Lexend Deca" 70 | sizes = [400] 71 | type = "heading_font" 72 | 73 | [[menu.main]] 74 | name = "About" 75 | url = "#" 76 | weight = 1 77 | identifier ="about" 78 | 79 | [[menu.main]] 80 | name = "About the initiative" 81 | url = "/about" 82 | parent = "about" 83 | weight = 1 84 | 85 | [[menu.main]] 86 | name = "Get involved" 87 | url = "#" 88 | weight = 3 89 | identifier = "getinvolved" 90 | 91 | [[menu.main]] 92 | name = "Participate" 93 | url = "/participate" 94 | parent = "getinvolved" 95 | weight = 1 96 | 97 | [[menu.main]] 98 | name = "Sponsor" 99 | url = "/sponsor" 100 | parent="getinvolved" 101 | weight = 2 102 | 103 | [[menu.main]] 104 | name = "Meeting calendar" 105 | url = "/calendar" 106 | parent = "getinvolved" 107 | weight = 3 108 | 109 | [[menu.main]] 110 | name = "Code of conduct" 111 | url = "/code-of-conduct" 112 | parent = "getinvolved" 113 | weight = 4 114 | 115 | [[menu.main]] 116 | name = "Webinars" 117 | url = "/webinar" 118 | parent = "getinvolved" 119 | weight = 5 120 | 121 | [[menu.main]] 122 | name = "Word lists" 123 | url = "#" 124 | identifier = "lists" 125 | weight = 5 126 | 127 | [[menu.main]] 128 | name = "Overview" 129 | url = "/word-lists" 130 | parent = "lists" 131 | weight = 1 132 | 133 | [[menu.main]] 134 | name = "Tier 1: Replace Immediately" 135 | url = "/word-lists/tier-1" 136 | parent = "lists" 137 | weight = 2 138 | 139 | [[menu.main]] 140 | name = "Tier 2: Strongly Consider Replacing" 141 | url = "/word-lists/tier-2" 142 | parent = "lists" 143 | weight = 3 144 | 145 | [[menu.main]] 146 | name = "Tier 3: Recommendations to Replace" 147 | url = "/word-lists/tier-3" 148 | parent = "lists" 149 | weight = 4 150 | 151 | [[menu.main]] 152 | name = "No Changes Recommended" 153 | url = "/word-lists/no-change" 154 | parent = "lists" 155 | weight = 5 156 | 157 | [[menu.main]] 158 | name = "Wordlist Template" 159 | url = "/word-lists/template" 160 | parent = "lists" 161 | weight = 6 162 | 163 | [[menu.main]] 164 | name = "Handbook" 165 | url = "/handbook" 166 | identifier = "lang" 167 | weight = 6 168 | 169 | [[menu.main]] 170 | name = "Related projects" 171 | url = "/related-projects" 172 | weight = 7 173 | 174 | [[menu.main]] 175 | name = "FAQs" 176 | url = "/faqs" 177 | weight = 8 178 | 179 | [[menu.main]] 180 | name = "News & Media" 181 | url = "#" 182 | weight = 9 183 | identifier = "news-and-media" 184 | 185 | [[menu.main]] 186 | name = "Blog" 187 | url = "/blog" 188 | parent = "news-and-media" 189 | weight = 1 190 | 191 | [[menu.main]] 192 | name = "Media mentions" 193 | url = "/media-mentions" 194 | parent = "news-and-media" 195 | identifier = "media-mentions" 196 | weight = 2 197 | 198 | [[menu.main]] 199 | name = "Presentations" 200 | url = "https://github.com/inclusivenaming/org/tree/main/ws-marketing" 201 | parent = "news-and-media" 202 | identifier = "presentations" 203 | weight = 3 -------------------------------------------------------------------------------- /content/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Inclusive Naming Initiative" 3 | layout: wordlist 4 | --- 5 | 6 | {{< jumbotron title="Get involved" bgcolor="#2478D3" textcolor="#FFFFFF" align="text-center" >}} 7 | 8 | 9 | {{< cta >}} 10 | 11 | {{< /jumbotron >}} 12 | -------------------------------------------------------------------------------- /content/about.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "About the Inclusive Naming Initiative" 3 | --- 4 | 5 | The Inclusive Naming Initiative’s mission is to promote and facilitate replacing harmful and exclusionary language in information technology 6 | 7 | 8 | ## Activities, Goals, and Deliverables 9 | 10 | We're looking to bring together a community of information technology organizations and professionals to collaboratively: 11 | 12 | * Define **processes** for removing harmful and exclusionary language from software, APIs, standards, documentation, and other IT-related materials 13 | * Develop **resources and tools** such as a comprehensive list of harmful terms and suggested replacements, language evaluation frameworks, templates, and guidance and best practice materials 14 | * Recommend **implementation paths** for different use cases 15 | * Provide **tooling** to measure implementation success 16 | * Act as a platform for **community recognition** of organizations actively doing the work 17 | 18 | Sound interesting? 19 | 20 | {{< button "/participate/" "Get involved" >}} 21 | 22 | -------------------------------------------------------------------------------- /content/blog/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Blog 3 | linkTitle: Blog 4 | --- 5 | 6 | -------------------------------------------------------------------------------- /content/blog/ali-siddiqui-bmc-interview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Moving the needle on inclusive language. Ali Siddiqui" 3 | date: 2021-08-11 4 | slug: inclusive-language-inititives-bmc 5 | author: Oshrat Nir 6 | --- 7 | 8 | Welcome to our series Moving the Needle on inclusive language. In this series, we will be talking to leaders in the cloud native space as they share the inclusive naming initiatives they care about. This will include tools, activities, and results they have discovered along the way. 9 | 10 | [Ali](https://www.linkedin.com/in/ali-siddiqui-4bb3921/) joined BMC in early 2020 as Chief Product Officer with end-to-end responsibility for BMC’s product portfolio. Before joining BMC, Ali was at Broadcom where he was the head of AI Ops and IT Ops for their enterprise software division. Prior to that, he led the IT Ops division at CA Technologies, and the cloud and virtualization group at Cisco. He has also held leadership roles at Oracle and VMWare. His goals include spurring ongoing innovation and increasing customer value. With over 30 years of industry experience in managing, building, and growing successful software businesses, he is sure to meet them. 11 | 12 | **What triggered the inclusive language initiative at BMC?** 13 | 14 | BMC’s Diversity, Equity, and Inclusion team brought it to my attention! 15 | 16 | **You hold a senior role in the company. Do you think inclusive naming initiatives should happen top-down or bottom-up?** 17 | 18 | Both. It requires top-down support and leadership and bottom-up effort. It takes a lot of work and collaboration from all parties. 19 | 20 | **What steps have you taken to eliminate bias from the language you use at BMC? What will keep the initiative moving forward?** 21 | 22 | For starters, I have been working on personally checking my language. I understand my responsibility as a leader to set an example. 23 | 24 | I have also discussed with my direct reports and team members that eliminating bias from our language is not an option, it is a must-have for our business to succeed. I have given them guidance and support in engaging them and their teams through awareness. 25 | 26 | **BMC is a multinational company. How do you account for the different languages your employees use?** 27 | 28 | We try to always use English in our workplace interactions, meetings, and business dealings as a standard. 29 | 30 | > "One measure of leadership is the caliber of people who choose to follow you." ~ Dennis A. Peer 31 | 32 | In this interview, I have found Ali Siddiqui to be an ally of inclusive naming. He is well aware of the biases ingrained in the language we use daily in our workplaces. He takes action at a personal level, by being aware of the words he uses. He deliberately chooses to use inclusive language. He also takes action at a leadership level. He counsels his direct reports, and through them, the respective teams, to adopt the use of inclusive language. 33 | 34 | If you’d like to be featured or know someone who’d be a great fit, tweet us [@inclusivenaming](https://twitter.com/inclusivenaming) and spread the love. 35 | -------------------------------------------------------------------------------- /content/blog/inclusive-infra.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Towards More Inclusive Infrastructure" 3 | date: 2021-04-14 4 | slug: inclusive-infra 5 | author: Reinhardt Quelle 6 | --- 7 | This post will be short, because it really is _that simple_. 8 | 9 | My team at Cisco builds platform services that underlie the multiple projects within the Emerging Technology and Incubation group.  Our mission is to build 'paved roads' for developers; we create common reusable patterns and services that any engineer or venture needs to deliver an application. 10 | 11 | Recently, one of my peers pinged me in chat and pointed out that someone on my team had just announced the expansion of our CI build environment with the addition of "slaves 10-15". She inquired about the use of the term “slave” and I immediately knew she was pointing to a form of microaggression in code and something not in line with our values. 12 | 13 | 14 | She is right.  It's not only inappropriate to perpetuate the use of terms that are harmful to our diverse employees; it's also specifically against our company [policy](https://www.cisco.com/c/en/us/about/social-justice/inclusive-language-policy.html) to do so. 15 | 16 | Since these hosts had been created via "infrastructure as code", it was a simple matter to send a pull request to the repo containing that code with more inclusive - and indeed more descriptive - names, and re-deploy. 17 | 18 | But, since we are site reliability engineers, we are conditioned to ask "how could we prevent this from happening again?" Policy is fine, but we like to fix things in code. We enforce computer language standards and security policies via linters in our pipelines, so why not inclusive language? 19 | 20 | Again, it really is this simple. To make our platform more inclusive: 21 | 22 | > ```rules + audit = change + progress``` 23 | 24 | Indeed, a quick web search turns up not just one, but several open source projects. I posted a request to my team that afternoon, and when I got back into the office in the morning I found one of my platform engineers had already done a quick survey of the available tools and added a stage to our common build pipeline. More "X-as-code" for the win. We didn't have to modify hundreds of builds, but simply updated our common pipeline code which is already in place to do security, licensing, and other types of scans. 25 | 26 | This is where things became even more interesting. When announcing the change to let all of our engineering teams (SRE and product) know that they would be seeing warnings from the inclusive linter in their build outputs, we were immediately met with resistance. That then prompted a very healthy discussion around the "why" and the underlying context. What was even more interesting was the response from the global team - it turns out that our linter is very US-centric and is missing language that is problematic to our international community. 27 | 28 | Yes, there is more to be done – working with upstream projects, expanding to the other groups in our company, reporting back to our Office of Inclusive Futures, improving tools, and the list goes on. But, the most important thing is to just take the first step. 29 | 30 | This has been an incredibly rewarding experience; in one simple exercise, we have seen the power of infrastructure as code, the open source community, and robust collaboration technology that "powers an inclusive future for all". 31 | 32 | This was cross-posted from our [Cisco Tech Blog](https://ciscotechblog.com/blog/inclusive-infrastructure/). We are excited to be a part of the [Inclusive Naming Initiative](https://inclusivenaming.org) and we are looking forward to working with this community. Through the INI and the open source community at large, we believe we can illuminate and amplify the efforts happening across our whole industry. 33 | 34 | 35 | Reinhardt Quelle 36 | Director, Site Reliability Engineering, Cisco Emerging Technologies and Incubation 37 | 38 | --- 39 | 40 | Tools: 41 | 42 | * [woke](https://github.com/get-woke/woke) 43 | * [inclusivelint-lib](https://github.com/inclusivelint/inclusivelint-lib) 44 | 45 | References: 46 | 47 | * [Inclusive Naming Initiative](https://inclusivenaming.org) 48 | * [Linux Kernel inclusive-terminology merge tag](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=49decddd39e5f6132ccd7d9fdc3d7c470b0061bb) 49 | * [Cisco Social Justice Beliefs and Actions ](https://www.cisco.com/c/en/us/about/social-justice.html) 50 | 51 | -------------------------------------------------------------------------------- /content/blog/kickoff-post.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Welcome to the Inclusive Naming Project" 3 | date: 2021-04-13 4 | slug: welcome-post 5 | --- 6 | **A Short History** 7 | 8 | The Inclusive Naming Initiative was born out of the efforts by the Kubernetes community to address non inclusive language, which coalesced with the Black Lives Matter movement that rose to prominence last year. 9 | 10 | Kubernetes is the fastest growing open-source software project in history and is now used by companies around the world to make software development faster, and better. As a leading force, Kubernetes has set the bar for many software projects. However, Kubernetes wanted to include the larger community because nothing in open source is ever done alone. Open-source is created by a global community of developers. The very ethos of open-source is that many minds working together can produce a better outcome and that everybody who uses the OSS software can then share in the benefits. Thus, the Inclusive Naming Initiative was born to give every organization, project, company, individual, and body, the language and tools to make their work more inclusive and welcoming. 11 | 12 | **How We Work** 13 | 14 | The Inclusive Naming Initiative is a working group that was formed to inform the decisions that are ultimately made by software standards setting bodies. INI is not a standards setting body, nor a replacement for one, INI is working in partnership _with_ the various standards bodies in a supportive way, to inform the work they do around changing non-inclusive terms. 15 | 16 | INI aims to provide our industry, including standards bodies, with documentation on how to change terms without depreciation, frameworks, a glossary of offensive coding terms that should be changed, and developer input on how to make the changes so that they are made everywhere, not just in one company, or in one open source software project. 17 | 18 | INI provides a home for developers to collaborate on how to best do this work. We do not want software code that is non-inclusive because it is harmful to society. Nor do we want software code that breaks because changes made in one place don’t translate down the line. As we all work together towards a unifying goal, we’ll get these changes made faster with less disruption to the software that runs companies around the world. The key thing to remember, this work will never be finished and a standard is not absolute. Nor is everyone going to agree all the time, but INI shows there are plenty of us who are committed to making change. 19 | 20 | **How to get involved** 21 | 22 | We are always looking for new contributors and we would love to have you onboard. The easiest place to start is to join the mailing list: [inclusivenaming@googlegroups.com](https://groups.google.com/g/inclusivenaming), and identify yourself and your company. [Join a workstream](https://inclusivenaming.org/workstreams/) that fits your interest whether it be open source or marketing, we have a space for everyone no matter their background. We are also looking for people to step up and tell the stories around inclusive language in their organizations and be included in our blog. Please reach out to the marketing Slack channel with your story. 23 | 24 | Next, view the project board and [file issues](https://github.com/inclusivenaming/org/issues). The Project Board is where we track the work being done for the Inclusive naming initiative. You can also file issues for work you’d like to see or open questions you have via the [inclusivenaming/org repository](https://github.com/inclusivenaming/org). 25 | 26 | Finally, make changes in your projects! Use the resources we’ve compiled so far –[Word replacement list](https://inclusivenaming.org/word-lists/overview) , [Implementation path](https://inclusivenaming.org/language/implementation-path/) , and the [Language evaluation framework](https://inclusivenaming.org/language/evaluation-framework/) framework and start making changes in your own projects! This is the most impactful way to get involved and our goal as an initiative. 27 | -------------------------------------------------------------------------------- /content/blog/voices-of-the-world-cultural-diversity.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Voices of the World: Embracing Cultural Diversity Through Language" 3 | date: 2025-05-05 4 | slug: voices-of-the-world-cultural-diversity 5 | author: Aisha Shaibu-Salami 6 | --- 7 | 8 | **Why Language Isn't Universal and That's a Good Thing** 9 | 10 | In the previous [blog post](/blog/power-of-words/) we explored how inclusive naming helps shape equitable systems in tech. But inclusion doesn’t stop at replacing a few terms, it’s about recognizing the richness of voices from all over the world and how culture influences communication. 11 | 12 | As we move further into the global digital era, it's critical to understand that language is not neutral. It's a reflection of identity, tradition, and worldview. And in the tech industry, where collaboration is increasingly cross-border and multicultural, this understanding can make the difference between building systems that exclude or empower. 13 | 14 | ## **Celebrating Language Through Culture** 15 | 16 | This second phase shines a light on the diversity of voices across the globe. We're highlighting how language is shaped by culture, context, and community, and why honoring that matters in everything from code to customer service. 17 | 18 | ### **Different Cultures, Different Expressions** 19 | 20 | Every language carries its rhythm, structure, and soul, deeply influenced by the culture it originates from. Here are some examples: 21 | 22 | - **Nigeria**: With over 500 languages spoken, Nigeria's linguistic diversity reflects its rich cultural tapestry. Language here often conveys collective identity and respect for hierarchy. For an in-depth analysis, refer to the article on [Language and Culture: Nigerian Perspective](https://www.researchgate.net/publication/309277107_Language_and_Culture_Nigerian_Perspective).[ResearchGate](https://www.researchgate.net/publication/309277107_Language_and_Culture_Nigerian_Perspective) 23 | - **Japan**: Honorifics and formality are deeply embedded in both spoken and written Japanese, reflecting cultural values of respect and harmony. To understand the intricacies of Japanese honorifics, explore this comprehensive guide on [Honorific Speech in Japanese](https://en.wikipedia.org/wiki/Honorific_speech_in_Japanese). 24 | - **Germany**: The German language is known for its compound words and logic-based grammar, supporting precision and structure, qualities mirrored in its strong engineering reputation. Learn more about German compound words in this article: [What Are German Compound Words (And How to Make Your Own)](https://tandem.net/blog/german-compound-words). [Tandem - Speak Any Language](https://tandem.net/blog/german-compound-words) 25 | 26 | ### **How This Shapes Tech Communication** 27 | 28 | This diversity affects how instructions are followed, how feedback is given, how error messages are understood, and even how collaborative tools are used. A culturally insensitive phrase in one region might unintentionally confuse or offend. A “direct” message, meant as efficient, could be read as “harsh” in another culture. 29 | 30 | ### **Inclusive Language = Culturally Aware Language** 31 | 32 | When we speak about inclusive naming, we must also speak about cultural relevance. It's not just about removing offensive terms, it’s about choosing words that are clear, respectful, and accessible to people from all walks of life. 33 | 34 | ## **What We’re Doing Differently** 35 | 36 | As part of the objective of this initiative, we are 37 | 38 | - Building language-aware tools — Promoting tools that support multilingual documentation, translation support, and culturally sensitive UX writing. 39 | - Encouraging empathy-driven design — Tech teams are being urged to consider how localized language, time zones, symbols, humor, and tone affect global user experience. 40 | - Challenging Anglocentrism — While English remains dominant in tech, it’s time to question its default status. Multilingual spaces deserve equal attention and respect. 41 | 42 | ## **Words Build Bridges** 43 | 44 | The words we use can build bridges or create barriers. By celebrating linguistic and cultural diversity, we are doing more than avoiding exclusion; we are embracing connection, empathy, and innovation. 45 | 46 | Let’s build systems, communities, and cultures that reflect the real world’s richness, one word, one voice, and one culture at a time. -------------------------------------------------------------------------------- /content/calendar.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Calendar 3 | --- 4 | 5 | To receive invitations to meetings on this calendar, join the Inclusive Naming Initiative's mailing list at [inclusivenaming@googlegroups.com](https://groups.google.com/g/inclusivenaming). 6 | 7 | 8 | {{< calendar >}} -------------------------------------------------------------------------------- /content/faqs.md: -------------------------------------------------------------------------------- 1 | 2 | --- 3 | title: "Frequently asked questions" 4 | --- 5 | 6 | 7 | ## What is inclusive naming about? 8 | 9 | The software industry sometimes uses certain words, like blacklist and slave, that may carry a great deal of emotional and historical baggage. We are encouraging projects to choose phrases that clearly communicate the technical meaning, without using metaphors or colloquialisms. 10 | 11 | This has the dual purpose of removing problematic terms, and also communicating more clearly, particularly to those who are working in a secondary language. 12 | 13 | Our goals are to identify where problematic terms are used, collaborate on replacement terminology, support project contributors in making updates, and report on joint progress. 14 | 15 | ## Why is this important? 16 | 17 | If software is truly meant to be inclusive and a place where anyone can participate, it must be welcoming to all. If words or phrases convey secondary unintended meanings to our audience (or are simply confusing!) we are potentially limiting participation in our projects, which is antithetical to this goal. 18 | 19 | ## What terms are we recommending you consider? 20 | 21 | We have identified the terms "master/slave" and "whitelist/blacklist" to work on because these are considered most visible and problematic across the industry. 22 | 23 | Over time, we may recommend consideration of other terms, such as words that reference mental health, gender, physical handicaps, and several other categories. We may also give tips on avoiding colloquialisms that simply don't translate well or prove a barrier to understanding. 24 | 25 | ## What are the recommended replacement terms? 26 | 27 | See the word replacement list for all terms we recommend replacing. 28 | 29 | ## Oh no! Slippery slope! Newspeak! 30 | 31 | We've heard concerns that this initiative 32 | puts us on a slippery slope to Newspeak portrayed in the 1984 dystopia 33 | by George Orwell. This initiative is completely different from Newspeak. 34 | Newspeak involved multiple changes but the most essential were: 35 | 36 | * Removing precise words in favor of general words so that it would become difficult to form precise thoughts 37 | * Using the opposite word for the true situation to disguise what's really happening 38 | 39 | Everything in the conscious language initiative is *the exact opposite* of that. 40 | 41 | For example, "waived failures" is both more precise and more accurate than "whitelist"; 42 | 43 | "Primary" is both more precise and more accurate than "master" in projects that have made the switch. 44 | 45 | The goal of this project is to use more precise words, in order to avoid 46 | unintended connotations that some common words and phrases have. Not 47 | only does this eliminate the hurt caused by those connotations, it also 48 | improves understanding, particularly for people who are reading in a 49 | second language, where those idioms may be confusing. 50 | 51 | ## How can I educate myself on why these terms are problematic? 52 | 53 | Here are some resources on the topic: 54 | 55 | * [Welcoming Nomenclature](https://www.youtube.com/watch?v=hZuFeFuazwo) - Community Central presentation by Rich Bowen (Red Hat) 56 | * [Is It Enough To Remove Words With Racist Connotations From Tech Language? Hint: No](https://www.npr.org/2020/07/09/889502179/is-it-enough-to-remove-words-with-racist-connotations-from-tech-language-hint-no) - NPR interview with web developer Caroline Karanja 57 | * [Why is everything white?](https://www.bbc.com/news/av/world-us-canada-52988605/muhammad-ali-why-is-everything-white) (1971) - interview with Muhammed Ali 58 | * [That Word Black (2014)](http://mcwriting11.blogspot.com/2014/06/that-word-black-by-langston-hughes.html) - blog post by Langston Hughes 59 | * [Broken Metaphor: The Master-Slave Analogy in Technical Literature (2007)](https://www.jstor.org/stable/40061475?seq=1) - article in JSTOR, requires free membership to read 60 | * [Terminology, Power and Oppressive Language](https://tools.ietf.org/id/draft-knodel-terminology-00.html) - article with recommendations by Mallory Knodel and Niels ten Oever 61 | * [Why "master" matters](https://twitter.com/mislav/status/1270388510684598272) - A twitter thread. 62 | 63 | ## How do I get my organization involved? 64 | 65 | * Join our [mailing list](https://groups.google.com/g/inclusivenaming) to receive project updates and invitations to community meetings. 66 | * Identify key people in your organization who can represent this effort in an ongoing fashion 67 | * Read our Implementation Guide and other resources to start making effective changes 68 | -------------------------------------------------------------------------------- /content/handbook/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Inclusive Naming Initiative - Handbook" 3 | --- 4 | 5 | ## Overview 6 | 7 | The INI Handbook is the public resource of the Inclusive Naming Initiative, making available all the resources and links that will enable to community to collaborate better. It also serves as a single source of truth for how the initiative works. 8 | 9 | ## Table of Content 10 | -------------------------------------------------------------------------------- /content/handbook/how-we-work.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "How the INI community works" 3 | --- 4 | 5 | The Inclusive Naming Initiative understands the diversity of our community, that's why we constantly iterate our processes to make it easier to join the community and contribute. We are mostly an asynchronous community, which means we only meet once a month during our Monthly Contributors sync, while contributors work at their pace using our [Work plan sheet](https://docs.google.com/spreadsheets/d/1rf4HbPA7nTyrpGByioyKvdJIfZCbBLSEI67_Nf9M6dA/edit?gid=0#gid=0). Below is the process flow: 6 | 7 | - A member of the public uses the [Term submission form](https://forms.gle/rj3kWuvAtMJAYRWe8) to suggest a term 8 | - A Google Doc is created with details of the submission. 9 | - Contributors are notified and the Term is recorded in the Work Plan [Terms sheet](https://docs.google.com/spreadsheets/d/1rf4HbPA7nTyrpGByioyKvdJIfZCbBLSEI67_Nf9M6dA/edit?gid=0#gid=0). 10 | - Contributors review and make comments on the submission, in line with the [Language evaluation principles and framework](/handbook/evaluation-framework/). 11 | - After 3 to 5 (or more) reviews are received and there is a consensus on the next action to take, the term is either published or archived. 12 | 13 | ## Tasks 14 | 15 | In the Work plan spreadsheet, we maintain a list of [voluntary tasks](https://docs.google.com/spreadsheets/d/1rf4HbPA7nTyrpGByioyKvdJIfZCbBLSEI67_Nf9M6dA/edit?gid=1508334315#gid=1508334315) that can be carried out by any member of the contributors. These tasks can be any thing from a term review, GitHub issues triage, updates to the website or any other necessary task. Contributors can also add tasks they think would be beneficial to the initiative and any other contributor with bandwidth can take it on. 16 | 17 | The Tasks sheet is central to our activities, its where contributors see where they can contribute. Do you want to contribute? Join as a [contributor](https://forms.gle/wkaqTmhvSwgPn69t7) today. 18 | 19 | ## Communication 20 | 21 | Our Slack workspace is where collaboration happens, contributors or members of the community can collaborate or reach out to ask questions. If you are not in the Slack workspace yet, get an invite using [this link](https://communityinviter.com/apps/inclusive-naming/invite). 22 | 23 | ## GitHub 24 | 25 | GitHub Issues of our [org](https://github.com/inclusivenaming/org/issues) and [website](https://github.com/inclusivenaming/website/issues) have always been and are still where the community collaborates. They are regularly monitored and triaged. Issues requiring action, are logged in WorkPlan Tasks for a member of the contributors to work on and to ensure transparency. 26 | 27 | ## Why Google Sheet? 28 | 29 | In the past, we have had challenges onboarding community members who are new to GitHub or Open Source in general and it usually ends up in losing them. Google Sheet and Docs however have a low barrier of entry, allowing almost anyone with a gmail or Google account to start contributing immediately. 30 | 31 | ## Monthly Contributor Sync 32 | 33 | Every last Thursday of the Month, contributors meet at 18:00 UTC (6PM), to discuss reviews and sync on other activities. Any Contributor can join and discuss any agenda they find important. The calls are recorded to Zoom cloud and uploaded to Google drive for review of members who are unable to join. Its also important to document discussions held and the action items identified. 34 | -------------------------------------------------------------------------------- /content/media-mentions.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Media Mentions" 3 | --- 4 | 5 | {{< media-mentions >}} -------------------------------------------------------------------------------- /content/organizations.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supporting organizations" 3 | --- 4 | -------------------------------------------------------------------------------- /content/outreach.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Approaching Projects" 3 | --- 4 | 5 | ## Approaching Projects with Proposed Changes 6 | 7 | Once you start paying attention to inclusive language on your own 8 | projects, you'll start noticing issues in other projects, and you might 9 | want to do something about it. 10 | 11 | Unfortunately, if you rush in with a patch, this won't always be 12 | positively received. Some will take it as a personal attack, while 13 | others will see the changes as silly, unnecessary, or even actively 14 | harmful. That first interaction will set the tone for all future 15 | language-related discussions, so it should not be rushed or tactless. 16 | 17 | Here's some things to think about before you make that first contact. 18 | 19 | ### Remember whose side you’re on 20 | 21 | The project is not your enemy to be defeated. Rather, they are 22 | colleagues who you can help communicate better. We are in this together, 23 | to improve the experience for users and developers. 24 | 25 | In almost every case, language decisions that you are trying to change 26 | were made without intent. Avoid treating their language choices like offenses 27 | or attacks. Rather, they are past, innocent mistakes that you want to help 28 | them rectify, for the benefit of their users. 29 | 30 | Rushing in with an attitude that the project has done a bad thing, and 31 | you're there to fix it, is almost guaranteed to put everyone on the 32 | defensive, hurting your chance of success. 33 | 34 | ### Do your homework 35 | 36 | Open source projects are about conversations and collaboration. Take 37 | some time to learn something about the culture, and acceptable norms, 38 | before jumping into the conversation. 39 | 40 | Read the mailing lists. See what discussions have already happened around the 41 | topic. If you bring up the topic, and there has already been a divisive 42 | discussion around it, you will undermine your own message. 43 | 44 | See what the contribution process is. Drive-by patches from a random stranger 45 | might not be well received. Finding an ally within the community is 46 | often a less divisive approach. 47 | 48 | Whatever you do, do NOT just show up with a patch without looking around first. 49 | Patches from unengaged community members might be well-received, but in this 50 | particular case may be seen as criticism, and you may harm not only your chances 51 | of constructive engagement, but also anyone else approaching with a similar goal. 52 | 53 | ### Be patient 54 | 55 | It took us years to get here. A few more weeks isn’t going to hurt anything. 56 | Rushing into things is a great way to miss the social/community cues, and make 57 | the wrong first impression. 58 | 59 | ### Focus on the positive aspects of language choices 60 | 61 | Rather than focusing on why the project's chosen words are bad, focus on 62 | how your recommendations improve clarity, remove unintended 63 | connotations, or communicate more clearly to non-native speakers. 64 | 65 | While a large part of this initiative is, of course, removing offensive 66 | or otherwise problematic phrasing, it's also about all of those things - 67 | carefully, intentionally, consciously selecting words and phrases that 68 | are the best possible ones to communicate the concepts. 69 | 70 | ### Tell success stories, giving credit appropriately 71 | 72 | If a project begins to move towards more inclusive language, you should 73 | celebrate this. Tell the story, and give all the credit to the project, 74 | rather than to yourself, for the changes. This isn't about you, it's 75 | about making software, and, by extension, the whole world, a more 76 | welcoming place. 77 | 78 | 79 | 80 | -------------------------------------------------------------------------------- /content/participate.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Participate" 3 | --- 4 | 5 | There are a number of ways you can participate in the INI community. 6 | 7 | ## Join as a Contributor 8 | 9 | Contributors are active volunteers who help to run the activities of the Initiative. 10 | 11 | #### Reviewers 12 | 13 | Reviewers are passionate about inclusivity and seek ways to contribute to inclusive language efforts. A reviewer commits a couple of hours a month to review new term submissions and share their perspectives towards the recommendation of the term. The workflow of a reviewer is as follows: 14 | 15 | - A reviewer is added to a dedicated mailing list where new terms and other communications are sent 16 | - A reviewer collaborates with other reviewers via issues, slack or Google Docs 17 | - Where a vote is required, a reviewer votes on the adoption of a recommendation. 18 | - A reviewer can also be a Maintainer 19 | 20 | 21 | #### Maintainers 22 | 23 | Maintainers are familiar with GitHub and have technical knowledge to contribute to the website projects. Maintainers' activities include the following: 24 | 25 | - Triage issues in the [website](https://github.com/inclusivenaming/website) and [org](https://github.com/inclusivenaming/org) projects, keeping them updated and ensuring they don't become stale 26 | - Create code changes or Pull requests to update the wordlist and website project 27 | - Collaborate with leads on tooling for the projects 28 | - Advise and provide support as available to the initiative. 29 | - Time commitment is 1-2 hours per week 30 | - A contributor can be a reviewer and a maintainer. 31 | 32 | 33 | You can sign up to be a contributor using our [Call for Participation](https://forms.gle/wkaqTmhvSwgPn69t7) form. 34 | 35 | ### General Community 36 | 37 | You can be a part of the general community, learning and sharing with other members: 38 | 39 | - **Join the mailing list:** [inclusivenaming@googlegroups.com](https://groups.google.com/g/inclusivenaming). Send an email to if you want to use a non-Google email address. 40 | - **[Join the slack](https://communityinviter.com/apps/inclusive-naming/invite)** 41 | - Join public meetings, the [meeting calendar](/calendar) is always up to date and you can get invitations to the meetings via the mailing list! 42 | - Follow us on Twitter: [@inclusivenaming](https://twitter.com/inclusivenaming) and [LinkedIn](https://www.linkedin.com/company/inclusive-naming/) 43 | 44 | 45 | #### View the project board and file issues 46 | 47 | The [Project Board](https://github.com/orgs/inclusivenaming/projects/1) is where we track the work being done for the Inclusive Naming Initiative. You can also file issues for work you'd like to see or open questions you have via the [inclusivenaming/org repository](https://github.com/inclusivenaming/org/issues). 48 | 49 | #### Make changes in your projects 50 | 51 | Use the resources we've compiled so far–the [Word replacement list](/word-lists/overview), [Implementation path](/language/implementation-path), and the [Language evaluation framework](/language/evaluation-framework)–and start making changes in your own projects! This is the most impactful way to get involved and help us achieve our goal as an initiative. 52 | 53 | #### Approach other projects 54 | 55 | Outreach to other projects, to encourage them to change their language, needs to be handled carefully, patiently, and 56 | compassionately. We've collected some [tips on approaching projects](/outreach) to increase your chances of success. -------------------------------------------------------------------------------- /content/related-projects.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Related projects" 3 | --- 4 | 5 | We're lucky to be working with some of the most innovative and caring organizations on the planet for this initiative. Here's a list of the initiatives our participants are working on! 6 | 7 | ## By IBM and Red Hat 8 | 9 | {{< button "https://github.com/conscious-lang/conscious-lang-docs" "Conscious language in your open source projects" >}} 10 | 11 | Conscious language in your open source projects is a guide created by IBM and Red Hat to remove problematic language from software that they contribute to and release. The repository contains documents about that process. 12 | 13 | This project currently uses their [FAQs](faqs.md). 14 | 15 | ## By IBM 16 | 17 | {{< button "https://github.com/IBM/IBMInclusiveITLanguage" "IBM Inclusive IT Language" >}} 18 | 19 | IBM's Inclusive IT Language team put together a list of alternative terms, FAQ and advice for projects looking to make this switch. 20 | 21 | Members of this IBM project participate in INI as project leads and contributors. 22 | 23 | ## By the IETF 24 | 25 | {{< button "https://github.com/ietf/terminology" "Inclusive terminology in IETF documents" >}} 26 | 27 | A list of alternative terms in technology published by the IETF standards group for use on an ongoing basis. We also recommend reading the [Terminology, Power and Oppressive Language](https://tools.ietf.org/html/draft-knodel-terminology) draft document for more research and background. 28 | 29 | ## By Linux Foundation Networking 30 | 31 | {{< button "https://wiki.lfnetworking.org/display/LN/Inclusive+Language+Initiative" "Inclusive language working group" >}} 32 | 33 | The LF Networking nonprofit started this working group to tackle language and inclusive naming issues in the networking space. The group meets twice a month currently. We also recommend joining their [mailing list](https://lists.lfnetworking.org/g/inclusive-lang-wg). 34 | -------------------------------------------------------------------------------- /content/sponsor.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Sponsor the Inclusive Naming Initiative" 3 | --- 4 | 5 | Support the Inclusive Naming Initiative’s mission to promote and facilitate replacing harmful and exclusionary language in information technology. All sponsors of the initiative are also corporate members of the Linux Foundation, and belong to a group called the Sponsors Forum, who are empowered to create proposals for submissions to the Steering committee. The steering committee plans and tracks goals in all of the initiative's workstreams. 6 | 7 | Each Sponsor can appoint a number of representatives to the Sponsors Forum, depending on the Sponsorship level. The number of representatives also equals the voting power of the sponsor on the Sponsors Forum. 8 | 9 | ## Sponsorship Levels 10 | 11 | | Sponsorship Level | No. of Representatives | Annual Fees | 12 | |-------------------|-------------------------------------|---------------| 13 | |Premier | 3 | $ 25,000 | 14 | |Champion | 2 | $ 15,000 | 15 | |Startup | 1 | $ 2,000 | 16 | |Associate | 1 | $ 0 | 17 | 18 | NB: Only pre-approved non-profits, open source projects, and government entities can be associate sponsors. 19 | 20 | {{< button "https://enrollment.lfx.linuxfoundation.org/?project=ini" "Get Started" >}} -------------------------------------------------------------------------------- /content/webinar/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Webinars 3 | --- 4 | 5 | Upcoming and past webinars hosted by the Inclusive Naming Initiative. -------------------------------------------------------------------------------- /content/webinar/building-equitable-digital-world.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Building a More Respectful and Equitable Digital World" 3 | slug: building-equitable-digital-world 4 | date: "2025-05-22" 5 | draft: false 6 | description: "Join us for a conversation on how language and culture intersect in shaping digital experiences." 7 | registration_link: "" 8 | utc_datetime: "2025-05-22T18:00:00Z" # Use format like "2024-08-15T14:00:00Z" 9 | 10 | # Manually add formatted time strings for display 11 | time_los_angeles: "May 22, 11:00 AM PDT" 12 | time_new_york: "May 22, 02:00 PM EDT" 13 | time_london: "May 22, 7:00 PM BST" 14 | time_amsterdam: "May 22, 8:00 PM CEST" 15 | time_mumbai: "May 22, 11:30 PM IST" 16 | time_sydney: "May 23, 4:00 AM AEST" 17 | 18 | recording_link: "https://youtu.be/jzg4k0f7zzo" # Link to video recording if available 19 | 20 | presenters: ["Abubakar Siddiq Ango", "Aisha Shaibu-Salami"] # List of presenter names 21 | --- 22 | 23 | This webinar explores the role of inclusive naming and culturally sensitive communication in tech. Whether you're writing documentation or building products, this session offers fresh perspectives and ideas for creating more thoughtful and inclusive digital spaces. -------------------------------------------------------------------------------- /content/word-lists/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Overview" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | --- 10 | 11 | # Language recommendation lists 12 | 13 | The Inclusive Naming Initiative produces three tiers of language recommendation. These are compiled into lists for easy consumption by adopters. Terms are separated into lists based on the severity of the term in question as well as the level of review the terms have received. 14 | 15 | To add new terms to the lists, review the [Wordlist template](/word-lists/template/) page. 16 | 17 | 18 | ## [Tier 1: Replace Immediately](/word-lists/tier-1/) 19 | 20 | Tier 1 terms should be replaced whenever encountered. 21 | Terms included in this list have one or all of the following: 22 | 23 | - Strong social consensus within the software development community on replacements 24 | - Are identified by the Inclusive Naming Initiative as high-severity terms in need of immediate replacement 25 | - Terms where the impact of change or removal is low: for example, there is little entanglement in low-level systems or standardized language set by standards bodies 26 | - Have passed through all the review stages in Tiers 2 and 3 27 | 28 | ## [Tier 2: Strongly Consider Replacing](/word-lists/tier-2/) 29 | 30 | Terms in this list should be replaced whenever possible, barring major breaking changes. 31 | Terms included in this list have one or all of the following: 32 | 33 | - Are terms from Tier 3 that have undergone through external review by underrepresented minority groups and outside consultants 34 | - Terms which would otherwise be in Tier 1 but have dependencies on language set by standards bodies, or are deeply embedded in low-level systems and thus difficult to change 35 | 36 | ## [Tier 3: Recommendations to Replace](/word-lists/tier-3/) 37 | 38 | Terms in this list should be considered for replacement. 39 | Terms included in this list have one or all of the following: 40 | 41 | - Review by the Inclusive Naming Initiative, with particular attention paid to finding consensus among member companies and participants' companies for replacements 42 | - Research conducted by the Inclusive Naming Initiative on the etymology of the word and non-tech cultural connotations, per the [Language Evaluation Framework](https://inclusivenaming.org/language/evaluation-framework/) 43 | - A consensus-based replacement term or terms proposed by the Language Workstream and sent for approval and review to the larger Initiative. 44 | 45 | ## [No-Change](/word-lists/no-change/) 46 | 47 | This word list captures terms the Inclusive Naming Initiative and its partner organizations evaluated but did not recommend any changes for. 48 | 49 | 50 | ## JSON Formatted list 51 | 52 | The complete wordlist can be accessed in a single [JSON file](/word-lists/index.json), formatted as follows: 53 | 54 | ```json 55 | { 56 | "data" : 57 | [ 58 | { 59 | "term": "abort", 60 | "tier" : "1", 61 | "recommendation": "Replace when possible.", 62 | "recommended_replacements": ["User-Initiated Termination","Force quit","Cancel","System-Initiated Termination","Fail","Close (app, program, connection)","End","Halt","Hard stop","Stop (something you triggered)"], 63 | "term_page" : "http://inclusivenaming.org/word-lists/tier-1/abort/index.html" 64 | } 65 | ] 66 | } 67 | ``` 68 | 69 | -------------------------------------------------------------------------------- /content/word-lists/no-change/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "No Change Recommended" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | --- 10 | 11 | This word list captures terms the Inclusive Naming Initiative and its partner organizations evaluated but did not recommend any changes for. 12 | 13 | -------------------------------------------------------------------------------- /content/word-lists/no-change/blackbox.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Blackbox" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "blackbox" 12 | related_terms: 13 | - whitebox 14 | definition: "N/A" 15 | use_context: "An abstraction of a device or system in which only its externally visible behavior is considered and not its implementation or inner workings." 16 | recommendation: "No change recommended. This term may be used without restriction. Blackbox refers to opacity, such as details that aren't visible or are not the focus. This term is not based on a good/bad binary where white is represented as good or black is represented as bad and so does not promote racial bias." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group 27 | 28 | --- 29 | -------------------------------------------------------------------------------- /content/word-lists/no-change/blackout.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Blackout" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "blackout" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "A period of darkness, such as between acts in a play or during an electrical outage. Metaphorically, a period during which a service is unavailable." 16 | recommendation: "No change recommended. This term may be used without restriction. This term is not based on a good/bad binary where white is represented as good or black is represented as bad and so does not promote racial bias." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/disable.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Disable" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "disable" 12 | related_terms: 13 | - disabled 14 | definition: "N/A" 15 | use_context: "A feature that is deactivated or made unavailable." 16 | recommendation: "Do not change. The terms 'disable' and 'disabled' are valid in the context of technology, such as disabling an application or a network component. In the context of talking about disabled people, however, follow the guidance around it from the AP Style Guide, the [UK Government](https://www.gov.uk/government/publications/inclusive-communication/inclusive-language-words-to-use-and-avoid-when-writing-about-disability), the [National Center for Disability and Journalism](https://ncdj.org/style-guide/), or other sources. In most cases, the recommendation is to use the word 'disabled' to refer to disabled people rather than alternate terms. The [National Center for Disability and Journalism](https://ncdj.org/style-guide/) recommends to specify the disability where relevant, instead of grouping all people under the general term." 17 | recommended_replacements: 18 | - Deactivate/activate 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | N/A 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/fair-hiring-practice.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Fair Hiring Practise" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "fair hiring practice" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "N/A" 16 | recommendation: "No change recommended. This term is not biased because it's easy to distinguish 'fair' in the sense of unbiased from 'fair' in the sense of a light-skinned person in context." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/fellow.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Fellow" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "fellow" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "N/A" 16 | recommendation: "No change recommended. Fellow refers to the most senior rank or title one can achieve on a technical career in certain companies or a member of a learned or professional society, or a person who has been awarded a grant for studies, typically in the field of scientific research, or a person who has earned a fellowship. A Fellow can be of any gender. This term does not promote gender bias." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | N/A 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/master-inventor.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Master inventor" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "master inventor" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "N/A" 16 | recommendation: "No change recommended. This term does not fall under the criteria for replacing the term 'master'. It refers to a level of skill rather than a dominant/subordinate relationship." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/mastermind.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Mastermind" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "mastermind" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "N/A" 16 | recommendation: "No change recommended. This term does not fall under the criteria for replacing the term 'master'. It refers to a level of skill rather than a dominant/subordinate relationship." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/parent-child.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Parent Child" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "parent child" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "Used metaphorically to represent a dependent relationship, such as between a superior and dependent node." 16 | recommendation: "No change recommended. Although the relationship of parent and child is one of dependency, it is appropriate. Parents do have legal rights over children until a certain age, so it is a natural dependency relationship. Children falling victim to adult power is neither the main nor the intended result of this relationship, so this term does not typically represent an abuse of power." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/red-team.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Red Team" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "red team" 12 | related_terms: 13 | - None 14 | definition: "N/A" 15 | use_context: "Used in the military and security, a red team plays an attacker in a simulated attack while a blue team plays the defender." 16 | recommendation: "No change recommended. This use of 'red' does not refer to Indigenous people and does not reinforce a negative stereotype." 17 | recommended_replacements: 18 | - None 19 | unsuitable_replacements: 20 | - None 21 | rationale: | 22 | N/A 23 | status: | 24 | N/A 25 | supporting_content: | 26 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 27 | 28 | --- -------------------------------------------------------------------------------- /content/word-lists/no-change/whitebox.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Whitebox" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "whitebox" 12 | related_terms: 13 | - blackbox 14 | definition: | 15 | From [Wikipedia](https://en.wikipedia.org/wiki/White-box_testing): 16 | 17 | > White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of software testing that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing). 18 | use_context: "N/A" 19 | recommendation: "No change recommended. This term may be used without restriction." 20 | recommended_replacements: 21 | - None 22 | unsuitable_replacements: 23 | - None 24 | rationale: | 25 | White box refers to transparency, i.e., internal details are visible to the tester. This term is not based on a good/bad binary where white is represented as good or black is represented as bad and so does not promote racial bias. 26 | status: | 27 | N/A 28 | 29 | --- 30 | -------------------------------------------------------------------------------- /content/word-lists/no-change/whitelabel.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "White-label" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 0 11 | term: "white-label" 12 | related_terms: 13 | - white-label product 14 | - white-labeling 15 | definition: | 16 | From [Wikipedia](https://en.wikipedia.org/wiki/White-label_product): 17 | 18 | > A white-label product is a product or service produced by one company (the producer) that other companies (the marketers) rebrand to make it appear as if they had made it. The name derives from the image of a white label on the packaging that can be filled in with the marketer's trade dress. White label products are sold by retailers with their own trademark but the products themselves are manufactured by a third party. 19 | use_context: "N/A" 20 | recommendation: "No change recommended. This term may be used without restriction." 21 | recommended_replacements: 22 | - None 23 | unsuitable_replacements: 24 | - None 25 | rationale: | 26 | In this context, white refers to the most common background color of package paper. A white-label product lacks the printing, hence is fully white. This term is not based on a good/bad binary where white is represented as good or black is represented as bad and so does not promote racial bias. 27 | 28 | --- 29 | -------------------------------------------------------------------------------- /content/word-lists/template.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "WordList Template" 3 | ignore: true 4 | --- 5 | 6 | The Hugo software used to build this website uses Frontmatter of each page to determine how to process each page. The Wordlist section of this website uses the frontmatter to generate the pages for each Wordlist term and the JSON file containing all of them. To ensure consistency, the template below has been created. It is based on YAML. 7 | 8 | We you are creating a Pull Request for a new term, copy the template from the first `---` to the last one, make sure to include both `---`. 9 | 10 | **You can change the values of every field in the front matter, where necessary, except `type, layout and outputs`. These are used by Hugo to process the pages** 11 | 12 | 13 | ``` 14 | --- 15 | 16 | ############################ 17 | ### DO NOT CHANGE THESE VALUES ### 18 | type: wordlist 19 | layout: wordlist 20 | outputs: 21 | - html 22 | - json 23 | ############################ 24 | 25 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 26 | ## DO NOT CHANGE THE FIELD NAMES ## 27 | 28 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 29 | 30 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 31 | 32 | title: "Test1" 33 | 34 | tier: 1 35 | term: "test1" 36 | related_terms: 37 | - None 38 | definition: "N/A" 39 | use_context: "N/A" 40 | recommendation: "N/A" 41 | 42 | recommended_replacements: 43 | - None 44 | 45 | 46 | unsuitable_replacements: 47 | - None 48 | 49 | rationale: | 50 | N/A 51 | status: | 52 | N/A 53 | supporting_content: | 54 | N/A 55 | 56 | --- 57 | ``` 58 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/_cripple.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Cripple" 21 | 22 | tier: 1 23 | term: "cripple" 24 | related_terms: 25 | - crippled 26 | - crippleware 27 | definition: "N/A" 28 | use_context: "N/A" 29 | recommendation: "Adopt immediately." 30 | 31 | recommended_replacements: 32 | - Impacted 33 | - Degraded 34 | - Restricted 35 | - Immobilized 36 | 37 | unsuitable_replacements: 38 | - None 39 | 40 | rationale: | 41 | The terms cripple, crippled, and crippleware are sometimes used in writing about software or computer systems. These terms are rarely, if ever, used in software itself. These terms are used to indicate the following: 42 | 43 | - To limit functionality in software or to degrade performance of a system 44 | - An organization that is impacted, such as by a security breach` 45 | 46 | The term is ableist, that is, a pejorative term for people with physical disabilities. 47 | 48 | Example usage of recommended replacements: 49 | 50 | - Crippled performance speed 51 | - Impacted 52 | - Degraded 53 | - Crippled functionality 54 | - Restricted 55 | - Security issues cripple an organization 56 | - Impacted 57 | - Immobilized 58 | - Crippleware 59 | - Software with restricted functionality 60 | status: | 61 | N/A 62 | supporting_content: | 63 | N/A 64 | 65 | --- 66 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Tier 1: Replace Immediately" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | --- 10 | 11 | Tier 1 terms should be replaced whenever encountered. 12 | Terms included in this list have one or all of the following: 13 | 14 | - Strong social consensus within the software development community on replacements 15 | - Are identified by the Inclusive Naming Initiative as high-severity terms in need of immediate replacement 16 | - Terms where the impact of change or removal is low: for example, there is little entanglement in low-level systems or standardized language set by standards bodies 17 | - Have passed through all the review stages in Tiers 2 and 3 18 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/_master-slave.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Master-Slave" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | 11 | tier: 1 12 | term: "master-slave" 13 | related_terms: 14 | - N/A 15 | definition: "The “master/slave” metaphor in computing refers to a system with a single store of record and a set of replicas which maintain copies of the original data." 16 | use_context: "N/A" 17 | recommendation: "Adopt immediately" 18 | recommended_replacements: 19 | - Control plane/control plane node 20 | - Controller/doer 21 | - Primary/replica 22 | - Primary/secondary 23 | - Leader/follower 24 | - Parent/child 25 | unsuitable_replacements: 26 | - N/A 27 | rationale: | 28 | As the IETF puts it, “Master-slave is an oppressive metaphor that will and should never become fully detached from history.” The word’s origins and historicial use reveal use that is at best chauvinistic and racist, and in almost all cases connotative of ownership. While there is some small ambiguity about the term master, the term slave is unambiguously about the ownership and subjugation of another person, and has been since its inception. 29 | 30 | The terms master/slave are harmful to Black and people of color contributors and employees. Slavery is a tradition barely 3 generations abolished – there are grandparents alive today who were actual, non-metaphorical slaves. Segregation and Apartheid are even more recent. In accordance with most open source codes of conduct and company handbooks, the mandate of all people in a project is to create a welcoming space, regardless of the level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Master/slave are not welcoming words. 31 | 32 | 33 | status: | 34 | Nill 35 | supporting_content: | 36 | * [Broken Metaphor: The Master-Slave Analogy in Technical Literature](https://www.researchgate.net/publication/236752849_Broken_Metaphor_The_Master-Slave_Analogy_in_Technical_Literature) 37 | * [IETF Network Working Group: Terminology, Power and Oppressive Language](https://tools.ietf.org/id/draft-knodel-terminology-00.html) 38 | * [django/django PR #2692](https://github.com/django/django/pull/2692) 39 | * [Python issue #34605](https://bugs.python.org/issue34605) 40 | * [Drupal issue](https://www.drupal.org/node/2275877) 41 | * [COUCHDB-2248](https://issues.apache.org/jira/browse/COUCHDB-2248) 42 | 43 | --- 44 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/_master.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Master" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | tier: 1 11 | term: "master" 12 | related_terms: 13 | - N/A 14 | definition: "In computing, A “master” often refers to the original or main version of an entity." 15 | use_context: "N/A" 16 | recommendation: "Adopt immediately." 17 | recommended_replacements: 18 | - main 19 | - original 20 | - source 21 | - control plane 22 | unsuitable_replacements: 23 | - N/A 24 | rationale: | 25 | While master in and of itself is potentially neutral, the propensity in which it is associated with the term slave in computing makes master on its own guilty by association. Though it is used as a standalone, it's impossible to remove the association with command and control entirely, and thus we recommend moving away from even singular use. 26 | status: | 27 | Nill 28 | supporting_content: | 29 | * [github/renaming](https://github.com/github/renaming) 30 | 31 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-1/abort.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | title: "Abort" 17 | tier: 1 18 | term: "abort" 19 | related_terms: 20 | - abortion 21 | definition: "None" 22 | use_context: "'Abort' usually refers to the abnormal, abrupt termination of a process, either by the system itself or by a user." 23 | recommendation: "Replace when possible." 24 | recommended_replacements: 25 | - User-Initiated Termination 26 | - Force quit 27 | - Cancel 28 | - System-Initiated Termination 29 | - Fail 30 | - Close (app, program, connection) 31 | - End 32 | - Halt 33 | - Hard stop 34 | - Stop (something you triggered) 35 | unsuitable_replacements: 36 | - Kill (as in Linux systems) 37 | rationale: | 38 | The term “abort” frequently appeared in Inclusive Language 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. 39 | 40 | INI recommends replacing “abort” wherever possible. In accordance with the INI’s language framework, the term does not necessarily constitute a first-order concern. However, because it is such a charged term outside of computing, “abort” fails to provide a clear 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 “abort.” 41 | 42 | Although the INI debated whether the word “abort” itself or the procedure commonly associated with it (“abortion”) caused 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 “abort” 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. 43 | 44 | All this being said, the INI does not advocate for a blanket replacement of the term. “Abort” appears in many standards 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. 45 | 46 | Some organizations have noted that using “abort” in contexts 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’s right to control their body. The judgment 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, “abort” may become a less contentious term; at that juncture, the appropriateness of the term may be revisited. 47 | 48 | status: | 49 | 50 | Version: 0.1 51 | 52 | Created: August 2021 53 | 54 | Review status: 55 | - [x] Reviewed by Inclusive Naming Initiative 56 | - [x] Approved by Inclusive Naming Initiative Language Workstream 57 | - [ ] Reviewed by URM organizations and working groups 58 | - [ ] Reviewed by professional diversity consultants 59 | supporting_content: | 60 | None 61 | 62 | --- 63 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/blackhat-whitehat.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Blackhat - WhiteHat" 21 | 22 | tier: 1 23 | term: "blackhat-whitehat" 24 | related_terms: 25 | - None 26 | definition: "N/A" 27 | use_context: "Ethical, or “white hat” hacking, is authorized by a company and is done by employees or consultants with the intention of identifying vulnerabilities in a system so they can be fixed. Unethical, or “black hat” hacking, is criminal activity done by unauthorized agents with the intention of exploiting vulnerabilities in a system." 28 | recommendation: "Replace immediately." 29 | 30 | recommended_replacements: 31 | - ethical hacker 32 | - unethical hacker, attacker 33 | 34 | 35 | unsuitable_replacements: 36 | - None 37 | 38 | rationale: | 39 | The terms *white hat* and *black hat* promote racial bias because black is used to indicate malevolence while white indicates ethical, positive behavior. 40 | 41 | status: | 42 | N/A 43 | supporting_content: | 44 | *Adapted from a recommendation originally published by the IBM Inclusive IT Language Initiative Words Matter working group.* 45 | 46 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-1/grandfathered.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Grandfathered" 21 | 22 | tier: 1 23 | term: "grandfathered" 24 | related_terms: 25 | - grandfathered in 26 | - grandfathering 27 | - grandfather clause 28 | - grandfather policy 29 | definition: "an activity, person, group, etc. that is exempt from a new law or policy, often for reasons requireing understanding of historic context" 30 | use_context: "N/A" 31 | recommendation: "Adopt immediately." 32 | 33 | recommended_replacements: 34 | - exempted 35 | - excused 36 | - preapproved 37 | - preauthorized 38 | - legacy 39 | 40 | unsuitable_replacements: 41 | - None 42 | 43 | rationale: | 44 | The terms grandfathered and grandfather clause are sometimes used to indicate the following: 45 | 46 | - To allow compliance exemption from new or updated policies / terms. 47 | - To allow a legacy software system to exist outside of current best practices. 48 | 49 | These terms have roots in 19th century racially motivated voter disenfranchisement efforts. 50 | 51 | status: | 52 | N/A 53 | supporting_content: | 54 | - [The Racial History Of The 'Grandfather Clause'](https://www.npr.org/sections/codeswitch/2013/10/21/239081586/the-racial-history-of-the-grandfather-clause) 55 | 56 | --- 57 | -------------------------------------------------------------------------------- /content/word-lists/tier-1/tribe.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Tribe" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | 11 | tier: 1 12 | term: "tribe" 13 | related_terms: 14 | - N/A 15 | definition: "N/A" 16 | use_context: "Used to describe teams within an organization." 17 | recommendation: "Use with caution. Do not use to refer to a group formed to accomplish a task." 18 | recommended_replacements: 19 | - Squad of squads 20 | - Team 21 | unsuitable_replacements: 22 | - None 23 | rationale: | 24 | "Tribe" is a term that can be associated with colonialism or can be considered cultural appropriation. The word has a history of being used to describe division along ethnic or racial lines. As such, choose other words to describe groups of people. 25 | status: | 26 | N/A 27 | supporting_content: | 28 | **Recommendation from the IBM Inclusive IT Language Initiative Words Matter working group** 29 | 30 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-1/whitelist.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Whitelist" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | 11 | tier: 1 12 | term: "whitelist" 13 | related_terms: 14 | - blacklist 15 | definition: "Lists which permit or deny a set of nouns, or select enabled features." 16 | use_context: "N/A" 17 | recommendation: "Adopt immediately" 18 | recommended_replacements: 19 | - allowedNouns/deniedNouns (or other verbs) 20 | - allowlist/denylist 21 | unsuitable_replacements: 22 | - N/A 23 | rationale: | 24 | The underlying assumption of the whitelist/blacklist metaphor is that white = good and black = bad. Because colors in and of themselves have no predetermined meaning, any meaning we assign to them is cultural: for example, the color red in many Southeast Asian countries is lucky, and is often associated with events like marriages, whereas the color white carries the same connotations in many European countries. 25 | 26 | From a technical communication perspective, using whitelist/blacklist as a naming convention applies metaphor (and, in turn, unintended meaning) when it isn’t needed. A suitable verb or adjective enhances understanding by replacing the metaphor with a direct description. 27 | 28 | In English, "whitelist" and "blacklist" can be used as either verbs or nouns. As a verb, commonly used words such as "allow" or "deny" can be used directly. Depending on the context, other verbs such as "skip", "ignore", "block", "waive", "disable" can be used instead. As a noun, words such as "allowlist" and "denylist" are in use and are more descriptive than whitelist/blacklist, but they may be difficult to translate to other human languages. Consider prefixed forms instead, such as "allowedRecipients" as a replacement for "recipientWhitelist"; in descriptive text (as opposed to code) you may want to prepend "list of", as in "list of allowed recipients". 29 | 30 | 31 | status: | 32 | N/A 33 | supporting_content: | 34 | (1) [“Blacklists” and “whitelists”: a salutary warning concerning the prevalence of racist language in discussions of predatory publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) 35 | (2) [IETF Network Working Group: Terminology, Power and Oppressive Language](https://tools.ietf.org/html/draft-knodel-terminology) 36 | (3) [Android PR](https://9to5google.com/wp-content/uploads/sites/4/2020/06/android-aosp-allowlist-explanation.png) 37 | (4) [cURL PR](https://github.com/curl/curl/pull/5546) 38 | 39 | --- 40 | -------------------------------------------------------------------------------- /content/word-lists/tier-2/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Tier 2: Strongly Consider Replacing" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | --- 10 | 11 | Terms in this list should be replaced whenever possible, barring major breaking changes. 12 | Terms included in this list have one or all of the following: 13 | 14 | - Are terms from Tier 3 that have undergone through external review by underrepresented minority groups and outside consultants 15 | - Terms which would otherwise be in Tier 1 but have dependencies on language set by standards bodies, or are deeply embedded in low-level systems and thus difficult to change 16 | -------------------------------------------------------------------------------- /content/word-lists/tier-2/sanity-check.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Sanity-check" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | 11 | tier: 2 12 | term: "sanity-check" 13 | related_terms: 14 | - sanity-test 15 | definition: "*Recommendation donated from the IBM Inclusive IT Language Initiative Words Matter working group*" 16 | use_context: "N/A" 17 | recommendation: "Replace" 18 | recommended_replacements: 19 | - confidence check 20 | - coherence check 21 | - test 22 | - verification 23 | unsuitable_replacements: 24 | - N/A 25 | rationale: | 26 | This term might be derogatory to neurodiverse people. Jargon, such as "sanity test", is difficult to translate and is difficult to understand by readers whose first language is not English. 27 | 28 | Note: The original recommendation via IBM’s Words Matter group included different recommendations, but INI liked [Twitter’s recommendations][twitter-recs] of "confidence check" and "coherence check" and have opted to use them instead. 29 | status: | 30 | N/A 31 | supporting_content: | 32 | [twitter-recs] (https://www.mediaite.com/news/twitter-bans-sanity-checks-company-announces-plan-to-make-code-more-politically-correct/) 33 | 34 | --- 35 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Tier 3: Recommendations to Replace" 3 | 4 | type: wordlist 5 | layout: wordlist 6 | outputs: 7 | - html 8 | - json 9 | - custom 10 | --- 11 | 12 | Terms in this list should be considered for replacement. 13 | Terms included in this list have one or all of the following: 14 | 15 | - Review by the Inclusive Naming Initiative, with particular attention paid to finding consensus among member companies and participants' companies for replacements 16 | - Research conducted by the Inclusive Naming Initiative on the etymology of the word and non-tech cultural connotations, per the [Language Evaluation Framework](https://inclusivenaming.org/language/evaluation-framework/) 17 | - A consensus-based replacement term or terms proposed by the Language Workstream and sent for approval and review to the larger Initiative 18 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/blast-radius.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Blast radius" 21 | 22 | tier: 3 23 | term: "blast-radius" 24 | related_terms: 25 | - None 26 | definition: "Blast radius refers to the extent to which a particular vulnerability affects a software project." 27 | use_context: "N/A" 28 | recommendation: "Recommended to replace." 29 | 30 | recommended_replacements: 31 | - extent 32 | - affected components 33 | 34 | 35 | unsuitable_replacements: 36 | - None 37 | 38 | rationale: | 39 | The term *blast radius* comes from warcraft. It refers to the extent of damage caused by an explosion. Many people, including but not limited to those who have served in the military or lived in war zones, could experience triggered reactions or otherwise take offense. 40 | 41 | Additionally, *blast radius* is not universally known within the IT community, and there is a high risk of it being mistranslated. Both of the recommended replacement terms are clear and unambiguous. 42 | status: | 43 | N/A 44 | supporting_content: | 45 | N/A 46 | 47 | --- 48 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/end-of-life.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "End of Life" 21 | 22 | tier: 3 23 | term: "end-of-life" 24 | related_terms: 25 | - None 26 | use_context: "In the IT world, 'End of Life' (EOL) refers to the point when a product, such as software or hardware, is no longer supported by the manufacturer." 27 | 28 | definition: "N/A" 29 | 30 | recommendation: "Recommended to replace." 31 | 32 | recommended_replacements: 33 | - "End of Support" 34 | - "Device/Application Retirement" 35 | - "End of Warranty" 36 | 37 | unsuitable_replacements: 38 | - N/A 39 | 40 | rationale: | 41 | In healthcare, "End of Life" refers to the care provided to individuals who are in the final stages of a terminal illness. This care focuses on comfort, dignity, and quality of life. People who may have loved ones going through End of Life support, may be triggered by the use of the term. 42 | 43 | status: | 44 | N/A 45 | 46 | supporting_content: | 47 | N/A 48 | 49 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-3/evangelist.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "evangelist" 21 | 22 | tier: 3 23 | term: "evangelist" 24 | related_terms: 25 | - None 26 | use_context: "N/A" 27 | definition: "An evangelist is someone who advocates for a particular technology, process, or individual product." 28 | 29 | recommendation: "Recommended to replace." 30 | 31 | recommended_replacements: 32 | - "influencer" 33 | - "advocate" 34 | - "ambassador" 35 | - "proponent" 36 | 37 | unsuitable_replacements: 38 | - "preacher" 39 | 40 | rationale: | 41 | *Evangelist* has a strongly religious connotation and might therefore cause offense. It is the English rendering of the Greek word *euangelistas*, which in the Christian New Testament refers to someone who spreads the faith. 42 | 43 | It is inappropriate to apply the word to someone who prefers not to be associated with the Christian faith. Conversely, the term can also cause offense to those who object to its being used in a secular (non-religious) context. 44 | 45 | status: | 46 | N/A 47 | 48 | supporting_content: | 49 | N/A 50 | 51 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-3/hallucinate.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Hallucinate" 21 | 22 | tier: 3 23 | term: "hallucinate" 24 | related_terms: 25 | - None 26 | use_context: "N/A" 27 | definition: "An artificial intelligence (AI) application generates information that has no basis in fact." 28 | 29 | recommendation: "Recommended to replace when possible." 30 | 31 | recommended_replacements: 32 | - "inaccurate information (noun)" 33 | - "*create* or *generate* inaccurate information (verb)" 34 | 35 | 36 | unsuitable_replacements: 37 | - None 38 | 39 | rationale: | 40 | Hallucinations -- perceptions that are not based in reality -- are often associated with mental illness or drug use. Using the term in a technology context, in either its noun or verb form, can be seen as insensitive to people who experience those conditions. 41 | 42 | status: | 43 | N/A 44 | supporting_content: | 45 | N/A 46 | 47 | --- -------------------------------------------------------------------------------- /content/word-lists/tier-3/man-hour.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Man Hour" 21 | 22 | tier: 3 23 | term: "man-hour" 24 | related_terms: 25 | - None 26 | definition: "A man-hour is a unit that describes the average amount of work done in an hour." 27 | use_context: "N/A" 28 | recommendation: "Recommended to replace." 29 | 30 | recommended_replacements: 31 | - work-hour 32 | - person-hour 33 | - staff-hour 34 | - hour 35 | 36 | 37 | unsuitable_replacements: 38 | - woman-hour 39 | 40 | rationale: | 41 | Gendered language that can perpetuate bias and stereotypes. 42 | Can cause one to wonder if the relation between time and work done differs by gender. 43 | status: | 44 | N/A 45 | supporting_content: | 46 | N/A 47 | 48 | --- 49 | 50 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/man-in-middle.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ############################ 4 | ### DO NOT CHANGE THESE VALUES ### 5 | type: wordlist 6 | layout: wordlist 7 | outputs: 8 | - html 9 | - json 10 | - custom 11 | ############################ 12 | 13 | ## YOU CAN CHANGE THE VALUES OF THE FIELDS BELOW ## 14 | ## DO NOT CHANGE THE FIELD NAMES ## 15 | 16 | ## Related terms, Recommended Replacements & Unsuitable Replacements fields expect a buletted list using - symbol ## 17 | 18 | ## Rationale, Status & Supporting Content allows multiline content, you can also use markdown format. Please make use the | symbol is not deleted. 19 | 20 | title: "Man in the Middle attack" 21 | 22 | tier: 3 23 | term: "man-in-the-middle" 24 | related_terms: 25 | - None 26 | definition: "N/A" 27 | use_context: "N/A" 28 | recommendation: "Consider replacement" 29 | 30 | recommended_replacements: 31 | - Adversary-in-the-middle attack 32 | - Interceptor attack 33 | - Intermediary attack 34 | 35 | 36 | unsuitable_replacements: 37 | - None 38 | 39 | rationale: | 40 | When an attacker secretly intercepts and relays communications between two systems or people who believe that they are communicating directly with each other. Gendered language that can perpetuate bias and stereotypes. Implies that women do not have the skills to perpetrate this type of hacking. 41 | status: | 42 | N/A 43 | supporting_content: | 44 | N/A 45 | 46 | --- 47 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/segregate.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Segregate" 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | 11 | tier: 3 12 | term: "segregate" 13 | related_terms: 14 | - All Derivatives 15 | - Segregation 16 | definition: "None" 17 | use_context: "Used when separating data, especially by use of policy." 18 | recommendation: "Replace" 19 | recommended_replacements: 20 | - Segment/segmentation 21 | - Separate/separation 22 | unsuitable_replacements: 23 | - Discriminate/discrimination 24 | rationale: | 25 | The word segregation carries strong context in regard to civil rights movements in the US and South Africa, segregation in the US South, and racist history. Though the word appears etymologically neutral at first, [Etymonline](https://www.etymonline.com/) notes that the term has strong moral contexts prior to US segregation, and after US segregation is almost exclusively associated with the segregation of Black people from White people, an extremely racist context. 26 | 27 | This meets one of the INI’s evaluation framework’s [first-order concerns](/language/evaluation-framework/#first-order-concerns): the term is loaded, problematic, or politically charged outside of technology contexts, even if the language is itself etymologically neutral. As such, we recommend replacing it to remove the distracting, racist, and negative connotations of the word. 28 | 29 | While the word is in use in security contexts and in GDPR and data protection contexts, it does not appear to be codified into any laws, policies, or other difficult to change or heavily embedded frameworks. Moreover, the replacement terms recommended—"segmentation” and “separation”—are both equally descriptive and in common use in technology, so we recommend replacing as you see the term. 30 | 31 | We acknowledge that switching from "segregation" to "segmentation" or "separation" loses a small amount of nuance: specifically, "segregation" implies "separation" based on a policy or human-defined ruleset. If this is an issue in the context in which you use the word, we recommend using descriptive words along with the replacement, such as “policy-based segmentation.” 32 | status: | 33 | N/A 34 | supporting_content: | 35 | N/A 36 | 37 | --- 38 | -------------------------------------------------------------------------------- /content/word-lists/tier-3/totem-pole.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | type: wordlist 4 | layout: wordlist 5 | outputs: 6 | - html 7 | - json 8 | - custom 9 | 10 | title: "Totem Pole" 11 | 12 | tier: 3 13 | term: "totem-pole" 14 | related_terms: 15 | - None 16 | use_context: "Often used in phrases such as *bottom of the totem pole* or *low man on the totem pole*." 17 | 18 | definition: "N/A" 19 | 20 | recommendation: "Recommended to replace." 21 | 22 | recommended_replacements: 23 | - "Do not use in phrases such as **bottom of the totem pole** or **low man on the totem pole**. Use more specific terms that are appropriate to the context in which this phrase may be referred." 24 | 25 | 26 | unsuitable_replacements: 27 | - N/A 28 | 29 | rationale: | 30 | A totem pole is a sacred object in Indigenous communities and the bottom of the totem pole has a specific symbolic meaning. Additionally, describing someone or something as *bottom* or *low man* implies that they are somehow inferior – which not only dishonors the symbolic meaning but is inaccurate. 31 | 32 | "Low man on the totem pole" is a good example here where there isn't a great alternative, because we're using generalized qualitative opinions about place in the hierarchy to infer capability or effectiveness. In this case, rather than identifying a replacement term, we need to encourage the user to utilize more specific language to get their point across. 33 | 34 | Some examples: 35 | - "I can't make a sale with this person because he's a low man on the totem pole" --> "I can't make a sale with this person because they cannot make buying decisions." 36 | 37 | - "The low man on the totem pole is the one who gets all the grunt work." --> "More junior team members are assigned more tedious, repetitive tasks." 38 | 39 | 40 | status: | 41 | N/A 42 | 43 | supporting_content: | 44 | N/A 45 | 46 | --- -------------------------------------------------------------------------------- /generateDocFormats.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | doindent() 4 | { 5 | # Do a small indent depending on how deep into the tree we are 6 | # Depending on your environment, you may need to use 7 | # echo " \c" instead of 8 | # echo -en " " 9 | j=0; 10 | while [ "$j" -lt "$1" ]; do 11 | #echo -en " " 12 | j=`expr $j + 1` 13 | done 14 | } 15 | 16 | traverse() 17 | { 18 | # Traverse a directory 19 | indent="$2" 20 | 21 | ls "$1" | while read i 22 | do 23 | doindent $2 24 | if [ -d "$1/$i" ]; then 25 | echo "Directory: $1/$i" 26 | # Calling this as a subshell means that when the called 27 | # function changes directory, it will not affect our 28 | # current working directory 29 | traverse "$1/$i" `expr $2 + 1` 30 | else 31 | if [ "$i" = "index.custom" ]; then 32 | echo "File: $1/$i" 33 | ./bin/pandoc -f html -t pdf --pdf-engine=context -s "$1/$i" -o "$1/inclusive-naming-word-lists-v1.0.pdf" 34 | ./bin/pandoc -f html -t html -s "$1/$i" -o "$1/inclusive-naming-word-lists-v1.0.html" 35 | ./bin/pandoc -f html -t odt -s "$1/$i" -o "$1/inclusive-naming-word-lists-v1.0.odt" 36 | fi 37 | fi 38 | done 39 | } 40 | 41 | if [ -z "$1" ]; then 42 | traverse . 0 43 | else 44 | traverse "$1" 0 45 | fi 46 | -------------------------------------------------------------------------------- /index.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/index.pdf -------------------------------------------------------------------------------- /layouts/_default/_markup/render-heading.html: -------------------------------------------------------------------------------- 1 | 2 | {{ .Text | safeHTML }} 3 | 4 | 5 | 6 | 7 | 8 | 9 | -------------------------------------------------------------------------------- /layouts/_default/_markup/render-link.html: -------------------------------------------------------------------------------- 1 | {{ $link := .Destination }} 2 | {{ $isRemote := strings.HasPrefix $link "http" }} 3 | {{- if not $isRemote -}} 4 | {{ $url := urls.Parse .Destination }} 5 | {{- if $url.Path -}} 6 | {{ $fragment := "" }} 7 | {{- with $url.Fragment }}{{ $fragment = printf "#%s" . }}{{ end -}} 8 | {{- if .Page.GetPage $url.Path }}{{ $link = printf "%s%s" (.Page.GetPage $url.Path).RelPermalink $fragment }}{{ end }}{{ end -}} 9 | {{- end -}} 10 | {{- .Text | safeHTML -}}{{ if $isRemote }} {{ end }} 11 | -------------------------------------------------------------------------------- /layouts/_default/baseof.html: -------------------------------------------------------------------------------- 1 | {{ $lang := site.LanguageCode }} 2 | 3 | 4 | 5 | 6 | {{ block "title" . }} 7 | {{ site.Title }} 8 | {{ end }} 9 | 10 | {{ partial "css.html" . }} 11 | {{ partial "favicon.html" . }} 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | {{ partial "navbar.html" . }} 20 | 21 |
22 |
23 | {{ block "main" . }} 24 | {{ end }} 25 |
26 |
27 | 28 | {{ partial "footer.html" . }} 29 | {{ partial "javascript.html" }} 30 | 31 | 32 | -------------------------------------------------------------------------------- /layouts/_default/list.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 | {{ partial "breadcrumb.html" . }} 6 |
7 | 8 |

{{ .Title }}

9 | 10 | {{ if .Content }} 11 |
12 | {{ .Content }} 13 |
14 | {{ end }} 15 | 16 |
17 | {{ range .Pages }} 18 |
19 |

20 | 21 | {{ .Title }} 22 | 23 |

24 | 25 | {{ if .Params.description }} 26 |

{{ .Params.description }}

27 | {{ end }} 28 | 29 | 30 | Read More 31 | 32 |
33 | {{ end }} 34 |
35 |
36 |
37 | {{ end }} -------------------------------------------------------------------------------- /layouts/_default/section.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 |

{{ .Title }}

6 | {{ with .Description }} 7 |
{{ . }}
8 | {{ end }} 9 |
10 | 11 |
12 | {{ .Content }} 13 |
14 | 15 | {{ $pages := .Pages }} 16 | {{ if $pages }} 17 |
18 | {{ range $pages }} 19 |
20 | 21 | {{ .Title }} 22 | 23 | {{ with .Description }} 24 |
{{ . }}
25 | {{ end }} 26 |
27 | {{ end }} 28 |
29 | {{ end }} 30 |
31 |
32 | {{ end }} 33 | -------------------------------------------------------------------------------- /layouts/_default/single.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 | {{ partial "breadcrumb.html" . }} 6 |
7 | 8 |
9 |

{{ .Title }}

10 | 11 | {{ if .Params.description }} 12 |

{{ .Params.description }}

13 | {{ end }} 14 | 15 |
16 | {{ .Content }} 17 |
18 |
19 |
20 |
21 | {{ end }} 22 | -------------------------------------------------------------------------------- /layouts/blog/list.html: -------------------------------------------------------------------------------- 1 | {{ define "title" }} 2 | {{ .Title }} 3 | {{ end }} 4 | 5 | {{ define "main" }} 6 |
7 |
8 |

{{ .Title }}

9 | 10 | {{ if .Content }} 11 |
12 | {{ .Content }} 13 |
14 | {{ end }} 15 | 16 |
17 | {{ range .Pages }} 18 |
19 |
20 |

21 | 22 | {{ .Title }} 23 | 24 |

25 | 26 |
27 | {{ if .Params.author }} 28 | {{ .Params.author }} 29 | {{ end }} 30 | {{ if .Date }} 31 | 32 | {{ end }} 33 |
34 | 35 |
36 |

{{ .Summary }}

37 |
38 | 39 |
40 | 41 | Continue reading 42 | 43 |
44 |
45 |
46 | {{ end }} 47 |
48 |
49 |
50 | {{ end }} 51 | -------------------------------------------------------------------------------- /layouts/blog/single.html: -------------------------------------------------------------------------------- 1 | {{ define "title" }} 2 | {{ .Title }} | The Longhorn blog 3 | {{ end }} 4 | 5 | {{ define "main" }} 6 |
7 |
8 |
9 | {{ partial "breadcrumb.html" . }} 10 |
11 | 12 |
13 | {{ if .Params.image }} 14 |
15 | {{ .Title }} 16 |
17 | {{ end }} 18 | 19 |
20 |

{{ .Title }}

21 | 22 |
23 | {{ if .Params.author }} 24 | 25 | {{ .Params.author }} 26 | 27 | {{ end }} 28 | 29 | 30 | {{ .Date.Format "January 2, 2006" }} 31 | 32 | 33 | {{ if .Params.categories }} 34 | 35 | 36 | {{ range $index, $category := .Params.categories }} 37 | {{ if gt $index 0 }}, {{ end }} 38 | {{ . }} 39 | {{ end }} 40 | 41 | {{ end }} 42 |
43 | 44 | {{ if .Params.description }} 45 |

{{ .Params.description }}

46 | {{ end }} 47 | 48 |
49 | {{ .Content }} 50 |
51 | 52 | {{ if .Params.tags }} 53 |
54 |

Tags:

55 |
56 | {{ range .Params.tags }} 57 | 58 | #{{ . }} 59 | 60 | {{ end }} 61 |
62 |
63 | {{ end }} 64 |
65 |
66 | 67 |
68 |

Related Posts

69 |
70 | {{ $related := .Site.RegularPages.Related . | first 2 }} 71 | {{ with $related }} 72 | {{ range . }} 73 |
74 | {{ if .Params.image }} 75 | 76 | {{ .Title }} 77 | 78 | {{ end }} 79 |
80 |

81 | {{ .Title }} 82 |

83 |

{{ .Params.description | default .Summary }}

84 | 85 | Read More 86 | 87 |
88 |
89 | {{ end }} 90 | {{ else }} 91 |

No related posts found.

92 | {{ end }} 93 |
94 |
95 |
96 |
97 | {{ end }} 98 | -------------------------------------------------------------------------------- /layouts/partials/blog/content.html: -------------------------------------------------------------------------------- 1 | {{ $posts := where site.RegularPages "Section" "blog" }} 2 |
3 |
4 |
5 |
6 |

{{ .Title }}

7 | 8 |
9 | {{ if .Params.author }} 10 | 11 | {{ .Params.author }} 12 | 13 | {{ end }} 14 | 15 | 16 | {{ .Date.Format "January 2, 2006" }} 17 | 18 | 19 | {{ if .Params.categories }} 20 | 21 | 22 | {{ range $index, $category := .Params.categories }} 23 | {{ if gt $index 0 }}, {{ end }} 24 | {{ . }} 25 | {{ end }} 26 | 27 | {{ end }} 28 |
29 | 30 | {{ if .Params.description }} 31 |

{{ .Params.description }}

32 | {{ end }} 33 | 34 | {{ .Content }} 35 | 36 | {{ if .Params.tags }} 37 |
38 |

Tags:

39 |
40 | {{ range .Params.tags }} 41 | 42 | #{{ . }} 43 | 44 | {{ end }} 45 |
46 |
47 | {{ end }} 48 |
49 | 50 | 51 | 52 | Back to blog 53 | 54 | 55 |
56 |
57 |
58 | -------------------------------------------------------------------------------- /layouts/partials/blog/hero.html: -------------------------------------------------------------------------------- 1 | {{ $isPost := ne .File.BaseFileName "_index" }} 2 |
3 |

4 | {{ .Title }} 5 |

6 | {{ if $isPost }} 7 | {{ $date := dateFormat "January 2, 2006" .Date }} 8 |

9 | {{ .Params.author }} | {{ $date }} 10 |

11 | {{ end }} 12 |
-------------------------------------------------------------------------------- /layouts/partials/blog/post-list.html: -------------------------------------------------------------------------------- 1 | {{ $posts := where site.RegularPages "Section" "blog" }} 2 |
3 |
4 | {{ range (.Paginate $posts).Pages }} 5 | {{ $date := dateFormat "January 2, 2006" .Date }} 6 |
7 | {{ with .Params.featured_image }} 8 | {{ $.Title }} 9 | {{ end }} 10 |
11 |

12 | {{ .Title }} 13 |

14 |

{{ $date }}

15 |
{{ .Summary }}...
16 | Read more 17 |
18 |
19 | {{ end }} 20 |
21 | 22 |
23 | {{ partial "pagination.html" . }} 24 |
25 |
26 | -------------------------------------------------------------------------------- /layouts/partials/breadcrumb.html: -------------------------------------------------------------------------------- 1 | 30 | -------------------------------------------------------------------------------- /layouts/partials/css.html: -------------------------------------------------------------------------------- 1 | {{ $css := resources.Get "css/main.css" }} 2 | {{ $style := $css | css.PostCSS }} 3 | 4 | {{ if hugo.IsProduction }} 5 | {{ $style = $style | minify | fingerprint }} 6 | 7 | {{ else }} 8 | 9 | {{ end }} 10 | 11 | 12 | 13 | 14 | 15 | 16 | -------------------------------------------------------------------------------- /layouts/partials/docs/content.html: -------------------------------------------------------------------------------- 1 |
2 |
3 | {{ with .Content }} 4 | {{ . }} 5 | {{ end }} 6 | 7 | {{ if .Sections }} 8 |
9 | {{ range .Sections }} 10 |
11 | 12 | {{ .Title }} 13 | 14 |
15 | {{ end }} 16 |
17 | {{ end }} 18 |
19 |
20 | 21 | {{ if .IsSection}} 22 | {{ range .RegularPagesRecursive }} 23 |
  • 24 | {{.Params.term}} 25 |
    • 26 | {{ end }} 27 | {{ end }} -------------------------------------------------------------------------------- /layouts/partials/docs/content_wordlist.html: -------------------------------------------------------------------------------- 1 |
    2 |
    3 |
    4 | {{ with .Content }} 5 | {{ . }} 6 | {{ end }} 7 |
    8 |
    9 |
    10 | 11 | -------------------------------------------------------------------------------- /layouts/partials/docs/section-nav_wordlist.html: -------------------------------------------------------------------------------- 1 | 33 | -------------------------------------------------------------------------------- /layouts/partials/docs/section-wordlist.html: -------------------------------------------------------------------------------- 1 |
    2 |
    3 |
    4 |
    5 | {{ partial "breadcrumb.html" . }} 6 |
    7 | 8 |

    {{ .Page.Title | markdownify }}

    9 | {{ with .Page.Description }} 10 |

    {{ . | markdownify }}

    11 | {{ end }} 12 | 13 |
    14 | {{ partial "docs/content_wordlist.html" . }} 15 |
    16 |
    17 | 18 |
    19 |
    20 |

    In This Section

    21 | {{ partial "docs/section-nav_wordlist.html" . }} 22 |
    23 |
    24 |
    25 |
    26 | -------------------------------------------------------------------------------- /layouts/partials/favicon.html: -------------------------------------------------------------------------------- 1 | {{ $favicon := site.Params.favicon }} 2 | {{ with $favicon }} 3 | {{ $url := . | relURL }} 4 | 5 | {{ end }} 6 | -------------------------------------------------------------------------------- /layouts/partials/functions/convertTime.html: -------------------------------------------------------------------------------- 1 | {{ $timeInput := .time }} 2 | {{ $locationString := .location }} 3 | {{ $format := .format | default "Jan 2, 3:04 PM MST" }} 4 | 5 | {{ $location := time.LoadLocation $locationString }} 6 | {{ with $location }} 7 | {{ ($timeInput.In .).Format $format }} 8 | {{ else }} 9 | {{ warnf "convertTime Partial: Failed to load location '%s'" $locationString }} 10 | (Error: {{ $locationString }}) 11 | {{ end }} -------------------------------------------------------------------------------- /layouts/partials/github-edit.html: -------------------------------------------------------------------------------- 1 |
    2 | {{ $repoUrl := .Site.Params.repositoryUrl }} 3 | {{ $filePath := .File.Path }} 4 | {{ $editUrl := print $repoUrl "/content/" $filePath }} 5 | 6 |   Edit on GitHub 7 | 8 |
    9 | -------------------------------------------------------------------------------- /layouts/partials/home/content.html: -------------------------------------------------------------------------------- 1 |
    2 |
    3 | {{ with .Content }} 4 |
    5 | {{ . }} 6 |
    7 | {{ end }} 8 |
    9 |
    10 | -------------------------------------------------------------------------------- /layouts/partials/home/hero.html: -------------------------------------------------------------------------------- 1 | {{ $title := site.Title }} 2 | {{ $desc := site.Params.description | markdownify }} 3 |
    4 |
    5 |

    6 | {{ $title }} 7 |

    8 | 9 | {{ with $desc }} 10 |

    11 | {{ . }} 12 |

    13 | {{ end }} 14 | 15 |
    16 | 17 | Learn more 18 | 19 | 20 | 21 | Word Lists v1.0 22 | 23 |
    24 |
    25 |
    26 | -------------------------------------------------------------------------------- /layouts/partials/javascript.html: -------------------------------------------------------------------------------- 1 | {{ $app := resources.Get "js/app.js" | fingerprint }} 2 | 3 | 4 | 5 | 6 | 7 | {{ with resources.Get "js/main.js" }} 8 | {{ $js := . }} 9 | {{ if hugo.IsProduction }} 10 | {{ $js = $js | minify | fingerprint }} 11 | 12 | {{ else }} 13 | 14 | {{ end }} 15 | {{ end }} 16 | -------------------------------------------------------------------------------- /layouts/partials/menu-loop.html: -------------------------------------------------------------------------------- 1 | {{ $home := site.BaseURL }} 2 | {{ $here := .RelPermalink }} 3 | {{ $main := site.Menus.main }} 4 | 5 |
      6 | {{ with $main }} 7 | {{ range . }} 8 | {{ $isHere := eq .URL $here }} 9 |
    • 14 | 30 | 31 | {{ if .HasChildren }} 32 |
      33 | {{ range .Children }} 34 | 36 | {{ .Name }} 37 | 38 | {{ if .HasChildren }} 39 |
      40 | {{ range .Children }} 41 | 42 | {{ .Name }} 43 | 44 | {{ end }} 45 |
      46 | {{ end }} 47 | {{ end }} 48 |
      49 | {{ end }} 50 |
      • 51 | {{ end }} 52 |
    • 53 | 54 |
      • 55 | {{ end }} 56 | 57 | 58 |
    59 | -------------------------------------------------------------------------------- /layouts/partials/navbar.html: -------------------------------------------------------------------------------- 1 | {{ $home := site.BaseURL }} 2 | {{ $here := .RelPermalink }} 3 | {{ $title := site.Title }} 4 | {{ $logo := site.Params.logos.navbar }} 5 | {{ $menu := site.Menus.main }} 6 | {{ $social := site.Params.social }} 7 | 8 | 87 | 88 | -------------------------------------------------------------------------------- /layouts/partials/pagination.html: -------------------------------------------------------------------------------- 1 | {{ $pag := $.Paginator }} 2 | {{ if gt $pag.TotalPages 1 }} 3 | 51 | {{ end }} -------------------------------------------------------------------------------- /layouts/partials/section-nav.html: -------------------------------------------------------------------------------- 1 | {{ $allSections := site.Sections }} 2 | {{ $docsSections := where $allSections "Section" "test-content" }} 3 | {{ $thisUrl := .RelPermalink }} 4 | 5 | {{ range $docsSections }} 6 | {{ $isThisPage := eq .RelPermalink $thisUrl }} 7 | 34 | -------------------------------------------------------------------------------- /layouts/partials/sidebar.html: -------------------------------------------------------------------------------- 1 | 2 | {{ $home := site.BaseURL }} 3 | {{ $here := .RelPermalink }} 4 | {{ $title := site.Title }} 5 | {{ $logo := site.Params.logos.navbar }} 6 | {{ $menu := site.Menus.main }} 7 | {{ $social := site.Params.social }} 8 | 9 |
    10 |
    11 |
    12 | 13 | {{ if $logo }} 14 | {{ $url := printf "img/logos/%s" $logo | relURL }} 15 | 16 | {{ else }} 17 | {{ $title }} 18 | {{ end }} 19 | 20 |
    21 | {{ with $social }} 22 | {{ partial "social-buttons.html" . }} 23 | {{ end }} 24 |
    25 |
    26 | 27 | 42 |
    43 |
    44 | -------------------------------------------------------------------------------- /layouts/partials/social-buttons.html: -------------------------------------------------------------------------------- 1 | {{ range . }} 2 | 3 | 4 | 5 | {{ end }} 6 | -------------------------------------------------------------------------------- /layouts/partials/wordlist/download-section.html: -------------------------------------------------------------------------------- 1 |
    2 |

    Download Word Lists

    3 | 4 |
    5 | 6 | HTML 7 | 8 | 9 | OpenDocument 10 | 11 | 12 | JSON 13 | 14 | {{ if eq .Layout "section" }} 15 | 16 | PDF 17 | 18 | {{ end }} 19 |
    20 | 21 |
    -------------------------------------------------------------------------------- /layouts/partials/wordlist/terms-list.html: -------------------------------------------------------------------------------- 1 | {{ if .IsSection}} 2 |
    3 |

    Terms in this section

    4 |
    5 | {{ range .RegularPagesRecursive }} 6 |
    7 | 8 | {{.Params.term}} 9 | 10 |
    11 | {{ end }} 12 |
    13 |
    14 | {{ end }} -------------------------------------------------------------------------------- /layouts/shortcodes/button.html: -------------------------------------------------------------------------------- 1 | 8 | {{.Get 1}} 9 | 10 | -------------------------------------------------------------------------------- /layouts/shortcodes/calendar.html: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /layouts/shortcodes/cta.html: -------------------------------------------------------------------------------- 1 |

    2 | 3 | 8 | Get involved 9 | 10 | 11 | 12 | 13 | 18 | Suggest a term for review 19 | 20 | 21 |

    -------------------------------------------------------------------------------- /layouts/shortcodes/jumbotron.html: -------------------------------------------------------------------------------- 1 | 2 | {{ $bgcolor := .Get "bgcolor" }} 3 | {{ $textcolor := .Get "textcolor" }} 4 | {{ $title := .Get "title" }} 5 | {{ $align_class := .Get "align" }} 6 |
    8 |
    9 |

    10 | {{ $title }} 11 |

    12 | 13 |

    14 | {{ .Inner }} 15 |

    16 |
    17 |
    -------------------------------------------------------------------------------- /layouts/shortcodes/leadership.html: -------------------------------------------------------------------------------- 1 |
    2 | 3 |
    4 | 5 |

    Stephen Augustus

    6 |

    Head of Open Source
    7 | Cisco

    8 |

    Community Workstream Lead

    9 |
    10 | 11 |
    12 | 13 |

    Jason Brooks

    14 |

    Manager, OSPO
    Red Hat

    15 |

    Community Workstream Lead

    16 |
    17 | 18 |
    19 | 20 |

    Dale Davis Jones

    21 |

    Vice President & Distinguished Engineer
    IBM

    22 |

    Community Workstream Lead

    23 |
    24 | 25 | 26 | 27 |
    28 | 29 |

    Jim St. Leger

    30 |

    Marketing Manager
    Intel

    31 |

    Marketing Workstream Lead

    32 |
    33 | 34 |
    35 | 36 |

    Joanna Lee

    37 |

    Partner
    Gesmer Updegrove LLP

    38 |

    Standards Workstream Lead

    39 |
    40 | 41 |
    42 | 43 |

    André Pellet

    44 |

    Director, Content and Knowledge Management
    Dell EMC

    45 |

    Company Workstream Lead

    46 |
    47 | 48 |
    49 | 50 |

    Monica Rush

    51 |

    Senior Program Manager
    Microsoft

    52 |

    Company Workstream Lead

    53 |
    54 | 55 |
    56 | 57 |

    Priyanka Sharma

    58 |

    General Manager
    59 | CNCF

    60 |

    Marketing Workstream Lead

    61 |
    62 | 63 | 64 |
    65 | 66 |

    Matthew Schnoor

    67 |

    Debug Architect
    Intel

    68 |

    Standards Workstream Lead

    69 |
    70 | 71 |
    72 | 73 |

    Ed Warnicke

    74 |

    Distinguished Engineer
    Cisco

    75 |
    76 | 77 |
    78 | 79 |

    Abubakar Siddiq Ango

    80 |

    Developer Evangelism Program Manager
    GitLab

    81 |
    82 | 83 |
    84 | 85 |

    Taylor Waggoner

    86 |

    Program Manager
    CNCF

    87 |
    88 | 89 | 90 |
    91 | 92 | 93 | 94 |

    Emeritus

    95 | 96 |
    97 |
    98 | 99 |

    Celeste Horgan

    100 |

    Staff Technical Writer
    Stripe

    101 |

    Inclusive Naming Co-Founder

    102 |
    103 | 104 |
    105 | 106 |

    Larry Kunz

    107 |

    Language Workstream Lead

    108 |
    109 | 110 |
    111 | -------------------------------------------------------------------------------- /layouts/shortcodes/localize.html: -------------------------------------------------------------------------------- 1 | {{ $time := .Get "time" }} 2 | {{ $tz := .Get "tz" }} 3 | -------------------------------------------------------------------------------- /layouts/shortcodes/logos.html: -------------------------------------------------------------------------------- 1 | 2 |
    3 |

    Premier Sponsors

    4 |
    5 |
    6 | 7 |
    8 |
    9 | 10 |
    11 |
    12 | 13 |
    14 |
    15 |
    16 | 17 | 18 | 19 | 20 |
    21 |

    Champion Sponsors

    22 |
    23 |
    24 | 25 |
    26 |
    27 | 28 |
    29 |
    30 |
    31 | 32 | 33 | 34 |
    35 |

    Associate Sponsors

    36 |
    37 | 38 |
    39 | 40 |
    41 |
    42 | 43 |
    44 |
    45 | 46 |
    47 | 48 |
    49 |
    50 | -------------------------------------------------------------------------------- /layouts/word-lists/list.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |
    5 | {{ partial "breadcrumb.html" . }} 6 |
    7 | 8 |

    {{ .Title }}

    9 | 10 | {{ with .Description }} 11 |

    {{ . }}

    12 | {{ end }} 13 | 14 |
    15 | {{ .Content }} 16 |
    17 | 18 | {{ if .Pages }} 19 |
    20 |

    Terms in this list

    21 |
    22 | {{ range .Pages }} 23 |
    24 | 25 | {{ with .Params.term }}{{ . }}{{ else }}{{ .Title }}{{ end }} 26 | 27 | {{ with .Params.definition }} 28 |

    {{ . | markdownify }}

    29 | {{ end }} 30 |
    31 | {{ end }} 32 |
    33 |
    34 | {{ end }} 35 | 36 |
    37 |
    38 |

    Word Lists

    39 | {{ partial "docs/section-nav_wordlist.html" . }} 40 |
    41 |
    42 |
    43 |
    44 | {{ end }} -------------------------------------------------------------------------------- /layouts/word-lists/single.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |
    5 | {{ partial "breadcrumb.html" . }} 6 |
    7 | 8 |
    9 |
    10 |

    {{ with .Params.term }}{{ . }}{{ else }}{{ .Title }}{{ end }}

    11 | {{ with .Description }} 12 |

    {{ . }}

    13 | {{ end }} 14 |
    15 | 16 |
    17 | {{ .Content }} 18 | 19 | 20 | {{ if .Params.term }} 21 |
    22 | {{ with .Params.definition }} 23 |
    24 |

    Definition

    25 |

    {{ . | markdownify }}

    26 |
    27 | {{ end }} 28 | 29 | {{ with .Params.related_terms }} 30 |
    31 |

    Related Terms

    32 |
      33 | {{ range . }} 34 |
    • {{ . }}
      • 35 | {{ end }} 36 |
    37 |
    38 | {{ end }} 39 | 40 | {{ with .Params.usage_context }} 41 |
    42 |

    Usage Context

    43 |

    {{ . | markdownify }}

    44 |
    45 | {{ end }} 46 | 47 | {{ with .Params.recommendation }} 48 |
    49 |

    Recommendation

    50 |

    {{ . | markdownify }}

    51 |
    52 | {{ end }} 53 | 54 | {{ with .Params.recommended_replacements }} 55 |
    56 |

    Recommended Replacements

    57 |
      58 | {{ range . }} 59 |
    • {{ . }}
      • 60 | {{ end }} 61 |
    62 |
    63 | {{ end }} 64 | 65 | {{ with .Params.unsuitable_replacements }} 66 |
    67 |

    Unsuitable Replacements

    68 |
      69 | {{ range . }} 70 |
    • {{ . }}
      • 71 | {{ end }} 72 |
    73 |
    74 | {{ end }} 75 | 76 | {{ with .Params.rationale }} 77 |
    78 |

    Rationale

    79 |

    {{ . | markdownify }}

    80 |
    81 | {{ end }} 82 | 83 | {{ with .Params.status }} 84 |
    85 |

    Term Status

    86 |

    {{ . | markdownify }}

    87 |
    88 | {{ end }} 89 | 90 | {{ with .Params.supporting_content }} 91 |
    92 |

    Supporting Content

    93 |

    {{ . | markdownify }}

    94 |
    95 | {{ end }} 96 |
    97 | {{ end }} 98 |
    99 |
    100 | 101 |
    102 |
    103 |

    Word Lists

    104 | {{ partial "docs/section-nav_wordlist.html" . }} 105 |
    106 |
    107 |
    108 |
    109 | {{ end }} -------------------------------------------------------------------------------- /layouts/word-lists/wordlists.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 | {{ partial "breadcrumb.html" . }} 5 |
    6 | 7 |
    8 |

    {{ .Title }}

    9 | 10 |
    11 | {{ .Content }} 12 |
    13 | 14 |
    15 |
    16 |

    Tier 1: Replace Immediately

    17 |

    Terms that should be replaced whenever encountered. These terms have strong social consensus for replacement.

    18 | 19 | View Tier 1 Terms 20 | 21 |
    22 | 23 |
    24 |

    Tier 2: Strongly Consider Replacement

    25 |

    Terms that should be strongly considered for replacement. These terms have growing consensus for replacement.

    26 | 27 | View Tier 2 Terms 28 | 29 |
    30 | 31 |
    32 |

    Tier 3: Terms Under Discussion

    33 |

    Terms that are being discussed for potential replacement. These terms have some consensus for replacement.

    34 | 35 | View Tier 3 Terms 36 | 37 |
    38 |
    39 | 40 |
    41 |

    Download Word Lists

    42 |

    The Inclusive Naming Word Lists v1.0 are available as a single downloadable file in these formats:

    43 |
    44 | 45 | HTML 46 | 47 | 48 | OpenDocument (.odt) 49 | 50 | 51 | JSON 52 | 53 | 54 | PDF 55 | 56 |
    57 |
    58 |
    59 |
    60 | {{ end }} -------------------------------------------------------------------------------- /layouts/wordlist/404.json: -------------------------------------------------------------------------------- 1 | { 2 | "error" : "404", 3 | "message" : "page not found" 4 | } -------------------------------------------------------------------------------- /layouts/wordlist/baseof.custom: -------------------------------------------------------------------------------- 1 | {{ $lang := site.LanguageCode }} 2 | 3 | 4 | 5 | 6 | {{ block "title" . }} 7 | {{ site.Title }} 8 | {{ end }} 9 | 10 | {{ partial "css.html" . }} 11 | {{ partial "favicon.html" . }} 12 | 13 | 14 | 15 | 16 | 17 |
    18 |
    19 | {{ block "main" . }} 20 | {{ end }} 21 |
    22 |
    23 | 24 | 25 | -------------------------------------------------------------------------------- /layouts/wordlist/baseof.html: -------------------------------------------------------------------------------- 1 | {{ $lang := site.LanguageCode }} 2 | 3 | 4 | 5 | 6 | {{ block "title" . }} 7 | {{ site.Title }} 8 | {{ end }} 9 | 10 | {{ partial "css.html" . }} 11 | {{ partial "favicon.html" . }} 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | {{ partial "navbar.html" . }} 20 | 21 |
    22 |
    23 | {{ block "main" . }} 24 | {{ end }} 25 |
    26 |
    27 | 28 | {{ partial "footer.html" . }} 29 | {{ partial "javascript.html" }} 30 | 31 | 32 | -------------------------------------------------------------------------------- /layouts/wordlist/baseof.json.json: -------------------------------------------------------------------------------- 1 | { 2 | "data" : {{ block "response" .}}{{ end }} 3 | } -------------------------------------------------------------------------------- /layouts/wordlist/item.json.json: -------------------------------------------------------------------------------- 1 | { 2 | "term": "{{ .Params.term }}", 3 | "tier" : "{{ .Params.tier }}", 4 | "recommendation": "{{.Params.recommendation}}", 5 | "recommended_replacements": {{.Params.recommended_replacements | jsonify}}, 6 | "term_page" : "{{ .Permalink }}index.html" 7 | } -------------------------------------------------------------------------------- /layouts/wordlist/list.json.json: -------------------------------------------------------------------------------- 1 | {{ define "response" }} 2 | [ 3 | {{ range $index, $e := .Site.Pages }} 4 | {{ if and ($index) ( .Params.term) }} 5 | {{if ne ( .Params.term) "abort"}},{{end}} 6 | {{ .Render "item" }} 7 | {{ end }} 8 | {{ end }} 9 | ] 10 | {{ end }} -------------------------------------------------------------------------------- /layouts/wordlist/section.custom: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |

    {{ .Page.Title | markdownify }}

    5 | {{ with .Page.Description }} 6 |

    {{ . | markdownify }}

    7 | {{ end }} 8 | 9 |
    10 | {{ partial "docs/content_wordlist.html" . }} 11 |
    12 | 13 |
    14 |
    15 |

    Word Lists

    16 | {{ partial "docs/section-nav_wordlist.html" . }} 17 |
    18 |
    19 | 20 |
    21 | © 2023 The Inclusive Naming Initiative authors and collaborating organizations 22 |
    23 |
    24 |
    25 | {{ end }} 26 | -------------------------------------------------------------------------------- /layouts/wordlist/section.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |
    5 | {{ partial "breadcrumb.html" . }} 6 |
    7 | 8 |
    9 |
    10 |

    {{ .Page.Title | markdownify }}

    11 | {{ with .Page.Description }} 12 |

    {{ . | markdownify }}

    13 | {{ end }} 14 | 15 |
    16 | {{ partial "docs/content_wordlist.html" . }} 17 |
    18 |
    19 | 20 |
    21 | {{ partial "wordlist/terms-list.html" . }} 22 | {{ partial "wordlist/download-section.html" . }} 23 |
    24 |
    25 |
    26 |
    27 | {{ end }} 28 | -------------------------------------------------------------------------------- /layouts/wordlist/single.custom: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |
    5 |
    6 |

    Word List: Tier {{ .Params.tier }}

    7 |

    Term: {{ .Params.term }}

    8 |
    9 | 10 |
    11 |
    12 | {{ with .Params.definition }} 13 |
    14 |

    Definition

    15 |

    {{ . | markdownify }}

    16 |
    17 | {{ end }} 18 | 19 | {{ with .Params.related_terms }} 20 |
    21 |

    Related Terms

    22 |
      23 | {{ range . }} 24 |
    • {{ . }}
      • 25 | {{ end }} 26 |
    27 |
    28 | {{ end }} 29 | 30 | {{ with .Params.usage_context }} 31 |
    32 |

    Usage Context

    33 |

    {{ . | markdownify }}

    34 |
    35 | {{ end }} 36 | 37 | {{ with .Params.recommendation }} 38 |
    39 |

    Recommendation

    40 |

    {{ . | markdownify }}

    41 |
    42 | {{ end }} 43 | 44 | {{ with .Params.recommended_replacements }} 45 |
    46 |

    Recommended Replacements

    47 |
      48 | {{ range . }} 49 |
    • {{ . }}
      • 50 | {{ end }} 51 |
    52 |
    53 | {{ end }} 54 | 55 | {{ with .Params.unsuitable_replacements }} 56 |
    57 |

    Unsuitable Replacements

    58 |
      59 | {{ range . }} 60 |
    • {{ . }}
      • 61 | {{ end }} 62 |
    63 |
    64 | {{ end }} 65 | 66 | {{ with .Params.rationale }} 67 |
    68 |

    Rationale

    69 |

    {{ . | markdownify }}

    70 |
    71 | {{ end }} 72 | 73 | {{ with .Params.status }} 74 |
    75 |

    Term Status

    76 |

    {{ . | markdownify }}

    77 |
    78 | {{ end }} 79 | 80 | {{ with .Params.supporting_content }} 81 |
    82 |

    Supporting Content

    83 |

    {{ . | markdownify }}

    84 |
    85 | {{ end }} 86 |
    87 |
    88 |
    89 |
    90 |
    91 | {{ end }} 92 | -------------------------------------------------------------------------------- /layouts/wordlist/single.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
    3 |
    4 |
    5 | {{ partial "breadcrumb.html" . }} 6 |
    7 | 8 |
    9 |
    10 |
    11 |
    12 |

    Word List: Tier {{ .Params.tier }}

    13 |

    Term: {{ .Params.term }}

    14 |
    15 | 16 |
    17 |
    18 | {{ with .Params.definition }} 19 |
    20 |

    Definition

    21 |

    {{ . | markdownify }}

    22 |
    23 | {{ end }} 24 | 25 | {{ with .Params.related_terms }} 26 |
    27 |

    Related Terms

    28 |
      29 | {{ range . }} 30 |
    • {{ . }}
      • 31 | {{ end }} 32 |
    33 |
    34 | {{ end }} 35 | 36 | {{ with .Params.usage_context }} 37 |
    38 |

    Usage Context

    39 |

    {{ . | markdownify }}

    40 |
    41 | {{ end }} 42 | 43 | {{ with .Params.recommendation }} 44 |
    45 |

    Recommendation

    46 |

    {{ . | markdownify }}

    47 |
    48 | {{ end }} 49 | 50 | {{ with .Params.recommended_replacements }} 51 |
    52 |

    Recommended Replacements

    53 |
      54 | {{ range . }} 55 |
    • {{ . }}
      • 56 | {{ end }} 57 |
    58 |
    59 | {{ end }} 60 | 61 | {{ with .Params.unsuitable_replacements }} 62 |
    63 |

    Unsuitable Replacements

    64 |
      65 | {{ range . }} 66 |
    • {{ . }}
      • 67 | {{ end }} 68 |
    69 |
    70 | {{ end }} 71 | 72 | {{ with .Params.rationale }} 73 |
    74 |

    Rationale

    75 |

    {{ . | markdownify }}

    76 |
    77 | {{ end }} 78 | 79 | {{ with .Params.status }} 80 |
    81 |

    Term Status

    82 |

    {{ . | markdownify }}

    83 |
    84 | {{ end }} 85 | 86 | {{ with .Params.supporting_content }} 87 |
    88 |

    Supporting Content

    89 |

    {{ . | markdownify }}

    90 |
    91 | {{ end }} 92 |
    93 |
    94 |
    95 |
    96 | 97 |
    98 | {{ partial "wordlist/download-section.html" . }} 99 |
    100 |
    101 |
    102 |
    103 | {{ end }} 104 | -------------------------------------------------------------------------------- /layouts/wordlist/single.json.json: -------------------------------------------------------------------------------- 1 | {{ define "response" }} {{ .Render "item" }} {{ end }} -------------------------------------------------------------------------------- /netlify.toml: -------------------------------------------------------------------------------- 1 | [build] 2 | publish = "public" 3 | command = "hugo" 4 | 5 | [build.environment] 6 | HUGO_VERSION = "0.145.0" 7 | HUGO_ENV = "production" 8 | HUGO_ENABLEGITINFO = "true" 9 | NODE_VERSION = "16.14.0" 10 | 11 | [context.deploy-preview] 12 | command = "hugo" 13 | 14 | [context.branch-deploy] 15 | command = "hugo" 16 | 17 | [context.production.environment] 18 | HUGO_ENV = "production" 19 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "hugo-tailwind-site", 3 | "version": "1.0.0", 4 | "description": "Hugo site with Tailwind CSS", 5 | "main": "index.js", 6 | "scripts": { 7 | "dev": "hugo server", 8 | "build": "hugo --minify" 9 | }, 10 | "dependencies": { 11 | "@tailwindcss/typography": "^0.5.9", 12 | "tailwindcss": "^3.3.2" 13 | }, 14 | "devDependencies": { 15 | "autoprefixer": "^10.4.21", 16 | "postcss": "^8.5.3", 17 | "postcss-cli": "^10.1.0", 18 | "tailwindcss": "^3.3.2" 19 | } 20 | } 21 | -------------------------------------------------------------------------------- /postcss.config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | plugins: { 3 | tailwindcss: {}, 4 | autoprefixer: {} 5 | } 6 | } -------------------------------------------------------------------------------- /static/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/.DS_Store -------------------------------------------------------------------------------- /static/_redirects: -------------------------------------------------------------------------------- 1 | /language/word-list /word-lists 2 | /word-lists/overview /word-lists 3 | -------------------------------------------------------------------------------- /static/favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/favicon.png -------------------------------------------------------------------------------- /static/img/headshots/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/.DS_Store -------------------------------------------------------------------------------- /static/img/headshots/abubakar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/abubakar.png -------------------------------------------------------------------------------- /static/img/headshots/apellet.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/apellet.jpg -------------------------------------------------------------------------------- /static/img/headshots/bill.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/bill.png -------------------------------------------------------------------------------- /static/img/headshots/celeste.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/celeste.png -------------------------------------------------------------------------------- /static/img/headshots/dale.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/dale.jpg -------------------------------------------------------------------------------- /static/img/headshots/ewarnicke.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/ewarnicke.png -------------------------------------------------------------------------------- /static/img/headshots/jbrooks.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/jbrooks.jpg -------------------------------------------------------------------------------- /static/img/headshots/jlee.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/jlee.jpg -------------------------------------------------------------------------------- /static/img/headshots/jstleger.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/jstleger.jpg -------------------------------------------------------------------------------- /static/img/headshots/lkunz.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/lkunz.jpg -------------------------------------------------------------------------------- /static/img/headshots/mrush.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/mrush.jpg -------------------------------------------------------------------------------- /static/img/headshots/mschnoor.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/mschnoor.jpg -------------------------------------------------------------------------------- /static/img/headshots/priyanka.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/priyanka.jpg -------------------------------------------------------------------------------- /static/img/headshots/stephen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/stephen.png -------------------------------------------------------------------------------- /static/img/headshots/taylor-waggoner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/headshots/taylor-waggoner.png -------------------------------------------------------------------------------- /static/img/icons/json-file-tiny.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/icons/json-file-tiny.png -------------------------------------------------------------------------------- /static/img/layout/hero-bg-compressed.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/layout/hero-bg-compressed.jpg -------------------------------------------------------------------------------- /static/img/layout/hero-bg.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/layout/hero-bg.jpg -------------------------------------------------------------------------------- /static/img/layout/hero-bg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/layout/hero-bg.png -------------------------------------------------------------------------------- /static/img/layout/hero-bg.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /static/img/layout/sidebar-bg.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/BMC.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/BMC.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/Splunk.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/Splunk.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/akamai.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/akamai.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/canonical-group-limited.svg: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/cisco.svg: -------------------------------------------------------------------------------- 1 | 2 | Cisco.com Worldwide 3 | 4 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/cncf-color.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/cncf-color.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/cncf-color.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/cncf-white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/cncf-white.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/extreme-networks-inc.svg: -------------------------------------------------------------------------------- 1 | ExtremeLogo.FullLockup_HOR.FullColor -------------------------------------------------------------------------------- /static/img/logos/sponsors/ibm.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/intel.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 5 | 9 | 10 | 11 | 23 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /static/img/logos/sponsors/lf-color.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/lf-color.png -------------------------------------------------------------------------------- /static/img/logos/sponsors/redhat-color.svg: -------------------------------------------------------------------------------- 1 | RedHat-Logo-A-Color -------------------------------------------------------------------------------- /static/img/logos/sponsors/vmware.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/logos/sponsors/vmware.png -------------------------------------------------------------------------------- /static/img/media-mentions/joinup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/media-mentions/joinup.png -------------------------------------------------------------------------------- /static/img/media-mentions/nytimes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/media-mentions/nytimes.png -------------------------------------------------------------------------------- /static/img/media-mentions/the-register.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/media-mentions/the-register.png -------------------------------------------------------------------------------- /static/img/media-mentions/theCube.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/media-mentions/theCube.png -------------------------------------------------------------------------------- /static/img/media-mentions/theserverside.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/media-mentions/theserverside.png -------------------------------------------------------------------------------- /static/img/test/architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/inclusivenaming/website/534f34911fcd91f865bdf76f67324342b8a60420/static/img/test/architecture.png -------------------------------------------------------------------------------- /static/json/dci-lint-config-recommended-v1.json: -------------------------------------------------------------------------------- 1 | { 2 | "version": "1.0.0", 3 | "targetPhrasePatterns": [ 4 | "master", 5 | "slave", 6 | "blacklist", 7 | "whitelist" 8 | ] 9 | } -------------------------------------------------------------------------------- /tailwind.config.js: -------------------------------------------------------------------------------- 1 | /** @type {import('tailwindcss').Config} */ 2 | module.exports = { 3 | content: ["./layouts/**/*.html", "./content/**/*.md", "./content/**/*.html"], 4 | theme: { 5 | extend: { 6 | colors: { 7 | 'purple': '#704BDB', 8 | 'purple-dark': '#663ed8', 9 | 'primary': '#5a0fc8', 10 | }, 11 | fontFamily: { 12 | 'sans': ['Cairo', 'sans-serif'], 13 | 'heading': ['Lexend Deca', 'sans-serif'], 14 | }, 15 | backgroundColor: { 16 | 'primary-nav': '#5a0fc8', 17 | }, 18 | typography: { 19 | DEFAULT: { 20 | css: { 21 | h1: { 22 | color: '#333333', 23 | fontWeight: '700', 24 | fontFamily: 'Lexend Deca, sans-serif', 25 | }, 26 | h2: { 27 | color: '#333333', 28 | fontWeight: '600', 29 | fontFamily: 'Lexend Deca, sans-serif', 30 | }, 31 | h3: { 32 | color: '#333333', 33 | fontWeight: '600', 34 | fontFamily: 'Lexend Deca, sans-serif', 35 | }, 36 | a: { 37 | color: '#704BDB', 38 | '&:hover': { 39 | color: '#663ed8', 40 | }, 41 | }, 42 | }, 43 | }, 44 | }, 45 | }, 46 | }, 47 | plugins: [ 48 | require('@tailwindcss/typography'), 49 | ], 50 | } --------------------------------------------------------------------------------