Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
sideshowbarker opened this issue Jun 17, 2024 · 0 comments
Labels
session Breakout session proposal track: Feature lifecycle

Comments

@sideshowbarker
Copy link

sideshowbarker commented Jun 17, 2024

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:

  • 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

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)

#feature-success

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










Links to calendar

Meeting materials

@sideshowbarker sideshowbarker added the session Breakout session proposal label Jun 17, 2024
@sideshowbarker sideshowbarker changed the title How to build a new feature for the web platform — and make it a success with developers Discuss: How to build a new feature for the web platform — and make it a success with developers Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal track: Feature lifecycle
Projects
Status: No status
Development

No branches or pull requests

2 participants