Re: privacywg call for consensus: GPC first public working draft

Wearing my hat as a rep of my org (as opposed to my hat as an editor) no objections, fully support.

-- Aram Zucker-Scharff
The Washington Post
+1-703-829-0532


From: Jeffrey Yasskin <jyasskin@google.com>
Date: Monday, November 11, 2024 at 2:19 PM
To: Nick Doty <ndoty@cdt.org>
Cc: public-privacy (W3C mailing list) <public-privacy@w3.org>
Subject: Re: privacywg call for consensus: GPC first public working draft
CAUTION: EXTERNAL SENDER
For me:

support: publish a FPWD based on the gpc-spec repo
support: auto-publish new Working Drafts based on merged updates
neutral/abstain: plan to publish explainer as a non-normative Draft Note, and
set auto-publish as well

(That is, no objections.)

Thanks for moving this forward!
Jeffrey

On Mon, Nov 11, 2024 at 11:00 AM Nick Doty <ndoty@cdt.org<mailto:ndoty@cdt.org>> wrote:
Hi Privacy folks,

This is a call for consensus, to confirm on the list the proposed
resolution that we had at last week's Privacy Working Group meeting,
that the Privacy Working Group should publish a First Public Working
Draft of the GPC (Global Privacy Control) specification.

We had consensus at the meeting, but also wish to confirm on
the list, for the following proposed decisions:

proposed: publish a FPWD based on the gpc-spec repo
proposed: auto-publish new Working Drafts based on merged updates
proposed: plan to publish explainer as a non-normative Draft Note, and
set auto-publish as well

Meeting minutes:
https://github.com/w3c/privacywg/blob/main/minutes/privacywg-20241107.md


As was emphasized on the call, publishing a First Public Working Draft
of the GPC spec does not communicate Working Group consensus on all
the contents, but instead indicates that the Working Group is working
on this document and that we are asking for review as we work on it.
To follow the requirements of the Process, we also have to document
the open issues, which are currently tracked in the GitHub issue
tracker; that also doesn't preclude opening additional issues.

If you have an objection to these decisions, please let us know on
list by next Monday, November 18th.

This would also include these follow up actions that we would ask the
W3C Team to take. Thanks Philippe and Tara!

ask team to move repo to privacywg, and set up redirects
ask team to enable Echidna and auto-publication
ask team to notify / start wider review

Other reminders:
If you or your organization haven't yet joined the Privacy Working
Group, please do so by following the instructions here:
https://www.w3.org/groups/wg/privacy/instructions/ [w3.org]<https://urldefense.com/v3/__https:/www.w3.org/groups/wg/privacy/instructions/__;!!M9LbjjnYNg9jBDflsQ!DCdr68J-OjqCtnKrZAllQmXyXnnz__1ImoE1H3fK88rZJLdgcHdbfL_pgShbnysncupPJXFBYLU-Uea0811MbhTO4bxM$>

Because of the change in charter and type of the group, participants
in PING (Privacy Interest Group) need to re-join and approve the
commitments of participation.

We plan to meet again on Thursday, November 21st. There will be a
separate thread on questions of meeting scheduling.


Thanks for your participation and work on privacy. I anticipate in the
coming year that this will become an even more important area of work
and we will benefit from the W3C community's efforts.

-- Nick, for the co-chairs

--
Nick Doty | https://npdoty.name [npdoty.name]<https://urldefense.com/v3/__https:/npdoty.name__;!!M9LbjjnYNg9jBDflsQ!DCdr68J-OjqCtnKrZAllQmXyXnnz__1ImoE1H3fK88rZJLdgcHdbfL_pgShbnysncupPJXFBYLU-Uea0811MbtwY8gKo$>
Senior Technologist
Center for Democracy & Technology | https://cdt.org [cdt.org]<https://urldefense.com/v3/__https:/cdt.org__;!!M9LbjjnYNg9jBDflsQ!DCdr68J-OjqCtnKrZAllQmXyXnnz__1ImoE1H3fK88rZJLdgcHdbfL_pgShbnysncupPJXFBYLU-Uea0811Mbls1m-CZ$>