Update report.json, rec-track-repos.json, hr-repos.json

w3c-validate-repos-bot · w3c-validate-repos-bot · commit bc13befd0247 · 2025-11-25T00:29:49.000Z
diff --git a/report.json b/report.json
@@ -9845,7 +9845,7 @@
       }
     ]
   },
-  "timestamp": "2025-11-24T00:30:25.400Z",
+  "timestamp": "2025-11-25T00:29:48.847Z",
   "repos": [
     {
       "id": "MDEwOlJlcG9zaXRvcnk4MTAyMTg2MA==",
@@ -14250,8 +14250,8 @@
         "login": "immersive-web"
       },
       "isArchived": false,
-      "homepageUrl": "",
-      "description": "Additions to WebXR Device API for exposing real world data (Lead: Piotr Bialecki). Plane detection: https://immersive-web.github.io/real-world-geometry/plane-detection.html",
+      "homepageUrl": "https://immersive-web.github.io/plane-detection/",
+      "description": "Additions to WebXR Device API for exposing detected planes.",
       "isPrivate": false,
       "createdAt": "2019-04-08T17:16:59Z",
       "labels": [
@@ -14370,7 +14370,7 @@
         "text": " {\n    \"group\":      [87846]\n,   \"contacts\":   [\"dontcallmedom\",\"himorin\"]\n,   \"repo-type\":  \"cg-report\"\n}\n"
       },
       "prpreviewjson": {
-        "text": "{\n    \"src_file\": \"plane-detection.bs\",\n    \"type\": \"bikeshed\",\n    \"params\": {\n        \"force\": 1\n    }\n}\n"
+        "text": "{\n    \"src_file\": \"index.bs\",\n    \"type\": \"bikeshed\",\n    \"params\": {\n        \"force\": 1\n    }\n}\n"
       },
       "autoPublish": null,
       "travis": null,
@@ -14387,7 +14387,7 @@
         "text": "# Real World Geometry\nFeature lead: Alex Cooper (@alcooper91)\n\nStatus: Incubation\n\n## Introduction\nThe goal of this feature incubation is to incubate APIs allowing access to real world geometry (abbreviated RWG) like planes and meshes.\n\nAreas explored may include real-world plane and mesh detection, the fine-grained configuration of APIs related to such real-world geometry, the use of and/or interaction of anchors with such real-world geometry, and exposing detailed information about confidence in and quality of such real-world geometry. These explorations may also include the use of such RWG, including using it for hit testing and for occlusion/depth information to allow more realistic rendering of virtual objects in real-world scenes.\n\nThe initial focus is on surfacing plane detection API(s). The idea is that in order for some Augmented Reality scenarios to work nicely, developers need to know about surfaces present in the user’s environment (for example to ensure that there is sufficient space to place a virtual object in user’s environment). After surfacing a rudimentary API for plane detection to JavaScript, we will explore the use of the API and RWG, what’s possible in user space, and whether other APIs are necessary.\n\nIn addition to just exposing additional functionality, we should also consider allowing app developers to configure it. Example configuration options may include filtering for which types of planes are detected (e.g. only horizontal or vertical planes).\n\nMoreover, it could be beneficial to application developer to be able to retrieve information about the confidence / quality of data returned by RWG APIs.\n\n## Privacy considerations\nOne of the concerns with exposing real-world understanding information to web applications is the risk that the information will be abused. In order to mitigate that, the User Agent will have to ensure that the user gave the website consent to access RWG data. These topics are explored in the [privacy and security explainer](https://github.com/immersive-web/privacy-and-security/blob/master/EXPLAINER.md#accessing-real-world-data). Proposals in this repo will include mitigations from that repo that are relevant for the covered APIs.\n"
       },
       "prpreview": {
-        "src_file": "plane-detection.bs",
+        "src_file": "index.bs",
         "type": "bikeshed",
         "params": {
           "force": 1
@@ -57256,6 +57256,14 @@
           "name": "Tests: Unneeded",
           "color": "FEF2C0"
         },
+        {
+          "name": "Topic: Ruby Markup spec",
+          "color": "54bbb6"
+        },
+        {
+          "name": "Topic: Ruby TTS explainer",
+          "color": "54bbb6"
+        },
         {
           "name": "Type: Corrections and Improvements",
           "color": "C5DEF5"
@@ -129901,7 +129909,7 @@
         "body": "# Code of Conduct\n\nAll documentation, code and communication under this repository are covered by the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/).\n"
       },
       "readme": {
-        "text": "# W3C website template bundle & Design System\n\nThe Symfony website templates for [w3.org](https://github.com/w3c/w3c-website-frontend). This also generates the\nstatic HTML [design system website](https://design-system.w3.org/).\n\n## Design System\n\nThis repo contains the design system documentation, frontend assets and example Twig templates. \n\nDocumentation for implementing the W3C website design can be found on the [Design System website](https://design-system.w3.org/).\n\nFor documentation on how to make updates to the design system itself see [design system README](design-system.md).\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Template bundle\n\nThis repo also contains a Symfony bundle which loads the frontend assets and has a set of Twig templates available \nto build Symfony apps using the W3C website design system.\n\n### How to use the design system templates in Symfony\n\nThe design system contains [example Twig templates](design-system-templates) that cover all design patterns used\non the W3C website. These are simplified templates to help illustrate usage. \n\nTo actually use the design system Twig templates, you need to copy these to the [Symfony bundle templates](templates) \nand customise them for use in your application. At present we're building the \n[W3C frontend application](https://github.com/w3c/w3c-website-frontend) which will power \nw3.org. As we build pages we are copying the design system templates across to the bundle templates \nand modifying them for real-world usage. \n\nLong-term the plan is to be able to use the Symfony bundle templates in a range of different \nSymfony applications - though some refactoring may need to be done to ensure the templates work easily \nacross different applications.\n\n### Installation\n\nYou can install this in your Symfony app via:\n\n```bash\ncomposer require w3c/website-templates-bundle:dev-main\n```\n\nThis requires PHP 7.4+\n\nOn installation, front-end assets (CSS, JavaScript, fonts, etc.) will be copied into the public directory of the application.\nYou will find them in the folder `public/bundles/w3cwebsitetemplates/dist/assets`.\nYou will need to update the assets base URL to point to that folder. This can be done in your application `config/packages/assets.yaml` file for example.\n\nExample syntax (provided you have defined an `%app.app_url%` parameter):\n\n```yaml\nframework:\n    assets:\n        packages:\n            main:\n                base_urls: '%app.app_url%/bundles/w3cwebsitetemplates/dist/assets/'\n```\nYou can now use the W3C Twig templates and front-end assets in your application.\n\n### Usage\n\nThe templates available can be found in this bundle's 'templates' folder. You can reference them in your application using the\nhandle `@W3CWebsiteTemplates`. E.g.\n\n```twig\n{% extends '@W3CWebsiteTemplates/base.html.twig' %}\n```\n\n### Overriding the templates\n\nTemplates can be overridden in the `templates/bundles/w3cwebsitetemplates/` directory in your \nSymfony project, using the same name and path as the original templates.\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n"
+        "text": "# W3C website template bundle & Design System\n\nThe Symfony website templates for [w3.org](https://github.com/w3c/w3c-website-frontend). This also generates the\nstatic HTML [design system website](https://design-system.w3.org/).\n\n## Design System\n\nThis repo contains the design system documentation, frontend assets and example Twig templates. \n\nDocumentation for implementing the W3C website design can be found on the [Design System website](https://design-system.w3.org/).\n\nFor documentation on how to make updates to the design system itself see [design system README](design-system.md).\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n\n## Template bundle\n\nThis repo also contains a Symfony bundle which loads the frontend assets and has a set of Twig templates available \nto build Symfony apps using the W3C website design system.\n\n### How to use the design system templates in Symfony\n\nThe design system contains [example Twig templates](design-system-templates) that cover all design patterns used\non the W3C website. These are simplified templates to help illustrate usage. \n\nTo actually use the design system Twig templates, you need to copy these to the [Symfony bundle templates](templates) \nand customise them for use in your application. At present we're building the \n[W3C frontend application](https://github.com/w3c/w3c-website-frontend) which will power \nw3.org. As we build pages we are copying the design system templates across to the bundle templates \nand modifying them for real-world usage. \n\nLong-term the plan is to be able to use the Symfony bundle templates in a range of different \nSymfony applications - though some refactoring may need to be done to ensure the templates work easily \nacross different applications.\n\n### Installation\n\nYou can install this in your Symfony app via:\n\n```bash\ncomposer require w3c/website-templates-bundle:dev-main\n```\n\nThis requires PHP 7.4+\n\nOn installation, front-end assets (CSS, JavaScript, fonts, etc.) will be copied into the public directory of the application.\nYou will find them in the folder `public/bundles/w3cwebsitetemplates/dist/assets`.\nYou will need to update the assets base URL to point to that folder. This can be done in your application `config/packages/assets.yaml` file for example.\n\nExample syntax (provided you have defined an `%app.app_url%` parameter):\n\n```yaml\nframework:\n    assets:\n        packages:\n            main:\n                base_urls: '%app.app_url%/bundles/w3cwebsitetemplates/dist/assets/'\n```\nYou can now use the W3C Twig templates and front-end assets in your application.\n\n### Usage\n\nThe templates available can be found in this bundle's 'templates' folder. You can reference them in your application using the\nhandle `@W3CWebsiteTemplates`. E.g.\n\n```twig\n{% extends '@W3CWebsiteTemplates/base.html.twig' %}\n```\n\n\n### Note on development deployments\n\nIf you're testing work to the development server, please ensure that you have merged your work into the `development` branch first. This is because the frontend codebase on the development server will reference the development branch when it includes this repo in composer.\n\n### Overriding the templates\n\nTemplates can be overridden in the `templates/bundles/w3cwebsitetemplates/` directory in your \nSymfony project, using the same name and path as the original templates.\n\n## Reporting issues\n\nPlease report any issues to the [w3c-website](https://github.com/w3c/w3c-website/issues) repo.\n"
       },
       "w3c": {
         "group": [
@@ -169295,7 +169303,7 @@
         "text": "{\n    \"src_file\": \"index.html\",\n    \"type\": \"respec\"\n}\n"
       },
       "autoPublish": {
-        "text": "name: CI\non:\n  pull_request: {}\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v5\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: everything\n"
+        "text": "name: CI\non:\n  pull_request: {}\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v6\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: everything\n"
       },
       "travis": null,
       "contributing": null,
@@ -182280,7 +182288,7 @@
         "text": "{\n  \"src_file\": \"index.bs\",\n  \"type\": \"bikeshed\",\n  \"params\": {\n    \"force\": 1\n  }\n}\n\n"
       },
       "autoPublish": {
-        "text": "name: CI\non:\n  pull_request: {}\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v5\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: warning\n"
+        "text": "name: CI\non:\n  pull_request: {}\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v6\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: warning\n"
       },
       "travis": null,
       "contributing": {
@@ -183830,7 +183838,7 @@
         "text": "{\n  \"src_file\": \"index.bs\",\n  \"type\": \"bikeshed\",\n  \"params\": {\n    \"force\": 1\n  }\n}\n\n"
       },
       "autoPublish": {
-        "text": "name: CI\non:\n  pull_request:\n    branches: [main]\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v5\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: warning\n"
+        "text": "name: CI\non:\n  pull_request:\n    branches: [main]\n  push:\n    branches: [main]\njobs:\n  main:\n    name: Build, Validate and Deploy\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n    steps:\n      - uses: actions/checkout@v6\n      - uses: w3c/spec-prod@v2\n        with:\n          GH_PAGES_BRANCH: gh-pages\n          BUILD_FAIL_ON: warning\n"
       },
       "travis": null,
       "contributing": {
