w3c / did-test-suite

W3C DID Test Suite and Implementation Report

Home Page:https://w3c.github.io/did-test-suite/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

rename master branch

brentzundel opened this issue · comments

Summary

We should rename the branch master to main and use that going forward for our work.

From Problematic Terminology in Open-Source on master/slave terminology in software:

Use of this term is problematic. It references slavery to convey meaning about the relationship between two entities.

Removing this terminology from our workflow is a small gesture to include more people from marginalized groups in this project.

(I’m open to names other than main)

Technical Steps

  • create main branch from master
  • make main the default GitHub branch
  • modify github/central to use main for release notes reloading
  • redirect PRs to main in w3c/did-test-suite
  • move branch protections from master to main
  • modify docs to reference main instead of master
  • delete master branch to avoid confusion?

Feedback?

Please no. This wouldn't just affect the primary repository. This would affect every branch, every fork, and every local clone, requiring manual steps by all participants to make parallel changes to these copies. The chances of everyone getting this right are close to zero.

Using git correctly is already complicated enough. Please don't make this repository even more complicated than usual.

Its possible for us to do this, but I'm not going to unless directed to by chairs.

if we do it here, we should do it everywhere, at the same time...

IMO we should not do this, we already have enough problems with ECHIDNA / respec hosting...

however, if we are required to implement this change, we can only really do so when there are no PRs open.

so sooner rather than later on this decision would be good. @brentzundel @burnburn .

A conversation is ongoing here: w3c/did-core#332
GitHub and the W3C are both moving forward with plans to make this change simpler, but to my understanding they are not ready yet.

GitHub and the W3C are both moving forward with plans to make this change simpler, but to my understanding they are not ready yet.

I can do this in like 5 minutes... it's easy. I'll bring it up on the call today, there's no good reason for us to delay any longer. I'll need @iherman's help to change the repo settings (since I don't have access).

Done on 2021-03-25.