[GPC] [Owasp-topten] FW: OWASP ASVS Release version published!

Matt Tesauro mtesauro at gmail.com
Thu Jun 4 08:55:33 EDT 2009


Mike:  Great stuff.  Now we need to line up 2 reviewers.  Any
suggestions you may have please forward them to Paulo.

Paulo: Perhaps we could ask Leo or Pravir to be one of the reviewers as
they are rather well versed in OWASP document projects.

-- Matt Tesauro
OWASP Live CD Project Lead
http://www.owasp.org/index.php/Category:OWASP_Live_CD_Project
http://AppSecLive.org - Community and Download site

Boberski, Michael [USA] wrote:
>  Alpha Release Document Criteria
> 
> Pre-Assessment Checklist:
> 
>    1. Is your document licensed under a free and open license? (see
> Project Licensing section of the Guidelines for OWASP Projects)
> 
> [MIKE] Yes. Creative Commons Attribution ShareAlike 3.0. 
> 
>    2. Is the document available as a PDF (Portable Document Format) and
> an editable (.Doc) format on the project site?
> 
> [MIKE] Yes.
> https://www.owasp.org/index.php/Category:OWASP_Application_Security_Veri
> fication_Standard_Project#tab=Download
> 
>    3. Are all articles that constitute the project properly tagged
> within project category and available from main project Wiki page?
> 
> [MIKE] Yes.
> http://www.owasp.org/index.php/Category:OWASP_Application_Security_Verif
> ication_Standard_Project#Articles_Below_-_More_About_ASVS_and_Using_It
> 
>    4. Is there a roadmap for this project release which will take it
> from Alpha to Stable release? 
> [MIKE] Yes.
> https://www.owasp.org/index.php/Category:OWASP_Application_Security_Veri
> fication_Standard_Project#tab=About
> 
> 
> Beta Release Document Criteria
> 
> Pre-Assessment Checklist:
> 
>    1. Are the Alpha pre-assessment items complete?
> [MIKE] Yes.
>    2. Are all document contents (articles) present and listed on the
> OWASP project wiki page?
> [MIKE] Yes.
>    3. Is there an "About This Document" section in the document listing:
>          1. Document Name
>          2. Author(s)
>          3. Contributor(s)
>          4. Contact email address
>          5. Current version and/or release date
>          6. Project's web page address 
> 
> [MIKE] Yes. Everything's hyperlinked as well.
> 
> Reviewer Action Items:
> 
>    1. Does the document consider the OWASP Writing Style?
> 
> [MIKE] Yes.
> 
>    2. Do contents from wiki articles match download-able documents? (PDF
> and .doc versions)
> 
> [MIKE] Yes. See link above.
> 
>    3. Does the document have an "About This Document" section which
> allows the end user to get an overview of the state of the document?
> 
> [MIKE] Yes.
> https://www.owasp.org/index.php/Category:OWASP_Application_Security_Veri
> fication_Standard_Project#tab=FAQ
> 
>    4. How completely does the release address the goal of the project?
> Is the overall document complete in structure and organization? Are any
> missing or incomplete sections critical enough to keep the document at
> an Alpha quality level? 
> 
> [MIKE] 100%. No issues.
> 
> Stable Release Document Criteria
> 
> Pre-Assessment Checklist:
> 
>    1. Are the Alpha and Beta pre-assessment items complete?
> 
> [MIKE] Yes. See above.
> 
>    2. Have any limitations been documented?
> 
> [MIKE] Yes. It is specific to Web Apps, does not cover e.g. Web
> Services. Other limitations about scope can be found in for example the
> Foreword inside the document.
> 
>    3. Does the document considering OWASP Writing Style and OWASP
> Template for Docs?
> 
> [MIKE] Yes.
> 
>    4. Is there a one sheet overview document about the project?
> 
> [MIKE] Yes. See above.
> 
>    5. Is the document in a format which can be converted to an OWASP
> book? (books are currently via Lulu.com) 
> 
> [MIKE] Yes. A request to Larry for help to upload has already been sent.
> 


More information about the Global-projects-committee mailing list