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 Reviews Guideline"

From OWASP
Jump to: navigation, search
(→‎How can you contribute)
Line 28: Line 28:
 
We need regular or season reviewers to help us evaluate projects.
 
We need regular or season reviewers to help us evaluate projects.
  
 +
This is how you can help us evaluate the health of a project
 +
*Check the criteria that applies for each project type here:
 +
*Follow the criteria and do some research
 +
*Create a new Google sheet
 +
*Fill in the sheet. Try to add to your report also some print screens, hyperlinks, in other words how did you came to the conclusions and findings in the comments sections. It is very important that you can sustain the findings provided in your report sheet 
 +
*share the sheet through the Project task force mailing list
 +
 +
Quality of a Code/Tool projects:
 +
This kind of evaluation requires more work. It is necessary to download and install the project. The criteria to evaluate the minim quality of a project is very simple:
 +
 +
===For Code and Tools===
 +
For projects holding Flagship status, we closely monitor their health every 6 months on the following, among other key indicators:
 +
*Can the project be built correctly?
 +
*Does the project has any activity(commits) in the last 6 months?
 +
*Does the project had any releases in the last 6 months?
 +
*Has the project leaders updated his wiki or website to reflect latest releases?
 +
 +
===For Documentation===
 +
For this part, we are working on the development of an adequate assessment criteria
 +
The following is a draft of the new process proposal: [[https://www.owasp.org/index.php/File:Qualitative_and_Quantitative_Content_Audit.pdf Proposal for Reviewing OWASP Document projects]]
  
  

Revision as of 12:06, 21 August 2015

OWASP Project Header.jpg

Purpose

Project Reviews is a process within OWASP to help evaluate the health and quality of OWASP projects. The evaluation is based on a defined criteria which attempts to find out the progress and at which stage development the projects are.


Background

Projects are divided in 3 main categories:

  • Code
  • Tools
  • Documentation

These are the 3 main development classifications

  • Incubators
  • LAB
  • Flagship


How can you contribute

We need regular or season reviewers to help us evaluate projects.

This is how you can help us evaluate the health of a project

  • Check the criteria that applies for each project type here:
  • Follow the criteria and do some research
  • Create a new Google sheet
  • Fill in the sheet. Try to add to your report also some print screens, hyperlinks, in other words how did you came to the conclusions and findings in the comments sections. It is very important that you can sustain the findings provided in your report sheet
  • share the sheet through the Project task force mailing list

Quality of a Code/Tool projects: This kind of evaluation requires more work. It is necessary to download and install the project. The criteria to evaluate the minim quality of a project is very simple:

For Code and Tools

For projects holding Flagship status, we closely monitor their health every 6 months on the following, among other key indicators:

  • Can the project be built correctly?
  • Does the project has any activity(commits) in the last 6 months?
  • Does the project had any releases in the last 6 months?
  • Has the project leaders updated his wiki or website to reflect latest releases?

For Documentation

For this part, we are working on the development of an adequate assessment criteria The following is a draft of the new process proposal: [Proposal for Reviewing OWASP Document projects]


What is XXX?

OWASP XXX provides:

  • xxx
  • xxx


Presentation

Link to presentation



Team Project Review

Johanna Curiel Timo Goosen Minur Abbas Naderi


Related Projects


Openhub

Quick Download

  • Link to page/download

Email List

Project Email List

News and Events

  • [20 Nov 2013] News 2
  • [30 Sep 2013] News 1


In Print

This project can be purchased as a print on demand book from Lulu.com


Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files CODE.jpg
Q1
A1
Q2
A2

Volunteers

XXX is developed by a worldwide team of volunteers. The primary contributors to date have been:

  • xxx
  • xxx

Others

  • xxx
  • xxx

As of XXX, the priorities are:

  • xxx
  • xxx
  • xxx

Involvement in the development and promotion of XXX is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

  • xxx
  • xxx


PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
pending
last reviewed release
pending


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=Project_Reviews_Guideline&oldid=199329"