Project Information:template OpenSign Server Project - 50 Review - First Reviewer - C

Click here to return to the previous page.

50% REVIEW PROCESS
Project Deliveries & Objectives	OWASP OpenSign Server 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.	Alpha Quality for Tools Agree to OWASP's open source license OK The "main" page for any OWASP tool must be on the OWASP website. OK This page must: o describe the tool, the project leader, contact info, and include all relevant links, including a download link for the code and the executable version, OK o includes a roadmap/guideline pointing out the steps to achieve the purpose of project. OK o include the Alpha Quality Tool project tag. (Which we still need to define), WHEN ACHIEVED o be placed at OWASP Project page. OK Have its code and any documentation in Googlecode, or Sourceforge. OK Mailing list for project created. OK Solves a core application security need. OK since selected for the OWASP SoC What has been done by the authors documents: server concept and architecture : to be completed, Alpha quality OK implementation: draft of the welcome page of the OpenSign Server Web Interface. code structure Summary The criteria for alpha quality of the OpenSign Projects have been met before the 2008.07.15
2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.	Alpha Quality: 100 %. Overall project: 50 % Software development: 30 %
3. Please do use the right hand side column to provide advice and make work suggestions.	Document sent to the authors, 1. week of July [1]