Gender neutral language
Open
Nobody has claimed this yet.
bug
feature: frontend 🖌️
medium
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Rough summary of https://help.nextcloud.com/t/geschlechtsneutrale-sprache-genderneutral/82200
- Avoid words like "Users" and use "Accounts" or "Person"
- Seems we also should avoid "Participant", it was suggested to also replace with "Person", but that doesn't really work as we then have the same word covering 2 different hierarchies and concepts. Also Participants can also be guests, groups, circles, ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Nextcloud forum discussion, then search the project for user-facing uses of “Users,” “Accounts,” “Person,” and “Participant.” Resolve the terminology and hierarchy questions before changing wording; done means the agreed gender-neutral language is applied consistently without conflating participants, guests, groups, or circles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- internationalization, localization
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100