Security/B2G/2013 20 6
From MozillaWiki
News
Q3 goals
https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ap-jgPe0UrMhdC1OZ0VoTEc1UnhzT2ljRnQ3b19XTFE#gid=1
Security Assurance Program *new* https://docs.google.com/a/mozilla.com/document/d/1X09wPgr_XD0JTC8gsBbbgnACN8e7ZLS3MTxy7V5jygo/edit#heading=h.vlxfrt9ld4yu TLDR: - more targeted reviews - more penetration testing - testing/certification of release builds as a whole https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtVT90hlMtdSdEd4TVVjWXNfU3ctMlVhWFRrWkpweVE#gid=16 1.2 Reviews https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Ap-jgPe0UrMhdHNaNUFrQS00Q09FbUFZUmQ5eThpOFE#gid=0 b2g email sanitizer: https://bugzilla.mozilla.org/show_bug.cgi?id=783958
Weekly goals
[dchan] - need to finish writing gecko review guide
Goal Status Updates
1.2 code (?) freeze probably happening in october / sandbox planned to be present for that release
https://bugzilla.mozilla.org/show_bug.cgi?id=845738#c3 (supervisor process model updates)
[cr] working on reviewer checklist
agreed with Marketplace folks on dual approach:
1. general bullet point list in wiki
quicker updates for incidence response
like https://wiki.mozilla.org/Marketplace/Reviewers/Apps/Testing#Testing_Procedure_-_.2APrivileged.2A_Packaged_Apps
Marketplace team asked for revamp, comments on this?)
2. more detail per permission in the reviewer tool
Where to put our reviewer guidelines