Information

The Future of TAG Reviews & Other Output
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
– Pacific Daylight Time
Status:
Confirmed
Location:
-1 Lower Level - Catalina 7
Participants:
Rachel Andrew, Daniel Appelquist, Panos Astithas, Matthew Atkinson, David Baron, Christian Biesinger, Sarven Capadisli, Tantek Çelik, Daniel Ehrenberg, Sam Goto, Reilly Grant, Scott Haseley, Xiaocheng Hu, Lu Huang, Rick Johnson, Brian Kardell, Zoltan Kis, Roman Komarov, Ege Korkan, Siye Liu, Nigel Megitt, Michal Mocny, Mark Nottingham, Nicolas Pena Moreno, Vincent Scheib, Zacharias Törnblom, Lea Verou, Chris Wilson, Rachel Yager, Jeffrey Yasskin, Benjamin Young
Big meeting:
TPAC 2024 (Calendar)

Since 2013, the TAG has been systematically reviewing new web features as they are being designed and specified. We’ve called this process “Design Review”. Right 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, such as updates to the Design Principles, Security & Privacy Self-Review Questionnaire, newer documents such as the Privacy Principles, and BF Cache Guide, as well as one-off "findings."

The design review issue queue is what drives most of our meeting agendas. Insights that come out of design reviews also inform and prioritize the work we do on these other documents that the TAG publishes. The TAG has a backlog of design reviews, and its feedback in those reviews has sometimes been too late to have an effect on the development of the 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 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 best ways to do that.

This session is to gather 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 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.

Agenda

Chairs:
Daniel Appelquist, Lea Verou

Description:
Since 2013, the TAG has been systematically reviewing new web features as they are being designed and specified. We’ve called this process “Design Review”. Right 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, such as updates to the Design Principles, Security & Privacy Self-Review Questionnaire, newer documents such as the Privacy Principles, and BF Cache Guide, as well as one-off "findings."

The design review issue queue is what drives most of our meeting agendas. Insights that come out of design reviews also inform and prioritize the work we do on these other documents that the TAG publishes. The TAG has a backlog of design reviews, and its feedback in those reviews has sometimes been too late to have an effect on the development of the 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 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 best ways to do that.

This session is to gather 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 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.

Goal(s):
Refine the plan in https://github.com/w3ctag/process/issues/36.

Agenda:
The format will be a short overview of the Design Review process followed by open discussion. Please note, we don’t want to use this as a forum to discuss the technical details of currently open reviews.

Materials:

Track(s):

  • Standards

Minutes

 Read minutes

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

Feedback

Report feedback and issues on GitHub.