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

Proposal: pick dashed-names instead of DashedNames for new repos #42

Closed
foolip opened this issue Oct 16, 2017 · 3 comments
Closed

Proposal: pick dashed-names instead of DashedNames for new repos #42

foolip opened this issue Oct 16, 2017 · 3 comments

Comments

@foolip
Copy link
Member

foolip commented Oct 16, 2017

In biblio.json there are 3 things using CamelCase:

Also WICG-originating, I think:

People don't seem to want to use the CamelCase names in web-platform-tests, see resize-observer, intersection-observer and service-workers: https://github.com/w3c/web-platform-tests

It would be less work for me matching up specs and tests in https://foolip.github.io/day-to-day/ if WICG repos tended to start out at dashed-names :)

@anssiko
Copy link
Member

anssiko commented Oct 16, 2017

Also W3C TR shortnames tend to be dashed-names, making for a better migration story if we stick with that convention for WICG repos too.

@marcoscaceres
Copy link
Contributor

Agree. We should do this going forward. I'll update the wiki.

@marcoscaceres
Copy link
Contributor

@cwilso, @yoavweiss ^^^ please note the new naming policy. I've added that check as part of the transfer process.

https://github.com/WICG/admin/wiki/Process-to-transfer-a-repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants