Open atopal opened 10 months ago
ianbjacobs
commented
10 months ago For our formatting needs, I replaced the following:
- Interop
- Research These address mainly the same participants
With session numbers: #33 and #42.
If those were not the sessions you were thinking about, please let me know. Thanks!
atopal
commented
10 months ago Thank you!
On Thu, Aug 31, 2023 at 5:42 PM ianbjacobs @.***> wrote:
For our formatting needs, I replaced the following:
- Interop
- Research These address mainly the same participants
With session numbers: #33 https://github.com/w3c/tpac2023-breakouts/issues/33 and #42 https://github.com/w3c/tpac2023-breakouts/issues/42.
If those were not the sessions you were thinking about, please let me know. Thanks!
— Reply to this email directly, view it on GitHub https://github.com/w3c/tpac2023-breakouts/issues/60#issuecomment-1701285263, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEIGHEG2LRV22UQQS54K7TXYCWFHANCNFSM6AAAAAA4GD5IFI . You are receiving this because you authored the thread.Message ID: @.***>
Session description
Web developers report that keeping up with changes to the platform is a major issue for them. 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-established in their users’ browsers.
Even though many developers enjoy access to detailed information about their audiences and the browsers they use (e.g., through site analytics, support metrics, 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 indirect view of the capabilities of users’ browsers.
Despite 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.
The Baseline project is one way that intends to help these developers by offering a shortcut past the complexity.
This 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.
Session goal
Broader awareness of the problem that is being addressed and identifying ideas that are worth exploring further
Additional session chairs (Optional)
No response
IRC channel (Optional)
beyond-interop
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
33, #42
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)