Projects/OWASP X5s Project/Releases/x5s v1.0.1/Assessment - Revision history

Paulo Coimbra at 20:19, 1 December 2010

2010-12-01T20:19:32Z

Paulo Coimbra at 20:56, 3 November 2010

2010-11-03T20:56:26Z

Paulo Coimbra at 20:53, 3 November 2010

2010-11-03T20:53:26Z

Sandra Paiva: Created page with 'Click here to return to project's main page
== Stable Release Review of the OWASP X5s Project - x5s v1.0.1 == ==== Project Leader for …'

2010-10-13T17:41:37Z

Created page with 'Click here to return to project's main page == Stable Release Review of the OWASP X5s Project - x5s v1.0.1 == ==== Project Leader for …'

New page

[[:OWASP X5s Project|Click here to return to project's main page]] 

== Stable Release Review of the OWASP X5s Project - x5s v1.0.1 ==

==== Project Leader for this Release ====
'''''[[User:Chrisweber|Chris Weber]]'s Pre-Assessment Checklist:'''''

{{ Pre-Assessment Questions - Tools
| 1. Is this release associated with a project containing at least the [[Assessing_Project_Health#Project_Wiki_Page_Minimal_Content|Project Wiki Page Minimum Content]] information?
= (answer #1)

| 2. Is your tool licensed under an open source license?
= (answer #2)

| 3. Is the source code and any documentation available in an online project repository?
= (answer #3)

| 4. Is there working code?
= (answer #4)

| 5. Is there a roadmap for this project release which will take it from Alpha to Stable release?
= (answer #5)

| 6. Are the Alpha pre-assessment items complete?
= (answer #6)

| 7. Is there an installer or stand-alone executable?
= (answer #7)

| 8. Is there user documentation on the OWASP project wiki page?
= (answer #8)

| 9. Is there an "About box" or similar help item which lists the following?
= (answer #9)

| 10. Is there documentation on how to build the tool from source including obtaining the source from the code repository?
= (answer #10)

| 11. Is the tool documentation stored in the same repository as the source code?
= (answer #11)

| 12. Are the Alpha and Beta pre-assessment items complete?
= (answer #12)

| 13. Does the tool include documentation built into the tool?
= (answer #13)

| 14. Does the tool include build scripts to automate builds?
= (answer #14)

| 15. Is there a publicly accessible bug tracking system?
= (answer #15)

| 16. Have any existing limitations of the tool been documented?
= (answer #16)

}}

==== First Reviewer ====
'''''[[User:Name|TBD]]'s Review:''''' 
Ideally, reviewers should be an existing OWASP project leader or chapter leader.

{{ Assessment Questions - Tools

| 1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?
=

| 2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?
=

|3. Does the tool have an “About box” or similar help item which allows the end user to get an overview of the state of this tool? Is this information readily available and easy to find?
=

| 4. Does the documentation on building the source provide the necessary information and detail to allow someone to build the tool? Is there sufficient detail and information for the target user? Is there any domain specific knowledge that is assumed and not provided?
=

| 5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?
=

| 6. Is there anything missing that is critical enough to keep the release at a alpha quality?
=

| 7. Does the tool substantially address the application security issues it was created to solve?
=

| 8. Is the tool reasonably easy to use?
=

| 9. Does the documentation meet the needs of the tool users and is easily found?
=

| 10. Do the build scripts work as expected? Can you build the tool? The goal is a “One-click” build.
=

| 11. Is the bug tracking system usable? Is it hosted at the same place as the source code? (e.g. Google Code, Sourceforge)
=

| 12. Have you noted any limitations of the tool that are not already documented by the project lead.
=

| 13. Would you consider using this tool in your day to day work assuming your professional work includes a reason to use this tool? Why or why not?
=

| 14. What, if anything, is missing which would make this a more useful tool? Is what is missing critical enough to keep the release at a beta quality?
=

}}

==== Second Reviewer ====
'''''[[User:Name|TBD]]'s Review:''''' 
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.

{{ Assessment Questions - Tools

| 1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?
=

| 2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?
=

|3. Does the tool have an “About box” or similar help item which allows the end user to get an overview of the state of this tool? Is this information readily available and easy to find?
=

| 4. Does the documentation on building the source provide the necessary information and detail to allow someone to build the tool? Is there sufficient detail and information for the target user? Is there any domain specific knowledge that is assumed and not provided?
=

| 5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?
=

| 6. Is there anything missing that is critical enough to keep the release at a alpha quality?
=

| 7. Does the tool substantially address the application security issues it was created to solve?
=

| 8. Is the tool reasonably easy to use?
=

| 9. Does the documentation meet the needs of the tool users and is easily found?
=

| 10. Do the build scripts work as expected? Can you build the tool? The goal is a “One-click” build.
=

| 11. Is the bug tracking system usable? Is it hosted at the same place as the source code? (e.g. Google Code, Sourceforge)
=

| 12. Have you noted any limitations of the tool that are not already documented by the project lead.
=

| 13. Would you consider using this tool in your day to day work assuming your professional work includes a reason to use this tool? Why or why not?
=

| 14. What, if anything, is missing which would make this a more useful tool? Is what is missing critical enough to keep the release at a beta quality?
=

}}

__NOTOC__
<headertabs/>

@@ Line 1: / Line 1: @@
-<small>[[:OWASP X5s Project|Click here to return to project's main page]]</small><br>
+<small>[[OWASP Fiddler Addons for Security Testing Project|Click here to return to project's main page]]</small><br>
-== Stable Release Review of the OWASP X5s Project - x5s v1.0.1 ==
+== Stable Release Review of the OWASP X5s Project - [[Projects/OWASP X5s Project/Releases/x5s v1.0.1|x5s v1.0.1]] ==
 ==== Project Leader for this Release ====

@@ Line 4: / Line 4: @@
 ==== Project Leader for this Release ====
-'''''[[User:Chrisweber|Chris Weber]]'s Pre-Assessment Checklist:'''''
+'''''[[User:ChrisWeber|Chris Weber]]'s Pre-Assessment Checklist:'''''
 {{ Pre-Assessment Questions - Tools

@@ Line 64: / Line 64: @@
 | 1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?
+= (answer #1)
 | 2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?
+= (answer #2)
 |3. Does the tool have an “About box” or similar help item which allows the end user to get an overview of the state of this tool? Is this information readily available and easy to find?
+= (answer #3)
 | 4. Does the documentation on building the source provide the necessary information and detail to allow someone to build the tool? Is there sufficient detail and information for the target user? Is there any domain specific knowledge that is assumed and not provided?
+= (answer #4)
 | 5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?
+= (answer #5)
 | 6. Is there anything missing that is critical enough to keep the release at a alpha quality?
+= (answer #6)
 | 7. Does the tool substantially address the application security issues it was created to solve?
+= (answer #7)
 | 8. Is the tool reasonably easy to use?
+= (answer #8)
 | 9. Does the documentation meet the needs of the tool users and is easily found?
+= (answer #9)
 | 10. Do the build scripts work as expected? Can you build the tool? The goal is a “One-click” build.
+= (answer #10)
 | 11. Is the bug tracking system usable? Is it hosted at the same place as the source code? (e.g. Google Code, Sourceforge)
+= (answer #11)
 | 12. Have you noted any limitations of the tool that are not already documented by the project lead.
+= (answer #12)
 | 13. Would you consider using this tool in your day to day work assuming your professional work includes a reason to use this tool? Why or why not?
+= (answer #13)
 | 14. What, if anything, is missing which would make this a more useful tool? Is what is missing critical enough to keep the release at a beta quality?
+= (answer #14)
 }}
@@ Line 114: / Line 114: @@
 | 1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?
+= (answer #1)
 | 2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?
+= (answer #2)
 |3. Does the tool have an “About box” or similar help item which allows the end user to get an overview of the state of this tool? Is this information readily available and easy to find?
+= (answer #3)
 | 4. Does the documentation on building the source provide the necessary information and detail to allow someone to build the tool? Is there sufficient detail and information for the target user? Is there any domain specific knowledge that is assumed and not provided?
+= (answer #4)
 | 5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?
+= (answer #5)
 | 6. Is there anything missing that is critical enough to keep the release at a alpha quality?
+= (answer #6)
 | 7. Does the tool substantially address the application security issues it was created to solve?
+= (answer #7)
 | 8. Is the tool reasonably easy to use?
+= (answer #8)
 | 9. Does the documentation meet the needs of the tool users and is easily found?
+= (answer #9)
 | 10. Do the build scripts work as expected? Can you build the tool? The goal is a “One-click” build.
+= (answer #10)
 | 11. Is the bug tracking system usable? Is it hosted at the same place as the source code? (e.g. Google Code, Sourceforge)
+= (answer #11)
 | 12. Have you noted any limitations of the tool that are not already documented by the project lead.
+= (answer #12)
 | 13. Would you consider using this tool in your day to day work assuming your professional work includes a reason to use this tool? Why or why not?
+= (answer #13)
 | 14. What, if anything, is missing which would make this a more useful tool? Is what is missing critical enough to keep the release at a beta quality?
+= (answer #14)
 }}

Projects/OWASP X5s Project/Releases/x5s v1.0.1/Assessment - Revision history

Paulo Coimbra at 20:19, 1 December 2010

Paulo Coimbra at 20:56, 3 November 2010

Paulo Coimbra at 20:53, 3 November 2010

Sandra Paiva: Created page with 'Click here to return to project's main page == Stable Release Review of the OWASP X5s Project - x5s v1.0.1 == ==== Project Leader for …'

Sandra Paiva: Created page with 'Click here to return to project's main page
== Stable Release Review of the OWASP X5s Project - x5s v1.0.1 == ==== Project Leader for …'