From 16810f2d946ddaf1737f874d6cfb3d9c101c21bf Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Thu, 6 Mar 2025 09:05:19 -0500 Subject: [PATCH 01/10] Create process.md Adding process explainer. --- process.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 process.md diff --git a/process.md b/process.md new file mode 100644 index 0000000..fd6c750 --- /dev/null +++ b/process.md @@ -0,0 +1,29 @@ +The PAT working group will use a process to similar to others that have employed a GitHub-centric mode of work. The process summary is as follows, and we should note that this is subject to change as we get closer to a final specification: + +* To access GitHub, you choose an interface, e.g., [command line interface](https://docs.github.com/en/github-cli), [GitHub mobile](https://docs.github.com/en/get-started/using-github/github-mobile), [GitHub desktop](https://docs.github.com/en/desktop), [VSCode](https://code.visualstudio.com/docs/sourcecontrol/github), or Browser. +* To start a discussion, you generate an [Issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). Most of the discussion happen on/in an Issue. +* To suggest a change, you generate a [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). “Discussions” about specific wording changes for a Pull Request occur on/in the PR. +* To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; PRs related to issues will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). +* To publish a new version of the specification, GitHub plus some [W3C Tooling](https://github.com/w3c/echidna?tab=readme-ov-file) takes care of this [within minutes](https://www.w3.org/2021/03/18-echidna/?full#1) of the PR being merged. +* To track what has happen, you can consult the GitHub logs; Github logs everything - all issues, discussions about issues, labels, label changes, and specification changes, etc. +* To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email, the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). + +What follows is a more detail explanation of the process. + +Not all Issues are created equal. Some Issues are editorial; some are noncontroversial, non-editorial; and some are controversial. More process is required for controversial Issues than for noncontroversial Issues. + +While nobody wants their Issue to be controversial and most do not start out that way, it happens and when it does the chairs get involved to (if necessary) mediate the discussion and to (chair only function) judge consensus on the way forward. We will use [Labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels), `discuss`, `needs consensus`, `call-for-consensus`, and `has consensus`, to move through the process. `discuss` is notice that the Issue needs to be discussed; can be applied by anyone. `needs consensus` is a request for the chairs step in; can be applied by anyone. `call-for-consensus` indicates that the PR or Issue is ready for working group participants to reach consensus; can only be applied by the chairs. `has consensus` is an indication to the editors that the Issue has consensus and work on the Pull Request can proceed or that the Pull Request can be merged; can only be applied by the chairs. If there is no consensus to merge the Issue/PR will be closed; GitHub also supports reopening Issues and PRs if there is new information. If you apply a Label, please add a comment to explain your understanding of the current state of the Issue and why you are applying the Label, e.g., discussed during interim meeting and the analysis in [link to comment] was supported, marking as `has consensus`. + +Editorial issues need to be dispatched quickly, and the process is as follows: + +* You submit a Pull Request to make the change; as noted earlier, editorial issues do not require that an Issue be filed. +* You apply the `editorial` Label. +* Editors will merge the Pull Request when appropriate + * If the editors or chairs disagree with the `editorial` label, they will apply the `discuss` Label. + +For noncontroverisal, non-editorial issues: + * You file an Issue. + * You add one or more Assignee(s) or one or more Assignee(s) will be selected during the discussion. + * If at some point during the discussion, the Issue ceases to be noncontroversial, non-editorial the `discuss` Label will be applied. + * The Assignee(s) submit(s) a Pull Request to address the issue; [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue) to the Issue to allow for autoclose. + * Editors will judge when the Pull Request is ready and when it is they will merge the Pull Request. From 797f8e14f0d90e2359c5ce1b89d01012b952cb89 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Thu, 6 Mar 2025 09:08:06 -0500 Subject: [PATCH 02/10] Update README.md Adding a link to the process explainer. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 8aebca2..4d19349 100644 --- a/README.md +++ b/README.md @@ -7,3 +7,5 @@ Attribution is the name given to the measurement system used in advertising. It This repository contains [a specification](https://w3c.github.io/ppa/) that describes an API that would be presented by a browser to websites. The specification contains all of the details. There is no [explainer](https://tag.w3.org/explainers/). All the explanation can be found up front, before it gets into the gory details. + +The WG will use the process outline [here](process.md) to develop this specification. Nothing contained therein is intended to override other W3C process and procedures. From 7e875213b8951a1525a15420074f5c333902204c Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:55:15 -0500 Subject: [PATCH 03/10] Fix grammar Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index fd6c750..34cdf60 100644 --- a/process.md +++ b/process.md @@ -1,4 +1,4 @@ -The PAT working group will use a process to similar to others that have employed a GitHub-centric mode of work. The process summary is as follows, and we should note that this is subject to change as we get closer to a final specification: +The PAT working group will use a process similar to others that have employed a GitHub-centric mode of work. The process summary is as follows, and we should note that this is subject to change as we get closer to a final specification: * To access GitHub, you choose an interface, e.g., [command line interface](https://docs.github.com/en/github-cli), [GitHub mobile](https://docs.github.com/en/get-started/using-github/github-mobile), [GitHub desktop](https://docs.github.com/en/desktop), [VSCode](https://code.visualstudio.com/docs/sourcecontrol/github), or Browser. * To start a discussion, you generate an [Issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). Most of the discussion happen on/in an Issue. From f1b66b51d8ee7a7ca75d15b172c57bb3ed586e2b Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:55:37 -0500 Subject: [PATCH 04/10] fix grammer Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index 34cdf60..a32032d 100644 --- a/process.md +++ b/process.md @@ -1,7 +1,7 @@ The PAT working group will use a process similar to others that have employed a GitHub-centric mode of work. The process summary is as follows, and we should note that this is subject to change as we get closer to a final specification: * To access GitHub, you choose an interface, e.g., [command line interface](https://docs.github.com/en/github-cli), [GitHub mobile](https://docs.github.com/en/get-started/using-github/github-mobile), [GitHub desktop](https://docs.github.com/en/desktop), [VSCode](https://code.visualstudio.com/docs/sourcecontrol/github), or Browser. -* To start a discussion, you generate an [Issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). Most of the discussion happen on/in an Issue. +* To start a discussion, you generate an [Issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). Most of the discussion happens on/in an Issue. * To suggest a change, you generate a [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). “Discussions” about specific wording changes for a Pull Request occur on/in the PR. * To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; PRs related to issues will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). * To publish a new version of the specification, GitHub plus some [W3C Tooling](https://github.com/w3c/echidna?tab=readme-ov-file) takes care of this [within minutes](https://www.w3.org/2021/03/18-echidna/?full#1) of the PR being merged. From ff8057f511b26b88e526ba2d72ceea90ced8581d Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:56:10 -0500 Subject: [PATCH 05/10] tech fix Co-authored-by: Charlie Harrison --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index a32032d..390d6ee 100644 --- a/process.md +++ b/process.md @@ -3,7 +3,7 @@ The PAT working group will use a process similar to others that have employed a * To access GitHub, you choose an interface, e.g., [command line interface](https://docs.github.com/en/github-cli), [GitHub mobile](https://docs.github.com/en/get-started/using-github/github-mobile), [GitHub desktop](https://docs.github.com/en/desktop), [VSCode](https://code.visualstudio.com/docs/sourcecontrol/github), or Browser. * To start a discussion, you generate an [Issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). Most of the discussion happens on/in an Issue. * To suggest a change, you generate a [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). “Discussions” about specific wording changes for a Pull Request occur on/in the PR. -* To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; PRs related to issues will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). +* To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; issues related to PRs will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). * To publish a new version of the specification, GitHub plus some [W3C Tooling](https://github.com/w3c/echidna?tab=readme-ov-file) takes care of this [within minutes](https://www.w3.org/2021/03/18-echidna/?full#1) of the PR being merged. * To track what has happen, you can consult the GitHub logs; Github logs everything - all issues, discussions about issues, labels, label changes, and specification changes, etc. * To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email, the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). From 048339d4e112a54919ecd715d181184d086784a0 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:56:31 -0500 Subject: [PATCH 06/10] Fix grammar Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index 390d6ee..68bfbc8 100644 --- a/process.md +++ b/process.md @@ -5,7 +5,7 @@ The PAT working group will use a process similar to others that have employed a * To suggest a change, you generate a [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). “Discussions” about specific wording changes for a Pull Request occur on/in the PR. * To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; issues related to PRs will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). * To publish a new version of the specification, GitHub plus some [W3C Tooling](https://github.com/w3c/echidna?tab=readme-ov-file) takes care of this [within minutes](https://www.w3.org/2021/03/18-echidna/?full#1) of the PR being merged. -* To track what has happen, you can consult the GitHub logs; Github logs everything - all issues, discussions about issues, labels, label changes, and specification changes, etc. +* To track what has happened, you can consult the GitHub logs; GitHub logs everything -- all issues, discussions about issues, labels, label changes, and specification changes, etc. * To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email, the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). What follows is a more detail explanation of the process. From fba306953fb3816b635b2562de80a385d0f9aa7c Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:56:51 -0500 Subject: [PATCH 07/10] Fix grammar Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index 68bfbc8..217fe9a 100644 --- a/process.md +++ b/process.md @@ -6,7 +6,7 @@ The PAT working group will use a process similar to others that have employed a * To make a change, editors and, in rare circumstances, Chairs “merge” the Pull Request; issues related to PRs will be autoclosed with [link](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). * To publish a new version of the specification, GitHub plus some [W3C Tooling](https://github.com/w3c/echidna?tab=readme-ov-file) takes care of this [within minutes](https://www.w3.org/2021/03/18-echidna/?full#1) of the PR being merged. * To track what has happened, you can consult the GitHub logs; GitHub logs everything -- all issues, discussions about issues, labels, label changes, and specification changes, etc. -* To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email, the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). +* To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email: the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). What follows is a more detail explanation of the process. From 5cd6e4cc71cd779c94830c7f0dc6400b8c58f919 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:57:06 -0500 Subject: [PATCH 08/10] Fix grammar Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index 217fe9a..efd026e 100644 --- a/process.md +++ b/process.md @@ -8,7 +8,7 @@ The PAT working group will use a process similar to others that have employed a * To track what has happened, you can consult the GitHub logs; GitHub logs everything -- all issues, discussions about issues, labels, label changes, and specification changes, etc. * To stay informed, you can either “watch” the [PPA repo](https://github.com/w3c/ppa) or check your email: the repo’s notifications are copied to the [PAT working group mailing list](https://lists.w3.org/Archives/Public/public-patwg/). -What follows is a more detail explanation of the process. +What follows is a more detailed explanation of the process. Not all Issues are created equal. Some Issues are editorial; some are noncontroversial, non-editorial; and some are controversial. More process is required for controversial Issues than for noncontroversial Issues. From 3399af89402be01afef2703d5e0eb16ab7c6afe6 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 7 Mar 2025 21:57:22 -0500 Subject: [PATCH 09/10] Fix spelling Co-authored-by: Andrew Paseltiner --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index efd026e..4c73607 100644 --- a/process.md +++ b/process.md @@ -21,7 +21,7 @@ Editorial issues need to be dispatched quickly, and the process is as follows: * Editors will merge the Pull Request when appropriate * If the editors or chairs disagree with the `editorial` label, they will apply the `discuss` Label. -For noncontroverisal, non-editorial issues: +For noncontroversial, non-editorial issues: * You file an Issue. * You add one or more Assignee(s) or one or more Assignee(s) will be selected during the discussion. * If at some point during the discussion, the Issue ceases to be noncontroversial, non-editorial the `discuss` Label will be applied. From d163e4898ce60566a654c169236fccfe1ac9474b Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Mon, 10 Mar 2025 08:58:36 -0400 Subject: [PATCH 10/10] Fix wallotext Co-authored-by: Martin Thomson --- process.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/process.md b/process.md index 4c73607..9b452ac 100644 --- a/process.md +++ b/process.md @@ -12,7 +12,16 @@ What follows is a more detailed explanation of the process. Not all Issues are created equal. Some Issues are editorial; some are noncontroversial, non-editorial; and some are controversial. More process is required for controversial Issues than for noncontroversial Issues. -While nobody wants their Issue to be controversial and most do not start out that way, it happens and when it does the chairs get involved to (if necessary) mediate the discussion and to (chair only function) judge consensus on the way forward. We will use [Labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels), `discuss`, `needs consensus`, `call-for-consensus`, and `has consensus`, to move through the process. `discuss` is notice that the Issue needs to be discussed; can be applied by anyone. `needs consensus` is a request for the chairs step in; can be applied by anyone. `call-for-consensus` indicates that the PR or Issue is ready for working group participants to reach consensus; can only be applied by the chairs. `has consensus` is an indication to the editors that the Issue has consensus and work on the Pull Request can proceed or that the Pull Request can be merged; can only be applied by the chairs. If there is no consensus to merge the Issue/PR will be closed; GitHub also supports reopening Issues and PRs if there is new information. If you apply a Label, please add a comment to explain your understanding of the current state of the Issue and why you are applying the Label, e.g., discussed during interim meeting and the analysis in [link to comment] was supported, marking as `has consensus`. +While nobody wants their Issue to be controversial and most do not start out that way, it happens and when it does the chairs get involved to (if necessary) mediate the discussion and to (chair only function) judge consensus on the way forward. We will use [Labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels), `discuss`, `needs consensus`, `call-for-consensus`, and `has consensus`, to move through the process. + +* `discuss` is notice that the Issue needs to be discussed; can be applied by anyone. +* `needs consensus` is a request for the chairs step in; can be applied by anyone. +* `call-for-consensus` indicates that the PR or Issue is ready for working group participants to reach consensus; can only be applied by the chairs. +* `has consensus` is an indication to the editors that the Issue has consensus and work on the Pull Request can proceed or that the Pull Request can be merged; can only be applied by the chairs. + +If there is no consensus to merge the Issue/PR will be closed; GitHub also supports reopening Issues and PRs if there is new information. + +If you apply a Label, please add a comment to explain your understanding of the current state of the Issue and why you are applying the Label, e.g., "discussed during interim meeting and the analysis in \[link to comment\] was supported, marking as `has consensus`". Editorial issues need to be dispatched quickly, and the process is as follows: