BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241002T124519Z
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:48bc46a0-adca-421e-86de-85cb2fde8ccb
DTSTAMP:20241002T124519Z
SUMMARY:Discuss: How to build a new feature for the web platform — and ma
ke it a success with developers
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/48bc46a0-adca-421e-86de-85cb
2fde8ccb/\n\nThe goal of this session is to explore and discuss how to bes
t get new features for the platform successfully created\, implemented\, t
ested\, documented\, and adopted — likely with active participation in t
he session from some people who’ve had experience in each of those areas
and who can offer particular “lessons learned” insights and tips. Als
o:\n\n- documenting the process/advice (brainstorming\, with the goal of w
riting something up from the session notes)\n- discussing ways in which th
e existing process might be improved\n- answering questions about parts of
the process that may be especially mysterious to most people\n\nAgenda\n\
n**Chairs:**\nMichael[tm] Smith (sideshowbarker)\n\n**Description:**\nThe
goal of this session is to explore and discuss how to best get new feature
s for the platform successfully created\, implemented\, tested\, documente
d\, and adopted — likely with active participation in the session from s
ome people who’ve had experience in each of those areas and who can offe
r particular “lessons learned” insights and tips. Also:\n\n- documenti
ng the process/advice (brainstorming\, with the goal of writing something
up from the session notes)\n- discussing ways in which the existing proces
s might be improved\n- answering questions about parts of the process that
may be especially mysterious to most people\n\n**Goal(s):**\nThe session
goal is to _discuss_ and help each other understand how to successfully ge
t new features into the platform.\n\n\n**Agenda:**\nThis session aims to a
very interactive **_discussion_ session**\, along the [“How to facilita
te a breakout discussion”](https://gist.github.com/spectranaut/d000bcc29
7005c262b711c117c770b22) guidelines.\n\nSo when you come to the session\,
please be prepared to _discuss_ — with the discussion we all have togeth
er being guided by the following _“How to build a new feature for the we
b platform”_ outline:\n\n_11-step process (zero-indexed\, in hex):_\n\n0
. Describing the problem: What specific problem are you trying to solve. W
ho are you trying to solve it for?\n1. Proposing a solution\; writing a go
od explainer with a problem description + proposed solution (**optional/`T
ODO` step**)\n2. Initiating and leading a focused discussion in a spec iss
ue tracker about the problem and possible solutions.\n3. Putting together
a spec or spec PR for a problem solution (and learning spec-publishing too
ls and their quirks).\n4. Writing good WPTs and getting attention for them
from reviewers.\n5. Using browser-project bug/issue trackers to raise com
pelling implementation requests.\n6. Contributing an implementation patch
to a browser project (and learning the project’s patch-contribution proc
ess).\n7. Getting documentation written for your feature in MDN (working
with MDN writers/editors and technical reviewers).\n8. Driving web-develop
er adoption through outreach in places where web-developers pay attention.
\n9. Monitoring web-developer experience/success and identifying web-devel
oper pain points/frustrations.\n\n A. Iterating over each step as ne
eded (including\, going back to step #0 and repeating the who
le cycle)\n\n_＊ Common off-by-one error many folks make: starting at ste
p #1 (proposing solutions without first describing problems).
_\n\n**Resources**\n\n- [The history of focus-visible and inert](https://w
ww.igalia.com/chats/alice-and-rob) — success story\n- [LXJS 2013 - Domen
ic Denicola - How to win friends and influence standards bodies](https://w
ww.youtube.com/watch?v=hneN6aW-d9w)\n- [Hitchhiker's Guide to Web Standard
s // Dominic Farolino // CascadiaJS 2018](https://www.youtube.com/watch?v=
z2SbknMWtp0)\n- [Web Platform Contribution Guide](https://wpc.guide/)\n---
\n\n- [HTML Design Principles](https://www.w3.org/TR/html-design-principle
s/#toc) — the “ten commandments” of web-platform feature development
\n- [How to Win Friends and Influence People](https://archive.org/details/
bwb_KS-365-216/) — 1936 book by Dale Carnegie (pioneer “motivational s
peaker”)\n- [Tips for effective explainers](https://tag.w3.org/explainer
s/#tips-for-effective-explainers) — W3C Tag document\n- https://ian.hix
ie.ch/bible/handling-people — the secret sauce\n---\n- [`https://www.w3.
org/community/about/faq/#how-do-i-propose-a-group`](https://www.w3.org/com
munity/about/faq/#how-do-i-propose-a-group)\n- [`https://www.w3.org/commun
ity/about/faq/#how-do-we-publish-a-report`](https://www.w3.org/community/a
bout/faq/#how-do-we-publish-a-report)\n- https://www.w3.org/community/abou
t/tool/ • https://github.com/w3c-cg → `https://w3c-cg.github.io/my-
feature`\n---\n- [`https://wicg.io/#proposals`](https://wicg.io/#proposals
)\n- [`https://github.com/WICG/admin/#contributing-new-proposals`](https:/
/github.com/WICG/admin/#contributing-new-proposals)\n- https://github.com/
WICG/starter-kit\n---\n- [`https://whatwg.org/faq#adding-new-features`](ht
tps://whatwg.org/faq#adding-new-features)\n- https://whatwg.org/working-mo
de\n- https://whatwg.org/stages\n---\n- https://github.com/tc39/ecma402/bl
ob/main/CONTRIBUTING.md\n- https://tc39.es/process-document/\n---\n- https
://web-platform-tests.org/writing-tests/\n- https://github.com/tc39/test26
2/blob/main/CONTRIBUTING.md\n---\n- https://webkit.org/contributing-code/\
n- https://firefox-source-docs.mozilla.org/\n- https://chromium.googlesour
ce.com/chromium/src/+/refs/heads/main/docs/contributing.md\n---\n- https:/
/github.com/mdn/content/blob/main/CONTRIBUTING.md\n---\n\n**Materials:**\n
- [minutes](https://www.w3.org/2024/09/25-feature-success-minutes.html)\n-
[Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/is
sues/7)\n\n**Track(s):**\n- Feature lifecycle
STATUS:CONFIRMED
CREATED:20240916T214708Z
LAST-MODIFIED:20241002T124519Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR