public-patcg@w3.org from May 2023 by date

Wednesday, 31 May 2023

• Re: [admin] Meeting: 14-15 June 2023 -- F2F in London (#14) Sean Turner via GitHub
• Closed: [admin] Meeting: 2nd & 4th May 2023 -- Virtual (#13) Sean Turner via GitHub

Tuesday, 30 May 2023

• Re: [meetings] Agenda Request - On premise trusted servers (#122) Eric Rescorla via GitHub
• Re: [meetings] Agenda Request - On premise trusted servers (#122) Alberto via GitHub

Monday, 29 May 2023

• Re: [meetings] Agenda Request - On premise trusted servers (#122) Eric Rescorla via GitHub
• [meetings] Agenda Request - On premise trusted servers (#122) Vincent Minet via GitHub

Thursday, 25 May 2023

• Re: [meetings] Agenda Request - Cross device attribution options (#115) Charlie Harrison via GitHub
• [meetings] Agenda Request - Presenting EXPAT (#121) rdar via GitHub

Wednesday, 24 May 2023

• Closed: [meetings] Agenda Request - Please add Agenda Items for the upcoming meeting (#111) Aram Zucker-Scharff via GitHub
• [meetings] Agenda open for next PATCG meeting (#120) Aram Zucker-Scharff via GitHub

Thursday, 18 May 2023

• Closed: [meetings] Agenda Request - Private measurement of single events (#112) Aram Zucker-Scharff via GitHub
• Closed: [docs-and-reports] Private measurement of single events (#41) Charlie Harrison via GitHub
• [docs-and-reports] Merged Pull Request: Add private single events to areas of agreement Charlie Harrison via GitHub

Tuesday, 16 May 2023

• Re: [meetings] Agenda Request - Private measurement of single events (#112) Aram Zucker-Scharff via GitHub
• Re: [docs-and-reports] Add private single events to areas of agreement (#43) Aram Zucker-Scharff via GitHub

Monday, 8 May 2023

• [patwg-charter] Pull Request: Mark single-implementation features "at risk" Jeffrey Yasskin via GitHub
• [patwg-charter] Charter should include baseline privacy boundaries (#61) Shivan Kaul Sahib via GitHub

Saturday, 6 May 2023

• [meetings] Merged Pull Request: Add slides from the May 2 meeting Sean Turner via GitHub

Friday, 5 May 2023

• Re: [meetings] 2023 Meeting Schedule (#89) Brian May via GitHub
• Re: [meetings] 2023 Meeting Schedule (#89) Sean Turner via GitHub
• Closed: [meetings] F2F Meeting Cadence (#88) Sean Turner via GitHub
• Re: [docs-and-reports] Add private single events to areas of agreement (#43) Martin Thomson via GitHub
• Re: [docs-and-reports] Add private single events to areas of agreement (#43) Charlie Harrison via GitHub

Thursday, 4 May 2023

• Re: [docs-and-reports] Add private single events to areas of agreement (#43) Charlie Harrison via GitHub
• Re: [docs-and-reports] Add private single events to areas of agreement (#43) Shivan Kaul Sahib via GitHub
• [meetings] Pull Request: Add slides from the May 2 meeting Charlie Harrison via GitHub
• Re: [docs-and-reports] Private measurement of single events (#41) Charlie Harrison via GitHub
• [docs-and-reports] Pull Request: Add private single events to areas of agreement Charlie Harrison via GitHub
• Re: [patwg-charter] WG Charter Comment Resolution (#44) Samuel Weiler via GitHub
• Closed: [patwg-charter] Require Data Section in Success Criteria (#35) Aram Zucker-Scharff via GitHub
• Re: [patwg-charter] Require Data Section in Success Criteria (#35) Aram Zucker-Scharff via GitHub
• Closed: [patwg-charter] Switch links to a dated version of the TAG document (#55) Aram Zucker-Scharff via GitHub
• [patwg-charter] Merged Pull Request: Proposals should clearly state business factors and user risks Aram Zucker-Scharff via GitHub

Wednesday, 3 May 2023

• Re: [meetings] Agenda Request - TPAC 2023 Meeting Request (#116) Sean Turner via GitHub
• Re: [patwg-charter] Deweaponize 'all known' (#60) Chris Needham via GitHub

Tuesday, 2 May 2023

• Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59) Shivan Kaul Sahib via GitHub
• Re: [patwg-charter] Addressing #35 - making explicit that proposals should detail the data they intend to use and return. (#36) Nick Doty via GitHub
• [patwg-charter] Closed Pull Request: Addressing #35 - making explicit that proposals should detail the data they intend to use and return. Aram Zucker-Scharff via GitHub
• Re: [patwg-charter] Addressing #35 - making explicit that proposals should detail the data they intend to use and return. (#36) Nick Doty via GitHub
• Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59) Martin Thomson via GitHub
• Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59) Aram Zucker-Scharff via GitHub
• Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59) Nick Doty via GitHub
• [patwg-charter] Merged Pull Request: Deweaponize 'all known' Aram Zucker-Scharff via GitHub
• [patwg-charter] Closed Pull Request: Following discussion with a number of colleagues this PR covers issue… Aram Zucker-Scharff via GitHub
• Re: [patwg-charter] Following discussion with a number of colleagues this PR covers issue… (#18) Aram Zucker-Scharff via GitHub
• Re: [meetings] 2023 Meeting Schedule (#89) Sean Turner via GitHub
• Re: [meetings] F2F Meeting Cadence (#88) Sean Turner via GitHub
• Re: [meetings] Agenda Request - Private measurement of single events (#112) Charlie Harrison via GitHub
• Event Invitation: PATCG Ad-Hoc Meetings: IPA Sean Turner (W3C Calendar)
• Event Invitation: PATCG Ad-Hoc Meetings: IPA Sean Turner (W3C Calendar)
• Event Invitation: PATCG Ad-Hoc Meetings: Topics Sean Turner (W3C Calendar)

Monday, 1 May 2023

• Re: [docs-and-reports] Private measurement of single events (#41) Benjamin M. Case via GitHub
• Re: [meetings] Agenda Request - TPAC 2023 Meeting Request (#116) Michael Kleber via GitHub

Last message date: Wednesday, 31 May 2023 00:59:33 UTC