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

w3c · Oct 27, 2024 · 22d0405 · 22d0405
1 parent 2f7c46b
commit 22d0405
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/report.json b/report.json
@@ -9888,7 +9888,7 @@
       }
     ]
   },
-  "timestamp": "2024-10-26T00:22:18.846Z",
+  "timestamp": "2024-10-27T00:22:47.210Z",
   "repos": [
     {
       "id": "MDEwOlJlcG9zaXRvcnk4MTAyMTg2MA==",
@@ -65655,6 +65655,10 @@
         {
           "name": "tag-tracker",
           "color": "7fff00"
+        },
+        {
+          "name": "voting",
+          "color": "3436FB"
         }
       ],
       "defaultBranch": {
@@ -153693,7 +153697,7 @@
         "body": "# Code of Conduct\n\nAll documentation, code, communication and discussion in this repository are covered by the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/).\n"
       },
       "readme": {
-        "text": "# Web Privacy Principles Task Force\n\n## Table of Contents\n\n<!-- START doctoc generated TOC please keep comment here to allow auto update -->\n<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->\n\n- [Charter](#charter)\n- [Privacy Task Force Members](#privacy-task-force-members)\n- [Input documents](#input-documents)\n- [Related documents](#related-documents)\n\n<!-- END doctoc generated TOC please keep comment here to allow auto update -->\n\n## Charter\n\nThe purpose of the Privacy Model Task Force is to bring together a small group of people to draft a set of privacy principles for the web.  This document is to include definitions of key privacy concepts on the web, enabling us to use common language as we work together on new web technologies that have an impact on user privacy.  It would also consolidate some of the work already done to define a privacy threat model.\n\nThis effort will look at privacy from a **web architecture** point of view, fitting together with the TAG's Ethical Principles, Design Principles, and the Privacy & Security Questionnaire jointly worked on between TAG and PING.\n\nThis effort will operate as a TAG-sponsored task force together with the Privacy Interest Group with participants invited by the TAG chairs and the PING chairs (which can include current or former members of each group).  There will be a maximum of 10 participants in the task force. The task force will run for 6 months and the final product will be a report which can be published as a TAG Finding (which can be subsequently elevated to a W3C statement) with some additional acknowledgement that the document has been produced jointly between PING and TAG.\n\nWe will be building on the work of the Ethical Web Principles which lays down an ethical framework for the web.  The goal of a privacy model for the web should be aligned with the goal of that document: to ensure that the web provides **a net positive social benefit to humanity**.\n\nPeriodically, and before working drafts are published, the task force will check in with an oversight group consisting of the TAG and PING chairs and team contacts for approval and comment.\n\nThis effort will happen in a public repo and with public comments.\n\nWe will be staying away from legal and regulatory material.\n\nThis effort will operate under the W3C's CEPC and as such we will maintain a respectful discourse. This effort will operate under anti-trust guidance from W3C.\n\nPossible names : Architectural Principles for Web Privacy; Architectural Considerations for Web Privacy; Privacy Architecture for the Web (PAW).\n\nWe will strike a balance between working on the web as it is and also not being constrained by existing approaches if those approaches contravene privacy principles.\n\ne.g.\n> As a target threat model, it describes not the current state of the Web including all current maybe-unwise APIs, but rather an end state that we hope to migrate to, and that new APIs should be held to. This is meant to be a plausible threat model: it doesn’t expect to remove any APIs or browser behavior that is deemed essential to the viability of the Web.\n\n## Privacy Task Force Members\n\n* Daniel Appelquist (Invited Expert, TAG, formerly Samsung)\n* Robin Berjon (Invited Expert, formerly The New York Times, TAG alum)\n* Nick Doty (Center for Democracy & Technology, PING)\n* Amy Guy (Digital Bazaar, TAG)\n* Don Marti (CafeMedia, PING)\n* Jonathan Kingston (DuckDuckGo)\n* Theresa O'Connor (Apple, TAG, PrivacyCG)\n* Christine Runnegar (W3C Invited Expert, PING)\n* Wendy Seltzer (Invited Expert)\n* Pete Snyder (Brave, PING)\n* Sam Weiler (W3C)\n* Jeffrey Yasskin (Google, PING)\n\n…with support from W3C Team.\n\nConstituencies we want to represent\n\n* Browsers\n* Publishers / Web Sites\n* Civil society\n* Adtech intermediaries\n* Advertising buyers\n* People fighting abuse and fraud\n* Web developers\n* Members of marginalized communities who use the web\n* Other people who use the web\n\nExperts we need input and review from:\n* Privacy advocates\n* Privacy theorists and legal scholars\n* Behavioral economists\n* Those working on emerging Web tech such as WebXR and new device APIs\n* User researchers\n* TAG and PING chairs and team contacts\n* WhatWG steering board\n\n## Input documents\n\n* https://w3cping.github.io/privacy-threat-model/\n* https://darobin.github.io/pup/\n\n## Related documents\n\n* https://w3ctag.github.io/ethical-web-principles/\n* https://w3ctag.github.io/design-principles/\n* https://w3ctag.github.io/security-questionnaire/\n* Definition of origin: https://html.spec.whatwg.org/multipage/origin.html#origin\n* https://www.w3.org/Consortium/cepc/\n* https://datatracker.ietf.org/doc/html/rfc6973\n"
+        "text": "# Web Privacy Principles Task Force\n\n## Table of Contents\n\n<!-- START doctoc generated TOC please keep comment here to allow auto update -->\n<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->\n\n- [Charter](#charter)\n- [Privacy Task Force Members](#privacy-task-force-members)\n- [Input documents](#input-documents)\n- [Related documents](#related-documents)\n\n<!-- END doctoc generated TOC please keep comment here to allow auto update -->\n\n## Charter\n\nThe purpose of the Privacy Model Task Force is to bring together a small group of people to draft a set of privacy principles for the web.  This document is to include definitions of key privacy concepts on the web, enabling us to use common language as we work together on new web technologies that have an impact on user privacy.  It would also consolidate some of the work already done to define a privacy threat model.\n\nThis effort will look at privacy from a **web architecture** point of view, fitting together with the TAG's Ethical Principles, Design Principles, and the Privacy & Security Questionnaire jointly worked on between TAG and PrivacyWG (and previously, PING).\n\nThis effort will operate as a TAG-sponsored task force together with the Privacy Interest Group with participants invited by the TAG chairs and the PrivacyWG chairs (which can include current or former members of each group).  There will be a maximum of 10 participants in the task force. The task force will run for 6 months and the final product will be a report which can be published as a TAG Finding (which can be subsequently elevated to a W3C statement) with some additional acknowledgement that the document has been produced jointly between PrivacyWG and TAG.\n\nWe will be building on the work of the Ethical Web Principles which lays down an ethical framework for the web.  The goal of a privacy model for the web should be aligned with the goal of that document: to ensure that the web provides **a net positive social benefit to humanity**.\n\nPeriodically, and before working drafts are published, the task force will check in with an oversight group consisting of the TAG and PrivacyWG chairs and team contacts for approval and comment.\n\nThis effort will happen in a public repo and with public comments.\n\nWe will be staying away from legal and regulatory material.\n\nThis effort will operate under the W3C's CEPC and as such we will maintain a respectful discourse. This effort will operate under anti-trust guidance from W3C.\n\nPossible names : Architectural Principles for Web Privacy; Architectural Considerations for Web Privacy; Privacy Architecture for the Web (PAW).\n\nWe will strike a balance between working on the web as it is and also not being constrained by existing approaches if those approaches contravene privacy principles.\n\ne.g.\n> As a target threat model, it describes not the current state of the Web including all current maybe-unwise APIs, but rather an end state that we hope to migrate to, and that new APIs should be held to. This is meant to be a plausible threat model: it doesn’t expect to remove any APIs or browser behavior that is deemed essential to the viability of the Web.\n\n## Privacy Task Force Members\n\n* Daniel Appelquist (Invited Expert, TAG, formerly Samsung)\n* Robin Berjon (Invited Expert, formerly The New York Times, TAG alum)\n* Nick Doty (Center for Democracy & Technology, PrivacyWG)\n* Amy Guy (Digital Bazaar, TAG)\n* Don Marti (CafeMedia, PrivacyWG)\n* Jonathan Kingston (DuckDuckGo)\n* Theresa O'Connor (Apple, TAG, PrivacyCG)\n* Christine Runnegar (W3C Invited Expert, PrivacyWG)\n* Wendy Seltzer (Invited Expert)\n* Pete Snyder (Brave, PrivacyWG)\n* Sam Weiler (W3C)\n* Jeffrey Yasskin (Google, PrivacyWG)\n\n…with support from W3C Team.\n\nConstituencies we want to represent\n\n* Browsers\n* Publishers / Web Sites\n* Civil society\n* Adtech intermediaries\n* Advertising buyers\n* People fighting abuse and fraud\n* Web developers\n* Members of marginalized communities who use the web\n* Other people who use the web\n\nExperts we need input and review from:\n* Privacy advocates\n* Privacy theorists and legal scholars\n* Behavioral economists\n* Those working on emerging Web tech such as WebXR and new device APIs\n* User researchers\n* TAG and PrivacyWG chairs and team contacts\n* WhatWG steering board\n\n## Input documents\n\n* https://w3cping.github.io/privacy-threat-model/\n* https://darobin.github.io/pup/\n\n## Related documents\n\n* https://w3ctag.github.io/ethical-web-principles/\n* https://w3ctag.github.io/design-principles/\n* https://w3ctag.github.io/security-questionnaire/\n* Definition of origin: https://html.spec.whatwg.org/multipage/origin.html#origin\n* https://www.w3.org/Consortium/cepc/\n* https://datatracker.ietf.org/doc/html/rfc6973\n"
       },
       "prpreview": {
         "src_file": "index.html",
@@ -164033,7 +164037,7 @@
         "body": "Please find the code of conduct at https://github.com/WebAssembly/meetings/blob/main/CODE_OF_CONDUCT.md.\n"
       },
       "readme": {
-        "text": "# Wide Arithmetic proposal for WebAssembly.\n\nThis repository is a clone of\n[`WebAssembly/spec`](https://github.com/WebAssembly/spec/). It is meant for\ndiscussion, prototype specification, and implementation of a proposal to add\nsupport for wide arithmetic instructions for WebAssembly.\n\n* See the [overview](./proposals/wide-arithmetic/Overview.md) for a\n  high-level summary and rationale of the proposal.\n\nOriginal README from upstream repository follows...\n\n--------------------------------------------------------------------------------\n\n[![CI for specs](https://github.com/WebAssembly/spec/actions/workflows/ci-spec.yml/badge.svg)](https://github.com/WebAssembly/spec/actions/workflows/ci-spec.yml)\n[![CI for interpreter & tests](https://github.com/WebAssembly/spec/actions/workflows/ci-interpreter.yml/badge.svg)](https://github.com/WebAssembly/spec/actions/workflows/ci-interpreter.yml)\n\n# spec\n\nThis repository holds the sources for the WebAssembly draft specification\n(to seed a future\n[WebAssembly Working Group](https://lists.w3.org/Archives/Public/public-new-work/2017Jun/0005.html)),\na reference implementation, and the official testsuite.\n\nA formatted version of the spec is available here:\n[webassembly.github.io/spec](https://webassembly.github.io/spec/),\n\nParticipation is welcome. Discussions about new features, significant semantic\nchanges, or any specification change likely to generate substantial discussion\nshould take place in\n[the WebAssembly design repository](https://github.com/WebAssembly/design)\nfirst, so that this spec repository can remain focused. And please follow the\n[guidelines for contributing](Contributing.md).\n\n# citing\n\nFor citing WebAssembly in LaTeX, use [this bibtex file](wasm-specs.bib).\n"
+        "text": "# Wide Arithmetic proposal for WebAssembly.\n\nThis repository is a clone of\n[`WebAssembly/spec`](https://github.com/WebAssembly/spec/). It is meant for\ndiscussion, prototype specification, and implementation of a proposal to add\nsupport for wide arithmetic instructions for WebAssembly.\n\n* See the [overview](./proposals/wide-arithmetic/Overview.md) for a\n  high-level summary and rationale of the proposal.\n\n* See the [modified spec](https://webassembly.github.io/wide-arithmetic/core/)\n  for the formalization of this proposal. Notably...\n  * [new abstract syntax](https://webassembly.github.io/wide-arithmetic/core/syntax/instructions.html#numeric-instructions)\n  * [new binary opcodes (scroll down)](https://webassembly.github.io/wide-arithmetic/core/binary/instructions.html#numeric-instructions)\n  * [new text opcodes (scroll down)](https://webassembly.github.io/wide-arithmetic/core/text/instructions.html#numeric-instructions)\n  * [new validation](https://webassembly.github.io/wide-arithmetic/core/valid/instructions.html#xref-syntax-types-syntax-valtype-mathsf-i64-mathsf-xref-syntax-instructions-syntax-binop-mathit-binop-mathsf-128)\n  * [new execution](https://webassembly.github.io/wide-arithmetic/core/exec/instructions.html#xref-syntax-types-syntax-valtype-mathsf-i64-mathsf-xref-syntax-instructions-syntax-binop-mathit-binop-mathsf-128)\n  * [new helper functions](https://webassembly.github.io/wide-arithmetic/core/exec/numerics.html#xref-exec-numerics-op-iconcat-mathrm-iconcat-m-n-i-1-i-2)\n\nOriginal README from upstream repository follows...\n\n--------------------------------------------------------------------------------\n\n[![CI for specs](https://github.com/WebAssembly/spec/actions/workflows/ci-spec.yml/badge.svg)](https://github.com/WebAssembly/spec/actions/workflows/ci-spec.yml)\n[![CI for interpreter & tests](https://github.com/WebAssembly/spec/actions/workflows/ci-interpreter.yml/badge.svg)](https://github.com/WebAssembly/spec/actions/workflows/ci-interpreter.yml)\n\n# spec\n\nThis repository holds the sources for the WebAssembly draft specification\n(to seed a future\n[WebAssembly Working Group](https://lists.w3.org/Archives/Public/public-new-work/2017Jun/0005.html)),\na reference implementation, and the official testsuite.\n\nA formatted version of the spec is available here:\n[webassembly.github.io/spec](https://webassembly.github.io/spec/),\n\nParticipation is welcome. Discussions about new features, significant semantic\nchanges, or any specification change likely to generate substantial discussion\nshould take place in\n[the WebAssembly design repository](https://github.com/WebAssembly/design)\nfirst, so that this spec repository can remain focused. And please follow the\n[guidelines for contributing](Contributing.md).\n\n# citing\n\nFor citing WebAssembly in LaTeX, use [this bibtex file](wasm-specs.bib).\n"
       },
       "w3c": {
         "group": [