Assessing Project Releases - Revision history

Paulo Coimbra: Removed "This is a DRAFT page still under review by the Global Projects Committee"

2009-07-02T14:56:34Z

Removed "This is a DRAFT page still under review by the Global Projects Committee"

Paulo Coimbra: /* Prerequisites for Project Release Assessment */ Replaced "Quality" by "Stable"

2009-06-23T15:03:23Z

‎Prerequisites for Project Release Assessment: Replaced "Quality" by "Stable"

Paulo Coimbra at 16:41, 22 June 2009

2009-06-22T16:41:36Z

Paulo Coimbra: /* Quality Levels */

2009-05-12T10:59:50Z

‎Quality Levels

Paulo Coimbra: /* Prerequisites for Project Release Assessment */

2009-05-07T15:09:43Z

‎Prerequisites for Project Release Assessment

Paulo Coimbra: /* Prerequisites for Project Assessment */

2009-05-07T15:04:52Z

‎Prerequisites for Project Assessment

Mtesauro: Updated to reflect 2009-05-01 GPC meeting

2009-05-04T18:24:38Z

Updated to reflect 2009-05-01 GPC meeting

Mtesauro: /* Quality Levels */ Wording change based on input from Jason Li

2009-04-28T14:21:32Z

‎Quality Levels: Wording change based on input from Jason Li

Mtesauro: /* Prerequisites for Project Assessment */ Added note about larger projects and reviewers

2009-04-27T18:43:45Z

‎Prerequisites for Project Assessment: Added note about larger projects and reviewers

Leocavallari at 15:04, 27 April 2009

2009-04-27T15:04:49Z

← Older revision		Revision as of 14:56, 2 July 2009
Line 1:		Line 1:
	[[Category:OWASP Project Assessment]]		[[Category:OWASP Project Assessment]]
−
−	~~This is a DRAFT page still under review by the [[Global Projects Committee]]~~

	This page is maintained by the [[Global Projects Committee]] to help assist Project Leaders with information about successfully running an OWASP Project. It will be updated from time to time, and changes will be discussed and announced on the OWASP-Leaders list.		This page is maintained by the [[Global Projects Committee]] to help assist Project Leaders with information about successfully running an OWASP Project. It will be updated from time to time, and changes will be discussed and announced on the OWASP-Leaders list.

@@ Line 34: / Line 34: @@
 * Ideally, reviewers should be an existing OWASP project leader or chapter leader.
 * If the project lead is unable to find the required reviewer(s), the Global Projects Committee can assist in identifying reviewers for the project.
-* It is recommended that an OWASP board member or Global Projects Committee member be the second reviewer on Quality releases. The board has the initial option to review the project, followed by the Global Projects Committee.
+* It is recommended that an OWASP board member or Global Projects Committee member be the second reviewer on Stable releases. The board has the initial option to review the project, followed by the Global Projects Committee.
 * The Global Projects Committee confirms the assignment of reviewers to a project.
 * For special cases (e.g. large documents), multiple reviewers may be utilized to break the review work into smaller units.  The over-riding principal is that one set of eye balls will review for Beta and two sets of eye balls will review for Quality.  For example, a large project 4 reviewers could be used to do the Stable quality review were each reviewer would be responsible for reviewing approximately 1/2 of the content where 4 x 1/2 = 2.

@@ Line 37: / Line 37: @@
 * The Global Projects Committee confirms the assignment of reviewers to a project.
 * For special cases (e.g. large documents), multiple reviewers may be utilized to break the review work into smaller units.  The over-riding principal is that one set of eye balls will review for Beta and two sets of eye balls will review for Quality.  For example, a large project 4 reviewers could be used to do the Stable quality review were each reviewer would be responsible for reviewing approximately 1/2 of the content where 4 x 1/2 = 2.
 ===Release Assessment Criteria===

@@ Line 7: / Line 7: @@
 === Quality Levels===
-For project releases, OWASP has created a criteria with three designations of quality:  Alpha, Beta and Stable releases.  As project releases move up the quality ladder from Alpha to Beta and finally to a Stable release, the amount of rigor required increases. In general, the project lead will determine the goal quality level of their project and work towards fulfilling the criteria for that level. Once a project lead has completed the prerequisites and criteria for the goal level, they request that their project be reviewed. The quality level will determine who reviews the release and how those reviews occur.
+For project releases, OWASP has created a criteria with three designations of quality:  Alpha, Beta and Stable releases.  As project releases move up the quality ladder from Alpha to Beta and finally to a Stable release, the amount of rigour required increases. In general, the project lead will determine the goal quality level of their project and work towards fulfilling the criteria for that level. Once a project lead has completed the prerequisites and criteria for the goal level, they request that their project be reviewed. The quality level will determine who reviews the release and how those reviews occur.
 * Alpha release: The review consists of the Global Project Committee (GPC) verifying that the project pre-assessment checklist is complete. Alpha release projects are the easiest to achieve since anyone with a start on a solution to an application security problem can self assess their project against the pre-assessment checklist.

@@ Line 31: / Line 31: @@
 Notes on reviewers
-* Ideally, the project lead will suggest project reviewer(s).
+* Ideally, per project release, the project leader will propose the reviewer(s).
-* Ideally, reviewers should be an existing OWASP project lead or chapter leader.
+* Ideally, reviewers should be an existing OWASP project leader or chapter leader.
 * If the project lead is unable to find the required reviewer(s), the Global Projects Committee can assist in identifying reviewers for the project.
 * It is recommended that an OWASP board member or Global Projects Committee member be the second reviewer on Quality releases. The board has the initial option to review the project, followed by the Global Projects Committee.

@@ Line 20: / Line 20: @@
 * Reviewer Action Items were designed to require some significant time commitment from the reviewer since the questions are subjective and require a good deal of understanding and review of the project's release.
-===Prerequisites for Project Assessment===
+===Prerequisites for Project Release  Assessment===
 Depending on the quality level criteria, the project lead may have prerequisites to complete before the project release(s) can be assessed by the criteria below

@@ Line 7: / Line 7: @@
 === Quality Levels===
-For project releases, OWASP has established the assessment criteria with three designations of quality:  Alpha, Beta and Quality releases.  As project releases move up the quality ladder from Alpha to Beta and finally to a Quality release, the amount of rigor required increases. In general, the project lead will determine the goal quality level of their project and work towards fulfilling the criteria for that level. Once a project lead has completed the prerequisites and criteria for the goal level, they request that their project be reviewed. The quality level will determine who reviews the release and how those reviews occur.
+For project releases, OWASP has created a criteria with three designations of quality:  Alpha, Beta and Stable releases.  As project releases move up the quality ladder from Alpha to Beta and finally to a Stable release, the amount of rigor required increases. In general, the project lead will determine the goal quality level of their project and work towards fulfilling the criteria for that level. Once a project lead has completed the prerequisites and criteria for the goal level, they request that their project be reviewed. The quality level will determine who reviews the release and how those reviews occur.
-* Alpha release: The review consists of the Global Project Committee (GPC) verifying that the project pre-assessment checklist is complete. Alpha release projects are the easiest to achieve since anyone with a start on a solution to an application security problem can assess their project against the pre-assessment checklist.
+* Alpha release: The review consists of the Global Project Committee (GPC) verifying that the project pre-assessment checklist is complete. Alpha release projects are the easiest to achieve since anyone with a start on a solution to an application security problem can self assess their project against the pre-assessment checklist.
-* Beta release:  The project lead completes the pre-assessment checklist. Then, the review will first be conducted by the project's reviewer (more on this below). After the reviewer completes the reviewer action items, the GPC will validate the project's assessment.
+* Beta release:  The project lead completes the pre-assessment checklist. Then, the review will first be conducted by the project's reviewer (more on this below). After the reviewer completes the review of the release, the GPC will validate the project's review.
-* Quality release: The project lead completes the pre-assessment checklist. Then, the two project reviewers will complete their action items (more on this below). After the reviews are complete, the Global Projects Committee and OWASP Board will validate the project's review.
+* Stable release: The project lead completes the pre-assessment checklist. Then, the two project reviewers will complete their review of the release (more on this below). After the reviews are complete, the Global Projects Committee and OWASP Board will validate the project's review.
@@ Line 26: / Line 26: @@
 * Alpha release: No prerequisites.
 * Beta release: 1 reviewer is required.
-* Quality release: 2 reviewers are required. Second review has special requirements.
+* Stable release: 2 reviewers are required. Second review has special requirements.
@@ Line 32: / Line 32: @@
 * Ideally, the project lead will suggest project reviewer(s).
-* Ideally, reviewers should be an existing OWASP project lead or Chapter leader.
+* Ideally, reviewers should be an existing OWASP project lead or chapter leader.
 * If the project lead is unable to find the required reviewer(s), the Global Projects Committee can assist in identifying reviewers for the project.
 * It is recommended that an OWASP board member or Global Projects Committee member be the second reviewer on Quality releases. The board has the initial option to review the project, followed by the Global Projects Committee.
 * The Global Projects Committee confirms the assignment of reviewers to a project.
-* For special cases (e.g. large documents), multiple reviewers may be utilized to break the review work into smaller units.  The over-riding principal is that one set of eye balls will review for Beta and two sets of eye balls will review for Quality.  For example, a large project 4 reviewers could be used to do the Quality review were each reviewer would be responsible for reviewing approximately 1/2 of the content where 4 x 1/2 = 2.
+* For special cases (e.g. large documents), multiple reviewers may be utilized to break the review work into smaller units.  The over-riding principal is that one set of eye balls will review for Beta and two sets of eye balls will review for Quality.  For example, a large project 4 reviewers could be used to do the Stable quality review were each reviewer would be responsible for reviewing approximately 1/2 of the content where 4 x 1/2 = 2.
 ===Release Assessment Criteria===