Incubation: the on ramp to new work

[cwilso]

Session description

The process of incubation, and some of its parameters, are not currently well-defined at W3C. I'd like to gather perspectives to further the work on Incubation in the AB (https://github.com/w3c/AB-memberonly/blob/master/documents/Incubation.md).

Some provoking questions to explore:

• How should incubation work?
• At what stage of "doneness" should work move from an incubation venue to a working group?
• How should an incubation group be communicating their work to a broader venue to ease acceptance as a WG deliverable?
• What expectation of incubation should there be before work is accepted into a WG, or into its charter?
• What best practices should we define for referring to incubations?

Session goal

Gather input and perspectives to further the AB work on improving incubation process

Session type

Breakout (Default)

Additional session chairs (Optional)

No response

IRC channel (Optional)

incubation

Other sessions where we should avoid scheduling conflicts (Optional)

19, #20, #22

Instructions for meeting planners (Optional)

This may be related to #22.

Agenda (link or inline) (Optional)

No response

Link to calendar (Optional)

Calendar entry

Meeting materials (Optional)

• Minutes

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[tidoust]

@cwilso re. "This may be related to #22", I will indeed talk a little bit about a possible signal that could inform transition out of incubation during the breakout on Web features, Baseline status, and standardization signals. Now, that possible signal is more to identify proposals that should probably have transitioned out of incubation some time ago, than proposals that start to look "done enough" (see slide 15 for signals that could be computed automatically).

The WebDX CG is also starting to look into collecting additional developer signals but that work has barely started. There may other data points that could be worth tracking to inform incubation!