RawGit is shutting down, replace it with jsDelivr

[jsdelivrbot]

RawGit is shutting down. This PR replaces all RawGit links with the recommended alternative - jsDelivr. jsDelivr is a free and fast open source CDN hosting all files from GitHub and npm.

This is an automated PR which is meant to make the migration process as easy as possible. If something doesn't look right or you have any questions, feel free to ping MartinKolarik or jimaek in this PR. You may also use our online migration tool to convert other RawGit links to jsDelivr links.

[davidlehn]

I think we should delay merging this for a while as it effects many projects. Hopefully people will confirm these changes work for their use cases. At some point before rawgit closes we'll merge whatever remains to be fixed.

[OR13]

This PR is ancient and should be closed.

[OR13]

This PR should be closed.

[OR13]

cc @davidlehn @dlongley

[stain]

I don't think it should be closed but merged - several of the links this fixes are now broken because rawgit has shut down - for instance https://cdn.rawgit.com/dini-ag-kim/movingwall/gh-pages/movingwall.owl no longer works but we know it works with jsdelivr. (Bad example as that has already been fixed!)

[davidlehn]

I'd prefer maintainers fix their own things as is appropriate for their project. I'm fine leaving issues like this open until that happens. Probably should re-ping owners of broken links every so often though.

[dgarijo]

+1 to closing. Plus, the branch now has conflicts.

[davidlehn]

@dgarijo This PR does have issues, but the problem remains. rawgit still hasn't really shut down and some of the patches here could still be applied. I had hope maintainers would update their own redirects because I don't want to do that for them. If anyone has time, perhaps it would help to refresh the related issues with the current problem files and tagging their maintainers.

[ThisIsMissEm]

@davidlehn @dgarijo one thing that could be done on this repo is adding a CODEOWNERS file, and then all the teams responsible for their areas would be tagged in PRs like this, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

[davidlehn]

@ThisIsMissEm The idea is fine, but in practice, some problems:

• File can only be 3MB, I imagine adding all w3id redirects to that will exceed that limit at some point.
• It's another thing to maintain, which we want to minimize.
• The people related to this issue were tagged in another issue and ignored it. I suspect people would just ignore CODEOWNERS requests too.

I imagine if/when redirects break and someone is still using them, they'll file PRs or issues to get it resolved. So problems will resolve themselves, just sometimes with more panic than was needed.