canmove, Confirmed users
637
edits
Security/Reviews/: Difference between revisions
Jump to navigation
Jump to search
Filled in a few addition details about the request process
m (→Process: reversing the order of filling in the form and sending the request mail) |
(Filled in a few addition details about the request process) |
||
| Line 3: | Line 3: | ||
=Process= | =Process= | ||
# Make a copy of the [https://docs.google.com/document/d/1GTXYJiDM9U8bmmg_93uQkF0tVzO3R1rVACeivMCWjP8/edit security review template] and fill in the sections. | # Make a copy of the [https://docs.google.com/document/d/1GTXYJiDM9U8bmmg_93uQkF0tVzO3R1rVACeivMCWjP8/edit security review template] and fill in the sections. | ||
# Send an email to [mailto:secreview@mozilla.com secreview@mozilla.com] to request a review, linking to the filled-in request | #* The first section of the template is not asking you to create new documentation; rather, we assume you have done this level of planning and will be able to share links to existing documents. If you don't have this documentation your feature may not be defined well enough to conduct a productive review. Send us mail and we can talk about it: maybe you need something less formal than a "review". | ||
#* Please share the completed request document with secreview@mozilla.com and grant Editor access. We will use this document to take meeting notes. | |||
# Send an email to [mailto:secreview@mozilla.com secreview@mozilla.com] to request a review, linking to the filled-in request document | |||
# Feature EPM or dev lead will schedule a meeting to review details and discuss risks | # Feature EPM or dev lead will schedule a meeting to review details and discuss risks | ||
# Follow-up items: Fixing issues, and optionally [[Security/Testing|Security Testing]] | # Follow-up items: Fixing issues, and optionally [[Security/Testing|Security Testing]] | ||