BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241002T122510Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:19f87be5-b119-47dc-87a1-59514bd929fa
DTSTAMP:20241002T122510Z
SUMMARY:The Future of TAG Reviews & Other Output
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/19f87be5-b119-47dc-87a1-5951
 4bd929fa/\n\nSince 2013\, the TAG has been systematically reviewing new we
 b features as they are being designed and specified. We’ve called this p
 rocess “Design Review”. Right now\, the majority of the TAG’s time a
 nd effort is spent on design reviews\, with the remainder of our time focu
 sing on "other" outputs\, such as updates to the [Design Principles](https
 ://www.w3.org/TR/design-principles/)\, [Security & Privacy Self-Review Que
 stionnaire](https://w3ctag.github.io/security-questionnaire/)\, newer docu
 ments such as the [Privacy Principles](https://www.w3.org/TR/privacy-princ
 iples/)\, and [BF Cache Guide](https://w3ctag.github.io/bfcache-guide/)\, 
 as well as [one-off "findings."](https://www.w3.org/2001/tag/doc/web-witho
 ut-3p-cookies/)\n\nThe design review issue queue is what drives most of ou
 r meeting agendas. Insights that come out of design reviews also inform an
 d prioritize the work we do on these other documents that the TAG publishe
 s. The TAG has a backlog of design reviews\, and its feedback in those rev
 iews has sometimes been too late to have an effect on the development of t
 he reviewed spec. This has caused some frustration both on the part of the
  people filing these reviews and in the TAG. We need to find a way to focu
 s and prioritize our work on the issues where it's most needed - where it 
 can have the greatest benefit to the web. This session is intended to gath
 er community ideas on the best ways to do that.\n\nThis session is to gath
 er feedback from the W3C community. Is it clear how the TAG design review 
 process works? Is it working for you? Have you filed TAG reviews and been 
 frustrated with the results? Have you filed TAG reviews and been delighted
  with the results? Are we balancing correctly between design reviews and o
 ther output? We’d like to “check the temperature” to ensure what we
 ’re doing is useful to the community and we’d also love your feedback 
 about what we could be doing better? Help us help you.\n\nAgenda\n\n**Chai
 rs:**\nDaniel Appelquist\, Lea Verou\n\n**Description:**\nSince 2013\, the
  TAG has been systematically reviewing new web features as they are being 
 designed and specified. We’ve called this process “Design Review”. R
 ight now\, the majority of the TAG’s time and effort is spent on design 
 reviews\, with the remainder of our time focusing on "other" outputs\, suc
 h as updates to the [Design Principles](https://www.w3.org/TR/design-princ
 iples/)\, [Security & Privacy Self-Review Questionnaire](https://w3ctag.gi
 thub.io/security-questionnaire/)\, newer documents such as the [Privacy Pr
 inciples](https://www.w3.org/TR/privacy-principles/)\, and [BF Cache Guide
 ](https://w3ctag.github.io/bfcache-guide/)\, as well as [one-off "findings
 ."](https://www.w3.org/2001/tag/doc/web-without-3p-cookies/)\n\nThe design
  review issue queue is what drives most of our meeting agendas. Insights t
 hat come out of design reviews also inform and prioritize the work we do o
 n these other documents that the TAG publishes. The TAG has a backlog of d
 esign reviews\, and its feedback in those reviews has sometimes been too l
 ate to have an effect on the development of the reviewed spec. This has ca
 used some frustration both on the part of the people filing these reviews 
 and in the TAG. We need to find a way to focus and prioritize our work on 
 the issues where it's most needed - where it can have the greatest benefit
  to the web. This session is intended to gather community ideas on the bes
 t ways to do that.\n\nThis session is to gather feedback from the W3C comm
 unity. Is it clear how the TAG design review process works? Is it working 
 for you? Have you filed TAG reviews and been frustrated with the results? 
 Have you filed TAG reviews and been delighted with the results? Are we bal
 ancing correctly between design reviews and other output? We’d like to 
 “check the temperature” to ensure what we’re doing is useful to the 
 community and we’d also love your feedback about what we could be doing 
 better? Help us help you.\n\n**Goal(s):**\nRefine the plan in https://gith
 ub.com/w3ctag/process/issues/36.\n\n\n**Agenda:**\nThe format will be a sh
 ort overview of the Design Review process followed by open discussion. Ple
 ase note\, we don’t want to use this as a forum to discuss the technical
  details of currently open reviews.\n\n**Materials:**\n- [minutes](https:/
 /www.w3.org/2024/09/25-future-tag-minutes.html)\n- [Session proposal on Gi
 tHub](https://github.com/w3c/tpac2024-breakouts/issues/59)\n\n**Track(s):*
 *\n- Standards
STATUS:CONFIRMED
CREATED:20240916T215613Z
LAST-MODIFIED:20241002T122510Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR