nodejs / nodejs/package-maintenance

Suggestion: Provide alternate phrasing dictionary

Open
#67 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pull request wanted
Dominant language
No language data
Stars
423
Forks
147
PR merge metrics
No merged PRs in 30d

Description

A lot of common used phrasing is offending and should be avoided. For example master/slave can be replaced with primary/secondary (or anything else). See this medium article for example. There are a lot more phrases.

I'd suggest providing a dictionary with alternate phrasing which can be discussed here or somewhere else. Package owners should be advised how to avoid pitfalls and be as inclusive as possible.

(just saw @bnb comment at #59 which leads me to suggest this)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with issue #67 and the referenced Medium article, then review its 18-comment discussion for an agreed scope. Done would require an agreed alternate-phrasing dictionary and guidance for package owners, but the issue does not identify files, tests, or an implementation entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.