This page serves as a way to list any problematic language in the Sling codebases and the steps to remove it.
Topics
Rename 'master' Git branch
This branch can be renamed. One suggestion is to rename it to the 'main' branch although we should monitor what elsewhere is becoming the consensus on a new name for this branch.
Actions to take (potentially incomplete)
asking INFRA to change the default remote for 200+ repositories ( gitbox and github? )
adjusting Jenkins tooling (and potentially Jenkins jobs)
evaluating whether we need to change something in SonarCloud
updating the 'repo' setup
updating documentation
asking everyone to update their local checkouts
needing to rebase (or drop!) existing PRs
Open questions:
- what happens to links once we rename branches? Do they go stale or can we redirect?
Find problematic language in code and rename if possible
- $ repo grep -i 'whitelist'
rename to ... - $ repo grep -i 'blacklist'
rename to ... - $ repo grep -i 'slave'
rename to ... - $ repo grep -i 'master'
rename to ...
We need to investigate if the rename has an impact on backward compatibility.
Actions to take
...
Open questions
- how should we handle API that is affected? See for instance https://github.com/apache/sling-org-apache-sling-discovery-base/tree/master/src/main/java/org/apache/sling/discovery/base/connectors/ping/wl
- how should we handle metatype entries that are affected?
Documentation changes
Problematic language
Any problematic language in the documentation on its own should be fixed.
Actions to take
...
Changes required because of code/git changes
Changes made in git and/or source code should be reflected in the associated documentation.
Actions to take
...