You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Session to talk about how we document web technologies and how we could create more positive feedback loops between specifications and technical docs (on MDN, and generally).
Session goal
Get technical writers and specification authors talking and discuss setting up a space where we could meet more frequently.
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.
Session description
Session to talk about how we document web technologies and how we could create more positive feedback loops between specifications and technical docs (on MDN, and generally).
Session goal
Get technical writers and specification authors talking and discuss setting up a space where we could meet more frequently.
Collect feedback on the idea of setting up a W3C Documentation Community Group (Docs CG) as outlined in
https://docs.google.com/document/d/1rLt1wT_y7OF9VINVGFj9U5x2C_z9_3aZeOtMh-p_Qf8/edit
Additional session chairs (Optional)
No response
IRC channel (Optional)
#web-platform-doc
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Instructions for meeting planners (Optional)
I'd prefer this to be scheduled not earlier than 4pm UTC.
Agenda for the meeting.
Links to calendar
The text was updated successfully, but these errors were encountered: