chore: Update URLs after moving projects (#4008)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -18,7 +18,7 @@ assignees: ''
 **Can you reproduce the issue with our latest release version?**
 
 
-**Can you reproduce the issue with the latest code from `master`?**
+**Can you reproduce the issue with the latest code from `main`?**
 
 
 **Are you using the demo app or your own custom app?**

.github/workflows/build-and-test.yaml

@@ -4,7 +4,7 @@ on:
   pull_request: # Trigger for pull requests.
     types: [opened, synchronize, reopened]
     branches:
-      - master
+      - main
       - v[0-9]*
   workflow_dispatch: # Allows for manual triggering.
     inputs:

.github/workflows/release-please.yaml

@@ -3,7 +3,7 @@ name: Release
 on:
   push:
     branches:
-      - master
+      - main
       - v[0-9]*
 
 jobs:
@@ -20,7 +20,7 @@ jobs:
         id: release
         with:
           # Without this command, the manifest file will be ignored.  At least
-          # for our initial master-branch releases using this workflow, we must
+          # for our initial main-branch releases using this workflow, we must
           # use the manifest and config file.
           command: manifest
           config-file: .release-please-config.json
@@ -55,20 +55,20 @@ jobs:
   # The jobs below are all conditional on a release having been created by
   # someone merging the release PR.  They all run in parallel.
 
-  tag-master:
+  tag-main:
     runs-on: ubuntu-latest
     needs: release
     if: ${{ needs.release.outputs.release_created }}
     steps:
       - uses: actions/checkout@v2
-      - name: Tag the master branch
+      - name: Tag the main branch
         run: |
           # Emulate the actions bot.
           git config user.email "github-actions[bot]"
           git config user.name "41898282+github-actions[bot]@users.noreply.github.com"
           VERSION=${{ needs.release.outputs.tag_name }}
-          git tag -m "$VERSION-master" "$VERSION-master"
-          git push origin "$VERSION-master"
+          git tag -m "$VERSION-main" "$VERSION-main"
+          git push origin "$VERSION-main"
 
   npm:
     runs-on: ubuntu-latest

CONTRIBUTING.md

@@ -3,8 +3,8 @@
 We'd love to accept your patches and contributions to this project.  There are
 just a few small guidelines you need to follow.
 
-1. File a bug at https://github.com/google/shaka-player/issues (if there isn't
-   one already).  If your patch is going to be large, you should start a
+1. File a bug at https://github.com/shaka-project/shaka-player/issues (if there
+   isn't one already).  If your patch is going to be large, you should start a
    discussion on GitHub first.
 
    Leave a comment to let us know that you are working on a PR for the issue.

README.md

@@ -52,7 +52,7 @@ NOTES:
  - ⁶: These are expected to work, but are community-supported and untested by
    us.
      - Official support for LG WebOS TV:
-       https://github.com/google/shaka-player/issues/1330
+       https://github.com/shaka-project/shaka-player/issues/1330
 
 We support iOS 12+ through Apple's native HLS player.  We provide the same
 top-level API, but we just set the video's `src` element to the manifest/media.
@@ -65,7 +65,7 @@ features and similar APIs for native apps on iOS. This project uses its own
 media stack, which allows it to play content that would otherwise not be
 supported. This supports both DASH and HLS manifests.
 
-[Shaka Player Embedded]: https://github.com/google/shaka-player-embedded
+[Shaka Player Embedded]: https://github.com/shaka-project/shaka-player-embedded
 
 
 ## Manifest format support matrix
@@ -102,12 +102,12 @@ DASH features supported:
 DASH features **not** supported:
  - Xlink with actuate=onRequest
  - Manifests without any segment info:
-   https://github.com/google/shaka-player/issues/1088
+   https://github.com/shaka-project/shaka-player/issues/1088
  - Changing codecs during a presentation (unsupported by MSE)
  - Multiple trick mode tracks for the same resolution at varying framerates or
    bitrates
  - Timescales so large that timestamps cannot be represented as integers in
