Web security docs for MDN

[wbamberg]

Session description

At the Secure the Web Forward workshop in 2023, writers from Open Web Docs led a discussion about the state of web security docs on MDN. One outcome from this was that OWD would draft an outline for some improved security documentation for MDN, which would be written in 2024.

We've now written up a draft outline and it's had some internal review: https://docs.google.com/document/d/1p1GtjmTd1uQrO2PRb_uUflAfQpEsfs7hBaopYeuoPMM/edit, and we're ready for some more extensive review of the outline before we start writing docs.

We're very keen on finding security experts to collaborate with us on this project, both in these early stages as we scope the project, and for detailed technical review of documents as we write them.

In this session, we'll present the draft outline, discuss any feedback, and next steps, which we hope will be making a start on the documentation!

Session goal

Review MDN web security docs outline proposal

Session type

Breakout (Default)

Additional session chairs (Optional)

No response

IRC channel (Optional)

#mdn-security

Other sessions where we should avoid scheduling conflicts (Optional)

#20, #22

Instructions for meeting planners (Optional)

I'd prefer this to be scheduled not earlier than 4pm UTC.

Agenda (link or inline) (Optional)

• Present security docs outline
• Discuss any questions that come up
• Propose next steps for the project
• Slides: https://wbamberg.github.io/web-security-w3c-breakouts-march-2024/

Link to calendar (Optional)

Calendar entry

Meeting materials (Optional)

• Minutes
• Recording

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

[wbamberg]

Thanks to everyone who attended this session. We're going to continue planning and writing web security docs on MDN, and anyone who would like to help review and/or collaborate on this work is invited to participate:

• on GitHub, through the main project issue for the work and any child issues created from it: Web security docs for MDN openwebdocs/project#198
• in the #security channel of the W3C community Slack instance: https://www.w3.org/wiki/Slack
• possibly, in a new W3C Community Group: Cross-organization group to take a holistic approach to security on the Web secure-the-web-forward-workshop#42