CG Specification Communication Enhancements

[ianbjacobs]

Session description

Our project to revamp the Community Group program includes improvements to communications about CG specifications. In this breakout session we will discuss our current thinking about the CG specification lifecycle.

An important part of improved communication includes clearer representation of status information and greater stylistics distinctions between CG specifications and Rec-track deliverables. We will share mockups and invite feedback.

We will also demo tooling for helping editors gather data that will be used to convey status information in specifications, and discuss ideas for maintenance of that data.

Session goal

Build support for enhanced CG specification lifecycle and gather feedback on mockups

Additional session chairs (Optional)

@dontcallmedom

Who can attend

Anyone may attend (Default)

Instructions for meeting planners (Optional)

Ideally before lunch on Wednesday.

IRC channel (Optional)

#council

Agenda for the meeting.

• Updates on CG spec lifecycle
• Seek feedback on mockups for CG specification changes
• Anticipated approach for gathering data used to communicate specification circumstances
• Planning for beta test of new styles (implemented in bikeshed and respec).

See our slides

Scheduling conflicts to avoid (For meeting planners only)

• Future of the Open Web #37
• Tell Us What's Wrong with the Process #13

Links to calendar

• Wednesday, 10:00 - 11:00

Meeting materials

• 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 TPAC breakouts organizers may update the description at any time, 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 TPAC breakouts organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.