Repository transfer proposal

[alerque]

Before this repo goes any farther, can I propose that we ⓐ rename & archive or delete this repo out of the way, then ⓑ transfer this repo into this org namespace, then ⓒ rename it as appropriate, then ⓓ cherry pick the commits to this repo to the other one to bring it up to speed with the code of conduct, etc. This will best preserve the edit and comment history to the charter which I believe is significant.

[lianghai]

Right. I suggested (a), (c), and (b) to @svgeesus yesterday, but didn’t realized the possibility of (d). Let’s wait for Chris’s response.

[alerque]

Operation ⓓ is a bit of advanced Git foo whereby you can git cherry-pick or even git merge from repositories that don't have the same root. I'd be happy to take care of that step. In fact let me just open a PR onto the original repository with that step done so that it will come across ready made with the transfer in ⓑ.

[xfq]

This suggestion looks good to me, so I'll go ahead and do it today.

@svgeesus If you think there is anything wrong, please let me know.

[xfq]

• rename this repo
• transfer the CG repo into w3c org namespace
• make sure that people who have owner/admin permissions in the old CG repo have owner/admin permissions in the new CG repo too
• rename it as appropriate
• cherry pick the commits to the new repo
• archive/delete the old repo (this repo)

I will modify the task list here after I finish each step.

[alerque]

Thanks @xfq. I've done the cherry-picking (see this PR) and merged the result. Everything from this repo is already in the replacement, I think the only step left is to archive/delete.

[alerque]

(Closing this issue in case the decision is to archive, in which case this can't be closed later and it's nice to have zero open issues — but deletion is probably a fine outcome too.)