Tracking spec maintenance

[jyasskin]

Session 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.

Session goal

Sketch a plan to sustainably identify specs that are falling behind on their maintenance needs

Additional session chairs (Optional)

No response

IRC channel (Optional)

#spec-maintenance

Who can attend

Anyone may attend (Default)

Session duration

60 minutes (Default)

Other sessions where we should avoid scheduling conflicts (Optional)

#3, #43, #58, #65

Estimated number of in-person attendees

Don't know (Default)

Instructions for meeting planners (Optional)

No response

Agenda, minutes, slides, etc. (Optional)

• Agenda
• Slides
• Minutes
• Brainstorming results
• Calendar