BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230919T113651Z
BEGIN:VTIMEZONE
TZID:Europe/Madrid
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:c2342b95-4d80-47c3-893c-25f07f2d8eb2
DTSTAMP:20230919T113651Z
SUMMARY:Beyond Interop: Baseline and more
DTSTART;TZID=Europe/Madrid:20230913T110000
DTEND;TZID=Europe/Madrid:20230913T120000
DESCRIPTION:https://www.w3.org/events/meetings/c2342b95-4d80-47c3-893c-25f0
 7f2d8eb2/\n\nWeb developers report that[ keeping up with changes to the pl
 atform is a major issue for them](https://web.dev/deep-dive-into-developer
 -pain-points/). Developers have difficulty keeping up with changes in the 
 web platform\, such as the introduction of new features and the resolution
  of interoperability issues\, and knowing when features are well-establish
 ed in their users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nEven though 
 many developers enjoy access to detailed information about their audiences
  and the browsers they use (e.g.\, through site analytics\, support metric
 s\, user interviews\, etc.)\, others don’t or work at a remove from end 
 users. A new project won’t have a measurable audience until it launches.
  A library maintainer or application vendor might have\, at best\, an indi
 rect view of the capabilities of users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\
 n\n\n\n\nDespite the glut of information about browser support\, releases\
 , and global usage\, these developers are left on their own to draw a plat
 form-wide support picture\, with ample opportunity for errors and confusio
 n. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe Baseline project is one way that in
 tends to help these developers by offering a shortcut past the complexity.
 \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThis session will discuss the lessons we l
 earned in the WebDX CG\, open questions we have\, and possible ways forwar
 d to serve the web developer community.\n\nAgenda\n\n**Chairs:**\nKadir To
 pal\n\n**Description:**\nWeb developers report that[ keeping up with chang
 es to the platform is a major issue for them](https://web.dev/deep-dive-in
 to-developer-pain-points/). Developers have difficulty keeping up with cha
 nges in the web platform\, such as the introduction of new features and th
 e resolution of interoperability issues\, and knowing when features are we
 ll-established in their users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
 Even though many developers enjoy access to detailed information about the
 ir audiences and the browsers they use (e.g.\, through site analytics\, su
 pport metrics\, user interviews\, etc.)\, others don’t or work at a remo
 ve from end users. A new project won’t have a measurable audience until 
 it launches. A library maintainer or application vendor might have\, at be
 st\, an indirect view of the capabilities of users’ browsers.\n\n\n\n\n\
 n\n\n\n\n\n\n\n\n\n\nDespite the glut of information about browser support
 \, releases\, and global usage\, these developers are left on their own to
  draw a platform-wide support picture\, with ample opportunity for errors 
 and confusion. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe Baseline project is one
  way that intends to help these developers by offering a shortcut past the
  complexity.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThis session will discuss the 
 lessons we learned in the WebDX CG\, open questions we have\, and possible
  ways forward to serve the web developer community.\n\n**Goal(s):**\nBroad
 er awareness of the problem that is being addressed and identifying ideas 
 that are worth exploring further\n\n\n**Materials:**\n- [slides](https://l
 ists.w3.org/Archives/Public/www-archive/2023Sep/att-0011/Beyond_Interop_Ba
 seline_and_more.pdf)\n- [minutes](https://www.w3.org/2023/09/13-beyond-int
 erop-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/
 tpac2023-breakouts/issues/60)\n\n**Track(s):**\n- developer experience
STATUS:CONFIRMED
CREATED:20230905T054036Z
LAST-MODIFIED:20230919T113651Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Nervion-Arenal II - Level -1
CATEGORIES:TPAC 2023,Breakout Sessions
END:VEVENT
END:VCALENDAR