-   JavaScript (2^53): https://github.com/google/shaka-player/issues/1667
+   JavaScript (2^53): https://github.com/shaka-project/shaka-player/issues/1667
 
 
 ## HLS features
@@ -128,8 +128,8 @@ HLS features supported:
  - Raw AAC, MP3, etc (without an MP4 container)
 
 HLS features **not** supported:
- - Key rotation: https://github.com/google/shaka-player/issues/917
- - I-frame-only playlists: https://github.com/google/shaka-player/issues/742
+ - Key rotation: https://github.com/shaka-project/shaka-player/issues/917
+ - I-frame-only playlists: https://github.com/shaka-project/shaka-player/issues/742
  - Low-latency streaming with blocking playlist reload
 
 [mux.js]: https://github.com/videojs/mux.js/releases

build/README.md

@@ -99,7 +99,7 @@ will choose a defaults based on your platform.  However, if you pass any
 arguments to `test.py`, it will not choose browsers and you *must* pass
 `--browsers`.
 
-[lib/debug/log.js]: https://github.com/google/shaka-player/blob/master/lib/debug/log.js
+[lib/debug/log.js]: https://github.com/shaka-project/shaka-player/blob/main/lib/debug/log.js
 
 ## Stats
 

build/shakaBuildHelpers.py

@@ -348,7 +348,7 @@ def update_node_modules():
 
   # Update the modules.
   # Actually change directories instead of using npm --prefix.
-  # See npm/npm#17027 and google/shaka-player#776 for more details.
+  # See npm/npm#17027 and shaka-project/shaka-player#776 for more details.
   with InDir(base):
     # npm ci uses package-lock.json to get a stable, reproducible set of
     # packages installed.

build/wrapper.template.js

