Rename CamelCase repo names

[foolip]

#42 updated https://github.com/WICG/admin/wiki/Process-to-transfer-a-repo to say:

Admin: Check the repo name adheres to our repo naming policy: lowercase, dashes (foo-bar, not fooBar!). If it doesn't adhere, ask the owner user to rename their repo.

A bunch of repos still don't adhere to this convention. Here's a script to enumerate them:

const {Octokit} = require('@octokit/rest');
(async () => {
  const octokit = new Octokit();
  const options = octokit.repos.listForOrg.endpoint.merge({org: 'WICG'});
  const repos = await octokit.paginate(options);
  for (const repo of repos) {
    if (repo.archived) {
      continue;
    }
    if (!repo.name.match(/^[a-z0-9-.]+$/)) {
      console.log(repo.name);
    }
  }
})();

And the resulting list:

• BackgroundSync (Suggestion: rename repo and spec to background-sync (is BackgroundSync) background-sync#176)
• InputDeviceCapabilities
• ResizeObserver
• CSS-Parser-API
• ScrollToTextFragment
• requestPostAnimationFrame
• WebOTP

[foolip]

@marcoscaceres perhaps you can help with this?

The reason I keep noticing is that this ends up as a mismatch with directory names in WPT.

[tabatkins]

I'll need to do some renaming in Shepherd when this happens. Not an issue, just alerting myself to this thread.

[marcoscaceres]

Sorry, missed this... will get on it.

[marcoscaceres]

Ok, did the renames... will file bugs for each to let them know.

[tidoust]

Why an uppercase I for Input-device-capabilities?

It would be good to update biblio.json for specs that were already in Specref, typically Input Device Capabilities. And a redirect at least for this one, as it has been referenced in multiple documents.

For the CSS Parser API, am I right to think that the work has moved to the Houdini Task Force? The README and the spec in the WICG repo could perhaps mention it. And Specref needs to be updated as it still points at the WICG URL. I'll take care of it.

[foolip]

I ran the script again and found the same as @tidoust, "Input-device-capabilities". I've unchecked that in the checklist.

[tidoust]

For the CSS Parser API, am I right to think that the work has moved to the Houdini Task Force? The README and the spec in the WICG repo could perhaps mention it. And Specref needs to be updated as it still points at the WICG URL. I'll take care of it.

Hmm, actually, the houdini draft points at the WICG as the place where incubation happens, so I suspect that the work has not really moved yet. In which case, it would make sense to re-insert an entry for it in biblio.json.

[marcoscaceres]

@tidoust reminded me to add the redirects over in the wicg.github.io repo.

[tidoust]

GitHub seems lost with the lowercase rename for input-device-capabilities. The repo correctly appears at https://github.com/wicg/input-device-capabilities but AFAICT the spec is still published at https://wicg.github.io/Input-device-capabilities (with an uppercase I). It may be worth switching off and on again GitHub Pages for the repo...

[marcoscaceres]

input-device-capabilities is fixed now.