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

chore: transfer repository to speced org #4713

Closed
hober opened this issue May 17, 2024 · 4 comments · Fixed by #4723
Closed

chore: transfer repository to speced org #4713

hober opened this issue May 17, 2024 · 4 comments · Fixed by #4723

Comments

@hober
Copy link

hober commented May 17, 2024

No description provided.

@hober hober added the bug label May 17, 2024
@marcoscaceres marcoscaceres removed the bug label May 20, 2024
@marcoscaceres
Copy link
Contributor

I think it should be fine... it was our intention to do this a few years ago. I don't expect anything will break.

@sidvishnoi any concerns?

@sidvishnoi
Copy link
Member

Things that might break:

  1. W3C ReSpec scripts hosting. cc @deniak - will need to update on their end.
  2. There are some references to w3c.github.io/respec. I'm not sure if they'll redirect fine. Specs using builds from w3c.github.io/respec might break. None in W3C, but other profiles do use it. See DINI, OCFL - they should use some CDN from npm though. @marcoscaceres IDK why we even add builds to repo, when things can be downloaded from npm.
  3. References to repo directly should redirect fine. We'll update references where to can do avoid redirects.

So, I think we can start the migration as soon as we all have some to handle any fallout.

@sidvishnoi sidvishnoi changed the title repo organization nit: it'd be nice if this were moved to speced chore: transfer repository to speced org May 22, 2024
@sidvishnoi
Copy link
Member

Also TODO: move respec-web-services repo there, and update any references.

@sidvishnoi
Copy link
Member

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

Successfully merging a pull request may close this issue.

3 participants