update links to repository after moving it to quic-interop org

quic-interop · Oct 25, 2023 · fd065ac · fd065ac
1 parent f2cdb1d
commit fd065ac
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -30,7 +30,7 @@ To enable IPv6 support for the simulator on Linux, the `ip6table_filter` kernel
 
 ## Building a QUIC endpoint
 
-To include your QUIC implementation in the Interop Runner, create a Docker image following the instructions for [setting up an endpoint in the quic-network-simulator](https://github.com/marten-seemann/quic-network-simulator), publish it on [Docker Hub](https://hub.docker.com) and add it to [implementations.json](implementations.json). Once your implementation is ready to interop, please send us a PR with this addition. Read on for more instructions on what to do within the Docker image.
+To include your QUIC implementation in the Interop Runner, create a Docker image following the instructions for [setting up an endpoint in the quic-network-simulator](https://github.com/quic-interop/quic-network-simulator), publish it on [Docker Hub](https://hub.docker.com) and add it to [implementations.json](implementations.json). Once your implementation is ready to interop, please send us a PR with this addition. Read on for more instructions on what to do within the Docker image.
 
 Typically, a test case will require a server to serve files from a directory, and a client to download files. Different test cases will specify the behavior to be tested. For example, the Retry test case expects the server to use a Retry before accepting the connection from the client. All configuration information from the test framework to your implementation is fed into the Docker image using environment variables. The test case is passed into your Docker container using the `TESTCASE` environment variable. If your implementation doesn't support a test case, it MUST exit with status code 127. This will allow us to add new test cases in the future, and correctly report test failures und successes, even if some implementations have not yet implented support for this new test case.
 

diff --git a/implementations.json b/implementations.json
@@ -51,7 +51,7 @@
   },
   "chrome": {
     "image": "martenseemann/chrome-quic-interop-runner",
-    "url": "https://github.com/marten-seemann/chrome-quic-interop-runner",
+    "url": "https://github.com/quic-interop/chrome-quic-interop-runner",
     "role": "client"
   },
   "xquic": {

diff --git a/trace.py b/trace.py
@@ -105,7 +105,7 @@ def _get_packets(self, f: str) -> List:
             self._filename,
             display_filter=f,
             override_prefs=override_prefs,
-            disable_protocol="http3",  # see https://github.com/marten-seemann/quic-interop-runner/pull/179/
+            disable_protocol="http3",  # see https://github.com/quic-interop/quic-interop-runner/pull/179
             decode_as={"udp.port==443": "quic"},
         )
         packets = []

diff --git a/web/index.html b/web/index.html
@@ -10,10 +10,10 @@
   <link rel="stylesheet" href="styles.css">
 </head>
 <body>
-  <a class="github-fork-ribbon" href="https://github.com/marten-seemann/quic-interop-runner" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
+  <a class="github-fork-ribbon" href="https://github.com/quic-interop/quic-interop-runner" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
 
   <nav class="navbar navbar-expand-lg navbar-light bg-light">
-    <a href="https://github.com/marten-seemann/quic-interop-runner">
+    <a href="https://github.com/quic-interop/quic-interop-runner">
       <span class="navbar-brand">
         <img src="https://github.com/quicwg/wg-materials/raw/main/badge/transparent/QUIC-Badge-Dark-RGB-Horiz.svg" height="45" class="d-inline-block align-middle" alt="QUIC" loading="lazy">
         Interop Runner
@@ -56,7 +56,7 @@ <h3 class="mt-5">About</h3>
     </p>
 
     <p>
-      It is straightforward to add <strong>your implementation</strong> to this automated testing effort; please <a href="https://github.com/marten-seemann/quic-interop-runner/blob/master/README.md#building-a-quic-endpoint">see these simple instructions</a>.
+      It is straightforward to add <strong>your implementation</strong> to this automated testing effort; please <a href="https://github.com/quic-interop/quic-interop-runner/blob/master/README.md#building-a-quic-endpoint">see these simple instructions</a>.
     </p>
 
     <h3 class="mt-5">Results Filter</h3>