Re: [admin] Meeting: 14-15 June 2023 -- F2F in London (#14)
Closed: [admin] Meeting: 2nd & 4th May 2023 -- Virtual (#13)
[meetings] Agenda Request - On premise trusted servers (#122)
- Re: [meetings] Agenda Request - On premise trusted servers (#122)
- Re: [meetings] Agenda Request - On premise trusted servers (#122)
- Re: [meetings] Agenda Request - On premise trusted servers (#122)
Re: [meetings] Agenda Request - Cross device attribution options (#115)
[meetings] Agenda Request - Presenting EXPAT (#121)
Closed: [meetings] Agenda Request - Please add Agenda Items for the upcoming meeting (#111)
[meetings] Agenda open for next PATCG meeting (#120)
Closed: [meetings] Agenda Request - Private measurement of single events (#112)
Closed: [docs-and-reports] Private measurement of single events (#41)
[patwg-charter] Pull Request: Mark single-implementation features "at risk"
[patwg-charter] Charter should include baseline privacy boundaries (#61)
Closed: [meetings] F2F Meeting Cadence (#88)
[meetings] Pull Request: Add slides from the May 2 meeting
[docs-and-reports] Pull Request: Add private single events to areas of agreement
- Re: [docs-and-reports] Add private single events to areas of agreement (#43)
- Re: [docs-and-reports] Add private single events to areas of agreement (#43)
- Re: [docs-and-reports] Add private single events to areas of agreement (#43)
- Re: [docs-and-reports] Add private single events to areas of agreement (#43)
- Re: [docs-and-reports] Add private single events to areas of agreement (#43)
- [docs-and-reports] Merged Pull Request: Add private single events to areas of agreement
Re: [patwg-charter] WG Charter Comment Resolution (#44)
Closed: [patwg-charter] Require Data Section in Success Criteria (#35)
Re: [patwg-charter] Require Data Section in Success Criteria (#35)
Closed: [patwg-charter] Switch links to a dated version of the TAG document (#55)
[patwg-charter] Merged Pull Request: Proposals should clearly state business factors and user risks
Re: [patwg-charter] Deweaponize 'all known' (#60)
[patwg-charter] Closed Pull Request: Addressing #35 - making explicit that proposals should detail the data they intend to use and return.
Re: [patwg-charter] Addressing #35 - making explicit that proposals should detail the data they intend to use and return. (#36)
Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59)
- Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59)
- Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59)
- Re: [patwg-charter] Proposals should clearly state business factors and user risks (#59)