Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use more inclusive language in this project #880

Closed
3 tasks done
tunetheweb opened this issue Jun 18, 2020 · 6 comments
Closed
3 tasks done

Use more inclusive language in this project #880

tunetheweb opened this issue Jun 18, 2020 · 6 comments
Assignees
Labels
development Building the Almanac tech stack writing Related to wording and content
Milestone

Comments

@tunetheweb
Copy link
Member

tunetheweb commented Jun 18, 2020

Following on from recent movements in other projects, I'd like to use more inclusive language in this project.

Namely:

  • A few instances of "whitelist" in the Security chapter for CSP. These are perfectly valid (it's in the CSP spec after all), but can easily be reworded to avoid this whole debate. Replace whitelist #883
  • Rename master branch to main in Git. Master branch rename #881
  • Delete master branch after release and a period (2 weeks?), to avoid confusion.

Now I know some people have strong views as to the need, effectiveness and point of these sorts of changes, and I'm not wanting to get into the debate on whether or not these terms have anything to do with the negative connotations some might feel they have (whether intentional or not). However, I feel anything we can do to make people feel more inclusive is the right thing to do, and goes with the ethos of this project. Additionally these are very small changes for us and now is the right time to make these changes (before 2020 ramps up in earnest).

For the master -> main rename the following steps need to be done (this will keep all our commit history btw):

Local copies and forks can be updated with these commands:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main

Then change your own default branch in /settings/branches for your repo.

Please comment if any technical concerns with this proposal or other suggested names rather than main.

@tunetheweb tunetheweb added development Building the Almanac tech stack writing Related to wording and content labels Jun 18, 2020
@rviscomi
Copy link
Member

I wholeheartedly endorse these changes.

When changing content, let's be sure to loop in the original authors.

@tunetheweb
Copy link
Member Author

Found some more references - including links to Licence and SQL on the website.

I still think it's worth doing though.

@tunetheweb
Copy link
Member Author

The default branch has been moved from master to main. Please follow above steps to update any local copies or forks. We will delete the master branch in a week or so.

Note if you want to just reset your forked main branch to be the same as the main repo, then you can do the following in your fork - after completing above steps:

git remote add upstream git@github.com:HTTPArchive/almanac.httparchive.org.git
git fetch upstream
git checkout main
git reset --hard upstream/main  
git push origin main --force 

@tunetheweb
Copy link
Member Author

Not heard any issues from this so plan to delete the master branch in next couple of days and the. close this issue. Shout if any reason not to!

@rviscomi
Copy link
Member

rviscomi commented Jul 1, 2020

SGTM!

@tunetheweb
Copy link
Member Author

It is gone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Building the Almanac tech stack writing Related to wording and content
Projects
None yet
Development

No branches or pull requests

2 participants