@@ -6,7 +6,7 @@
 
 (function() {
   // This is "window" in browsers and "global" in nodejs.
-  // See https://github.com/google/shaka-player/issues/1445
+  // See https://github.com/shaka-project/shaka-player/issues/1445
   var innerGlobal = typeof window != 'undefined' ? window : global;
 
   // This is where our library exports things to.  It is "this" in the wrapped
@@ -18,7 +18,7 @@
   // $jscomp.global, which will be "window", or "global", or "this", depending
   // on circumstances.
   // See https://github.com/google/closure-compiler/issues/2957 and
-  // https://github.com/google/shaka-player/issues/1455#issuecomment-393250035
+  // https://github.com/shaka-project/shaka-player/issues/1455#issuecomment-393250035
 
   // We provide "global" for use by Closure, and "window" for use by the Shaka
   // library itself.  Both point to "innerGlobal" above.

demo/customWarning.txt

@@ -4,5 +4,5 @@ of the asset you were playing at the time you pressed the bug report button.
 We have detected that you were playing a custom asset.
 If this asset's URL is confidential, you might instead want to fill out an issue
 template manually:
-https://github.com/google/shaka-player/issues/new/choose
--->
+https://github.com/shaka-project/shaka-player/issues/new/choose
+-->

demo/index.html

@@ -141,7 +141,7 @@ <h1 class="mdl-mega-footer__heading" localized-string="PROJECT_LINKS_HEADER"></h
               <ul class="mdl-mega-footer__link-list">
                 <li><a rel="noopener" target="_blank" href="../docs/api/index.html" localized-string="DOCUMENTATION"></a></li>
                 <li><a rel="noopener" target="_blank" href="https://www.apache.org/licenses/LICENSE-2.0" localized-string="LICENSE"></a></li>
-                <li><a rel="noopener" target="_blank" href="https://github.com/google/shaka-player" localized-string="SOURCE"></a></li>
+                <li><a rel="noopener" target="_blank" href="https://github.com/shaka-project/shaka-player" localized-string="SOURCE"></a></li>
                 <li><a rel="noopener" target="_blank" href="https://www.npmjs.com/package/shaka-player" localized-string="NPM"></a></li>
                 <li><a rel="noopener" target="_blank" href="../support.html" localized-string="SUPPORT"></a></li>
               </ul>

demo/main.js

@@ -164,7 +164,7 @@ shakaDemo.Main = class {
       case shaka.ui.Overlay.FailReasonCode.NO_BROWSER_SUPPORT:
         message = this.getLocalizedString(
             shakaDemo.MessageIds.FAILURE_NO_BROWSER_SUPPORT);
-        href = 'https://github.com/google/shaka-player#' +
+        href = 'https://github.com/shaka-project/shaka-player#' +
                 'platform-and-browser-support-matrix';
         break;
       case shaka.ui.Overlay.FailReasonCode.PLAYER_FAILED_TO_LOAD:
@@ -289,7 +289,7 @@ shakaDemo.Main = class {
 
     // Navigate to the github issue opening interface, with the
     // partially-filled template as a preset body.
-    let url = 'https://github.com/google/shaka-player/issues/new?';
+    let url = 'https://github.com/shaka-project/shaka-player/issues/new?';
     url += 'body=' + encodeURIComponent(text);
     // Open in another tab.
     window.open(url, '_blank');
@@ -1614,7 +1614,7 @@ shakaDemo.Main = class {
 
   /**
    * Sets the "version-string" divs to a version string.
-   * For example, "v2.5.4-master (uncompiled)".
+   * For example, "v2.5.4-main (uncompiled)".
    * @private
    */
   setUpVersionStrings_() {

docs/design/REDESIGN.md

@@ -28,11 +28,11 @@ often requiring [multiple][] [fixes][] to get certain dependencies removed.
 This means users all end up using the same monolithic player library.
 Features in Shaka 2 should be modular and easy to exclude from the build.
 
-[difficult]: https://github.com/google/shaka-player/commit/671611ef3722169b9f6b51ab44bdd6b4098d959e
-[to exclude]: https://github.com/google/shaka-player/commit/603fae969550c69ea38a61249da905857c67b9f1
-[from the build]: https://github.com/google/shaka-player/commit/f248647685b92ba928bbfd06d45d2b99023d60c2
-[multiple]: https://github.com/google/shaka-player/commit/39be45d3d55cdcef20a6a529a87246b0ea11cb33
-[fixes]: https://github.com/google/shaka-player/commit/6fe239150a8939728876e93e1a4269032530d9f1
+[difficult]: https://github.com/shaka-project/shaka-player/commit/671611ef3722169b9f6b51ab44bdd6b4098d959e
+[to exclude]: https://github.com/shaka-project/shaka-player/commit/603fae969550c69ea38a61249da905857c67b9f1
+[from the build]: https://github.com/shaka-project/shaka-player/commit/f248647685b92ba928bbfd06d45d2b99023d60c2
+[multiple]: https://github.com/shaka-project/shaka-player/commit/39be45d3d55cdcef20a6a529a87246b0ea11cb33
+[fixes]: https://github.com/shaka-project/shaka-player/commit/6fe239150a8939728876e93e1a4269032530d9f1
 
 Some operations, in particular [starting playback and filling the buffer][],
 take longer than they need to.  Startup and buffering in Shaka 2 should be as
@@ -46,54 +46,54 @@ us from updating MediaSource duration][] and makes it [difficult to set initial
 playback time][] on browsers other than Chrome.  Shaka 2 should have a simpler
 streaming core that works better across browsers.
 
-[StreamVideoSource]: https://github.com/google/shaka-player/blob/v1.5.x/lib/player/stream_video_source.js
-[Stream]: https://github.com/google/shaka-player/blob/v1.5.x/lib/media/stream.js
-[SourceBufferManager]: https://github.com/google/shaka-player/blob/v1.5.x/lib/media/source_buffer_manager.js
-[prevents us from updating MediaSource duration]: https://github.com/google/shaka-player/blob/v1.5.1/lib/player/stream_video_source.js#L1807
-[difficult to set initial playback time]: https://github.com/google/shaka-player/issues/101
+[StreamVideoSource]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/player/stream_video_source.js
+[Stream]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/media/stream.js
+[SourceBufferManager]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/media/source_buffer_manager.js
+[prevents us from updating MediaSource duration]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/player/stream_video_source.js#L1807
+[difficult to set initial playback time]: https://github.com/shaka-project/shaka-player/issues/101
 
 [Buffering state][] in Shaka 1 involves coordination between several layers
 (from [Player][] to [Stream][]) and has been [tough][] [to][] [get][]
 [right][].  Buffering state in Shaka 2 should be simple and consistent.
 
-[Buffering state]: https://github.com/google/shaka-player/blob/v1.5.1/lib/player/player.js#L994
-[Player]: https://github.com/google/shaka-player/blob/v1.5.x/lib/player/player.js
-[Stream]: https://github.com/google/shaka-player/blob/v1.5.x/lib/media/stream.js
-[tough]: https://github.com/google/shaka-player/issues/44
-[to]: https://github.com/google/shaka-player/issues/63
-[get]: https://github.com/google/shaka-player/issues/127
-[right]: https://github.com/google/shaka-player/issues/221#issuecomment-152781243
+[Buffering state]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/player/player.js#L994
+[Player]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/player/player.js
+[Stream]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/media/stream.js
+[tough]: https://github.com/shaka-project/shaka-player/issues/44
+[to]: https://github.com/shaka-project/shaka-player/issues/63
+[get]: https://github.com/shaka-project/shaka-player/issues/127
+[right]: https://github.com/shaka-project/shaka-player/issues/221#issuecomment-152781243
 
 Shaka 1 relies on the browser to implement support for text types, and is
 therefore limited to non-segmented WebVTT.  Shaka 2 should also support
 [segmented text types][] and [types not natively supported by the browser][].
 
-[segmented text types]: https://github.com/google/shaka-player/issues/150
-[types not natively supported by the browser]: https://github.com/google/shaka-player/issues/111
+[segmented text types]: https://github.com/shaka-project/shaka-player/issues/150
+[types not natively supported by the browser]: https://github.com/shaka-project/shaka-player/issues/111
 
 Bandwidth estimation in Shaka 1 relies on the assumption that segments are not
 cached locally.  Use of [cache-busting techniques][] to enforce this makes
 Shaka very [cache][]-[unfriendly][].  Shaka 2 should be cache-friendly.
 
-[cache-busting techniques]: https://github.com/google/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L241
-[cache]: https://github.com/google/shaka-player/issues/76
-[unfriendly]: https://github.com/google/shaka-player/issues/191
+[cache-busting techniques]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L241
+[cache]: https://github.com/shaka-project/shaka-player/issues/76
+[unfriendly]: https://github.com/shaka-project/shaka-player/issues/191
 
 Shaka 1 [uses HTTP headers to synchronize the user's clock][] with the server.
 This is [error-prone for some CDNs][] and also raises [CORS issues][], so Shaka
 2 should avoid using HTTP headers.
 
-[uses HTTP headers to synchronize the user's clock]: https://github.com/google/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L448
-[error-prone for some CDNs]: https://github.com/google/shaka-player/issues/205
-[CORS issues]: https://github.com/google/shaka-player/issues/159
+[uses HTTP headers to synchronize the user's clock]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L448
+[error-prone for some CDNs]: https://github.com/shaka-project/shaka-player/issues/205
+[CORS issues]: https://github.com/shaka-project/shaka-player/issues/159
 
 [HttpVideoSource][] does not build on MSE and classes like [EmeManager][] have
 special cases to support it.  Since it was originally created for debugging
 purposes, Shaka 2 should drop HttpVideoSource and only support MSE-based
 playback.
 
-[HttpVideoSource]: https://github.com/google/shaka-player/blob/v1.5.x/lib/player/http_video_source.js
-[EmeManager]: https://github.com/google/shaka-player/blob/v1.5.x/lib/media/eme_manager.js
+[HttpVideoSource]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/player/http_video_source.js
+[EmeManager]: https://github.com/shaka-project/shaka-player/blob/v1.5.x/lib/media/eme_manager.js
 
 Integration tests using externally-hosted resources [can be flaky][],
 especially when run outside of Google's network.  Shaka 2 should avoid tests
@@ -106,34 +106,34 @@ and application developers sometimes [have to use error message strings][]
 hard-coded into the library.  Shaka 2 should have a consistent error format
 that is easy to read.
 
-[have to use error message strings]: https://github.com/google/shaka-player/issues/201
+[have to use error message strings]: https://github.com/shaka-project/shaka-player/issues/201
 
 Networking abstractions in Shaka 1 are built inside of AjaxRequest, which
 requires non-HTTP requests to [pretend to come from XmlHttpRequest][].  The
 networking abstraction in Shaka 2 should be simpler and should not treat
 XHR as the basis for all networking.
 
-[pretend to come from XmlHttpRequest]: https://github.com/google/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L305
+[pretend to come from XmlHttpRequest]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/util/ajax_request.js#L305
 
 A developer who wishes to use a custom network protocol or a custom manifest
 format in Shaka 1 will have to modify the library to do so.  Shaka 2 should
 [support external plugins for networking][] and manifest support.
 
-[support external plugins for networking]: https://github.com/google/shaka-player/issues/198
+[support external plugins for networking]: https://github.com/shaka-project/shaka-player/issues/198
 
 The functionality that can be injected into Shaka 1 ([IBandwidthEstimator][],
 [IAbrManager][]) is based on implementing class interfaces, which can be complex
 for those unfamiliar with the Closure compiler.  Plugins and extensions to Shaka
 2 should be as simple as possible.
 
-[IBandwidthEstimator]: https://github.com/google/shaka-player/blob/v1.5.1/lib/util/i_bandwidth_estimator.js
-[IAbrManager]: https://github.com/google/shaka-player/blob/v1.5.1/lib/media/i_abr_manager.js
+[IBandwidthEstimator]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/util/i_bandwidth_estimator.js
+[IAbrManager]: https://github.com/shaka-project/shaka-player/blob/v1.5.1/lib/media/i_abr_manager.js
 
 [Static members][] in Shaka 1 make it impossible in some cases to host multiple
 Player instances with different settings.  Player instances should be completely
 independent in Shaka 1.
 
-[Static members]: https://github.com/google/shaka-player/issues/126
+[Static members]: https://github.com/shaka-project/shaka-player/issues/126
 
 
 ## Shaka v2 Design Principles

docs/design/bg-fetch.md

@@ -12,7 +12,7 @@ At the time it was added to the backlog, the feature was not quite ready for
 use. Since then, it has matured, and now is something we could feasibly use, but
 it has still been a low-priority feature.
 
-[since 2017]: https://github.com/google/shaka-player/issues/879
+[since 2017]: https://github.com/shaka-project/shaka-player/issues/879
 
 ## Design Concept
 
@@ -131,4 +131,4 @@ unrelated service worker for our own.
    1. This message can also be used to make sure the versions are the same.
 
 [the documentation]: https://developers.google.com/web/updates/2018/12/background-fetch#starting_a_background_fetch
-[a given scope]: https://developers.google.com/web/fundamentals/primers/service-workers#register_a_service_worker
+[a given scope]: https://developers.google.com/web/fundamentals/primers/service-workers#register_a_service_worker

docs/design/codec_preferences.md

@@ -97,7 +97,7 @@ A platform may support multiple DRM key systems, (for example, Widevine and
 PlayReady). The `drm.preferredKeySystems` configuration allows the application
 to specify which key systems it wants to choose.
 
-[Github issue](https://github.com/google/shaka-player/issues/3002)
+[Github issue](https://github.com/shaka-project/shaka-player/issues/3002)
 
 Previously, Shaka Player chose a DRM key system based on:
 1. Only use the key systems supported by the platform.