rename master branch about did-use-cases

[dlongley]

My understanding is that github is working on tools to make this sort of transition easier. I support moving to the new name, but I recommend we wait until the tools are ready to make it an easy change and so that we don't duplicate effort.

[iherman]

See my comment on w3c/did-core#332 (comment). TL;DR: this step creates problems with the github.io paging mechanism.

[philarcher]

Thanks to @iherman, this has been done.

[selfissued]

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.

[philarcher]

OK, so from this discussion, there's nothing to be done, at least for now. Putting this on the 'forget unless there's a reason to remember pile.

[brentzundel]

I'm fine with waiting to do this until tools to do so are provided by github, unless those tools aren't made available in 6 months.

[philarcher]

As discussed at the (virtual) F2F, there is no action to take for this issue. Closing now.

[brentzundel]

there will be steps to take, and I would like to keep this open as a reminder to take them when they are available

[brentzundel]

It looks like they're still working on tooling to make this easier: https://github.com/github/renaming#later-this-year-seamless-move-for-existing-repositories-
but these should be in place by the end of the year.

[jandrieu]

We agree with this direction, but frankly, the editors aren't sure how to do this. It seems like it would need adjustments to echidna, which we have famously failed to do correctly. @iherman is this a task you can take care of?

[iherman]

Actually, I think I am the only one who take care of it (you need admin rights). We did it for the did-core, but I know @msporny had done some preliminary steps in merging and branching and all that jazz... @msporny do you still have the list for the steps we had to take?

(Actually... if we decide to publish the note for the use cases soon, I would expect this repository to go very quiet. Maybe we should wait until then...)