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 "Project Information:template Source Code Review OWASP Projects - 50 Review - First Reviewer - C"

From OWASP
Jump to: navigation, search
m
 
(2 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Source Code Review OWASP Projects|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
 
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Source Code Review OWASP Projects|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
#No projects submitted to Fortify Open Source Review, as Fortify is updating the application.
+
#No projects submitted to Fortify Open Source Review (FOR), as Fortify is updating the application.
#"Preliminary Workflow" has been reviewed.
+
#"Preliminary Workflow" will probably need to be revised after a few projects have been submitted to FOR.
#"Project Creation Workflow" has been reviewed. This workflow assumes that the project already exists in accordance with how the Fortify Open Review (FOR) project operates. This workflow is designed more for auditors than developers.    
+
#"Project Creation Workflow" assumes that the project already exists in accordance with how the Fortify Open Source Review (FOR) project operates. This workflow will probably need to be revised after a few projects have been submitted to FOR.
 
  |-  
 
  |-  
 
  | style="width:25%; background:#7B8ABD" align="center"|  
 
  | style="width:25%; background:#7B8ABD" align="center"|  
Line 33: Line 33:
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
#With regard to the "Preliminary Workflow", it may be possible to simplify the workflow by taking out the "Is it a fixed version?" decision-point and configuring all projects as "continuous build". That may also allow a project to be re-started in the future without having to create a new project. It seems like this is more likely to happen with an open source project. It is not entirely clear if this workflow is supporting only the FOR process or also the OWASP process.
+
#With regard to the "Preliminary Workflow", it may be possible to simplify the workflow by taking out the "Is it a fixed version?" decision-point and configuring all projects as "continuous build". That may also allow a project to be re-started in the future without having to create a new project. It seems like this is more likely to happen with an open source project.
|}
 

Latest revision as of 20:20, 8 July 2008

Click here to return to the previous page.

50% REVIEW PROCESS

Project Deliveries & Objectives

OWASP Source Code Review OWASP-Projects Project's Deliveries & Objectives

QUESTIONS ANSWERS

1. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please exemplify writing down those of them that haven't been realised.

  1. No projects submitted to Fortify Open Source Review (FOR), as Fortify is updating the application.
  2. "Preliminary Workflow" will probably need to be revised after a few projects have been submitted to FOR.
  3. "Project Creation Workflow" assumes that the project already exists in accordance with how the Fortify Open Source Review (FOR) project operates. This workflow will probably need to be revised after a few projects have been submitted to FOR.

2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.

  1. Team of workflow reviewers finalized (100%)
  2. Preliminary Workflow (100%)
  3. Project Creation Workflow (100%)
  4. Projects Submitted (0%)

3. Please do use the right hand side column to provide advice and make work suggestions.

  1. With regard to the "Preliminary Workflow", it may be possible to simplify the workflow by taking out the "Is it a fixed version?" decision-point and configuring all projects as "continuous build". That may also allow a project to be re-started in the future without having to create a new project. It seems like this is more likely to happen with an open source project.