This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Project Reviewers Database"
m (Unprotected "OWASP Project Reviewers Database") |
|||
Line 87: | Line 87: | ||
{{:GPC_Project_Assessment/OWASP Secure Coding Practices - Quick Reference Guide | OWASP_Project_Assessment/Row}} | {{:GPC_Project_Assessment/OWASP Secure Coding Practices - Quick Reference Guide | OWASP_Project_Assessment/Row}} | ||
{{:GPC Project Assessment/OWASP Secure Coding Practices - Quick Reference Guide - SCP v2 | OWASP_Project_Assessment/Row}} | {{:GPC Project Assessment/OWASP Secure Coding Practices - Quick Reference Guide - SCP v2 | OWASP_Project_Assessment/Row}} | ||
+ | {{:GPC Project Assessment/OWASP HTTP Post Tool - HttpDosTool3 | OWASP_Project_Assessment/Row}} | ||
|} | |} | ||
__NOTOC__ | __NOTOC__ | ||
<headertabs/> | <headertabs/> |
Latest revision as of 22:38, 26 November 2010
Reviewers Drive Overview
Reviewers drive's goal and methodology explanation |
You may or may not have noticed, but as of the assessment criteria v2, each release will require at least three reviews as it moves from beta to stable. This reintroduces problems we have had in the past finding reviewers for these projects. In addition, at least one of these reviewers should be from the GPC. Based on the last GPC call on Monday, November 23, I am going to spear-head a drive for centralizing the collection and recruitment of OWASP Project reviewers. The general idea for this is to create a pool of known-good persons that can be pulled in when a reviewer is not supplied by the project lead. There are several phases I am planning to implement in order to streamline this.
These are merely early thoughts of how I’d like to see this formulated. Feedback is, as always, welcome. Brad Causey (OWASP Global Committee Member) http://globalprojectscommittee.wordpress.com/2009/11/27/new-drive-for-project-reviewers/ |
Project Reviewers/Volunteers
Volunteer Reviewer Identification, Interests and Commitments | ||||
Name | Projects I would be interested in reviewing | Projects currently reviewing | Projects reviewed | |
view edit | Paulo Coimbra (as an example) @ | Code Review, Testing and Firewalls. | ||
view edit | Jocelyn Aubert @ | Best practices, Code Review, Testing, OWASP Secure Coding Practices - Quick Reference Guide | N/A | N/A |
view edit | James McGovern @ | Anything of interest to CIO, CISO and Chief Architect audience | N/A | N/A |
view edit | Ludovic Petit @ | OWASP Secure Coding Practices - Quick Reference Guide, Top Ten, and same as James | N/A | N/A |
view edit | Michael Scovetta @ | OWASP Secure Coding Practices - Quick Reference Guide, best practices, code review, templates | N/A | N/A |
view edit | Sherif Koussa @ | Secure Coding Guidelines, Secure Code Reviews, Secure Development Lifecycle | N/A | N/A |
view edit | Sébastien Gioria @ | CodeReview, Testing, Top10, ASVS, Education materials | N/A | N/A |
view edit | Aung Khant @ | "OWASP Secure Coding Practices Quick Reference Guide", "OWASP Testing Project" | N/A | N/A |
view edit | Gandhi Aryavalli @ | Code Compliance, Static Secure Code Analysis, Top 10, Reverse Engineering, Dynamic Analysis, Malware Research, Network Enumerations, or anything of interest of OWASP in Information Security that makes an impact in bringing awareness to IT in the field of Security Science | N/A | N/A |
view edit | Volunteer 10 | N/A | N/A | |
view edit | Volunteer 11 | N/A | N/A | |
view edit | Volunteer 12 | N/A | N/A | |
view edit | Volunteer 13 | N/A | N/A | |
view edit | Volunteer 14 | N/A | N/A | |
view edit | Volunteer 15 | N/A | N/A |