Tracking spec maintenance
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
– Central European Summer Time
Status:
Confirmed
Location:
Magnolia - Low Level
Participants:
Elika Etemad, Dominique Hazaël-Massieux, Yen-Lin Huang, Michael Jackson, Xueyuan Jia, Chris Lilley, Florian Rivoal, Florian Scholz, Chris Wilson, Jeffrey Yasskin
Big meeting:
TPAC 2023 (Calendar)

The web platform includes lots of specifications, and we don't have an easy way of distinguishing the ones that are adequately maintained, vs the ones that need more investment.

Some considerations include (but aren't limited to):

  • Stable specs might not need much investment for long periods of time.

  • We should include specs that have only one implementation, so that:

    • If a group starts showing interest in writing a second implementation, their issues should be very visible.

  • Specs should triage issues fairly quickly, but it could be ok for low priority issues to sit around.

  • We probably need a consistent set of labels.

  • Chrome needs to do a lot of the maintenance, but the whole community should buy into the system and see the results.

Future discussion will happen on the spec-prod@w3.org mailing list.

Agenda

 View agenda

Chairs:
Jeffrey Yasskin

Description:
The web platform includes lots of specifications, and we don't have an easy way of distinguishing the ones that are adequately maintained, vs the ones that need more investment.

Some considerations include (but aren't limited to):

  • Stable specs might not need much investment for long periods of time.

  • We should include specs that have only one implementation, so that:

    • If a group starts showing interest in writing a second implementation, their issues should be very visible.

  • Specs should triage issues fairly quickly, but it could be ok for low priority issues to sit around.

  • We probably need a consistent set of labels.

  • Chrome needs to do a lot of the maintenance, but the whole community should buy into the system and see the results.

Future discussion will happen on the spec-prod@w3.org mailing list.

Goal(s):
Sketch a plan to sustainably identify specs that are falling behind on their maintenance needs

Materials:

Track(s):

  • getting work done

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.