Information

Discuss: How to build a new feature for the web platform — and make it a success with developers
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
– Pacific Daylight Time
Status:
Confirmed
Location:
-1 Lower Level - Catalina 1
Participants:
Martin Alvarez-Espinar, Rachel Andrew, Eemeli Aro, Panos Astithas, David Baron, Jan Jaap de Groot, Guohui Deng, Nishitha Dey, Balazs Engedy, Marie-Claire Forgue, Sam Goto, Joone Hur, Westbrook Johnson, Pete LePage, Alison Maher, Sandor Major, Arnaud Mandy, Niklas Merz, James Nurthen, Simon Pieters, Alexandra Reimers, Adrian Roselli, Vincent Scheib, Aaron Selya, Michael[tm] Smith (sideshowbarker), Rachel Yager
Big meeting:
TPAC 2024 (Calendar)

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:

  • documenting the process/advice (brainstorming, with the goal of writing something up from the session notes)
  • discussing ways in which the existing process might be improved
  • answering questions about parts of the process that may be especially mysterious to most people

Agenda

Chairs:
Michael[tm] Smith (sideshowbarker)

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:

  • documenting the process/advice (brainstorming, with the goal of writing something up from the session notes)
  • discussing ways in which the existing process might be improved
  • answering questions about parts of the process that may be especially mysterious to most people

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

Agenda:
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 <span>#</span>0 and repeating the whole cycle)

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

Resources

Materials:

Track(s):

  • Feature lifecycle

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.