search

w3c / tpac2024-breakouts

Repository setup to collect and organize breakout session proposals for TPAC 2024
0 stars 0 forks source link

Discuss: How to build a new feature for the web platform — and make it a success with developers #7

Open sideshowbarker opened 2 weeks ago

sideshowbarker commented 2 weeks ago

Session description

The goal of this session is to explore and discuss how to best get new features for the platform successfully created, implemented, tested, documented, and adopted — likely with active participation in the session from some people who’ve had experience in each of those areas and who can offer particular “lessons learned” insights and tips. Also:

Session goal

The session goal is to discuss and help each other understand how to successfully get new features into the platform.

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

discuss-how-to-build-a-new-feature-for-the-web-platform-and-make-it-a-success-with-developers

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

This session aims to a very interactive discussion session, along the “How to facilitate a breakout discussion” guidelines.

So when you come to the session, please be prepared to discuss — with the discussion we all have together being guided by the following “How to build a new feature for the web platform” outline:

11-step process (zero-indexed, in hex):

  1. Describing the problem: What specific problem are you trying to solve. Who are you trying to solve it for?
  2. Proposing a solution; writing a good explainer with a problem description + proposed solution (optional/TODO step)
  3. Initiating and leading a focused discussion in a spec issue tracker about the problem and possible solutions.
  4. Putting together a spec or spec PR for a problem solution (and learning spec-publishing tools and their quirks).
  5. Writing good WPTs and getting attention for them from reviewers.
  6. Using browser-project bug/issue trackers to raise compelling implementation requests.
  7. Contributing an implementation patch to a browser project (and learning the project’s patch-contribution process).
  8. Getting documentation written for your feature in MDN (working with MDN writers/editors and technical reviewers).
  9. Driving web-developer adoption through outreach in places where web-developers pay attention.
  10. Monitoring web-developer experience/success and identifying web-developer pain points/frustrations.

   A. Iterating over each step as needed (including, going back to step #0 and repeating the whole cycle)

＊ Common off-by-one error many folks make: starting at step #1 (proposing solutions without first describing problems).

Resources