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 "Category:OWASP Project Process"

From OWASP
Jump to: navigation, search
Line 11: Line 11:
  
 
Step 1:  
 
Step 1:  
New Project Leader submits New Project Request Form it is logged in the system and a alert is sent  to the the Project Coordinator  
+
New Project Leader submits New Project Request Form it is logged in the system and an alert is sent  to the Project Coordinator  
  
 
Step 2:
 
Step 2:
New Project Request is received and reviewed by Project Coordinator for complete information it must contain the following information to qualify as a acceptable submission:
+
New Project Request is received and reviewed by Project Coordinator for complete information .It must contain the following information to qualify as an acceptable submission:
<insert criteria>
+
You will need to gather the following information together for your application:
 +
 
 +
*Project Name,
 +
*Project purpose / overview,
 +
*Project Roadmap,
 +
*Project links (if any) to external sites,
 +
*[[Guidelines_for_OWASP_Projects#Project_Licensing|Project License],]
 +
*Project Leader name,
 +
*Project Leader email address,
 +
*Project Leader wiki account - the username (you'll need this to edit the wiki),
 +
*Project Contributor(s) (if any) - name email and wiki account (if any),
 +
*Project Main Links (if any).
 +
==>For Documentation: A table of Contents
 +
==>For Code: A prototype hosted in an open source repository of your choice. Make sure it has read access.
 +
https://www.owasp.org/index.php/Category:OWASP_Project#tab=Starting_a_New_Project
  
 
Step 3:  
 
Step 3:  
If approved, The Project Coordinator notifies the Project Leader that the request has been received and at that time requests additional information if needed.
+
If all information is completed following the minimum criteria for Projects (Code/Tool/documentation), The Project Coordinator notifies the Project Leader that the request has been accepted, and at the same time notifies the Review team that a new project has been submitted, including al the information requested in the project criteria
  
 
Step 4:  
 
Step 4:  
Project Task Force or Projet Review Team Project reviews the New Project Request and makes a decision. Then, the Project Coordinator creates the wiki page for the new project using the Code/Tool/Documentation Templates with information submitted by the Project Leader
+
Project Coordinator proceeds to create a new Wiki page for the project including all the information sent by the project leader. project coordinator uses one of these project wiki template:
 +
*For Docs: https://www.owasp.org/index.php/OWASP_Documentation_Project_Template
 +
*For Code: https://www.owasp.org/index.php/OWASP_Code_Project_Template
 +
*For Tool:  https://www.owasp.org/index.php/OWASP_Tool_Project_Template
 +
Also Project coordinator creates a mailing list for the project leader and sets him as admin
  
 
Step 5:  
 
Step 5:  
Project Coordinator notifies Project Leader with wiki page link and instructions to complete the wiki page.
+
Project Coordinator notifies project leader and Review team about the created wiki page, providing the link to the wiki page.
 +
*Review team might provide comments for further improvement of the wiki page if necessary
 +
*Project leader should request a wiki account to be able to update his own wiki page after wards
  
 
Step 6:  
 
Step 6:  
New Project wiki page is marked Pending until Project Leader updates and completes the wiki page with all necessary criteria
+
Project coordinator updates the Wiki project inventory, Dashboard and open hub with the information regarding the new created project
  
 
Step 7:  
 
Step 7:  
Project Coordinator reviews and communicates with the Project Leader on completion.
+
Project is set in the agenda for monitoring over the next 3 months to check how has been developing
  
Step 8:
 
Project Coordinator emails the Project Leader after 7 days as a reminder to complete the  wiki page.
 
  
Step 9:
+
Step 8:
Project Coordinator reviews the wiki for completion and submits to the Project Task Force or NEW Project Review Team by email for review and approval to be added to the inventory.
+
Every 3 months, project co-ordinator monitors the activity on the wiki page for new updates and on the Openhub for commits and level of activity
 +
Findings are then reported on the Dashboard as comments
  
Step 10:  
+
Step 9:  
Once the project is approved by the Project Task Force  the Project Leader is notified that the new project has been added to the inventory
+
if the project has not been updated and has no activities after six months of creation, project coordinator sends an email to the project leader, CC: project review team regarding the lack of activity and asks for a feedback and status to see how has been developing.The findings are then updated on the dashboard.
  
Step 11:
+
Step 10:
Project Coordinator sets up mailing lists, project is marked in Sales Force as approved,  new project announcement in the next connector and adds to the inventory list.
+
Over the next 6 months the project is monitored again for activity. If no updates has occurred since its inception after 12 months, project is then set as inactive and project leader is notified about the status.
 +
Project coordinators updates the inventory setting the project under the 'inactive category'
 +
Dashboard is updated
  
Step 12:
 
OWASP Foundation and community monitors progress of the project activity
 
  
 
<hr>
 
<hr>

Revision as of 21:30, 25 January 2016

Congratulations! You found the 2016 OWASP Project Process Page.

STATUS: DRAFT

Eveyrone has a dream of what the cake will look like at their marriage, wedding, birthday but they are different types of cakes.. Lets summarize the process for baking a cake(aka:project) at OWASP with a simple step by step process. Please do not use people's names rather roles in the description of the process.


Step 1: New Project Leader submits New Project Request Form it is logged in the system and an alert is sent to the Project Coordinator

Step 2: New Project Request is received and reviewed by Project Coordinator for complete information .It must contain the following information to qualify as an acceptable submission: You will need to gather the following information together for your application:

  • Project Name,
  • Project purpose / overview,
  • Project Roadmap,
  • Project links (if any) to external sites,
  • [[Guidelines_for_OWASP_Projects#Project_Licensing|Project License],]
  • Project Leader name,
  • Project Leader email address,
  • Project Leader wiki account - the username (you'll need this to edit the wiki),
  • Project Contributor(s) (if any) - name email and wiki account (if any),
  • Project Main Links (if any).

==>For Documentation: A table of Contents ==>For Code: A prototype hosted in an open source repository of your choice. Make sure it has read access. https://www.owasp.org/index.php/Category:OWASP_Project#tab=Starting_a_New_Project

Step 3: If all information is completed following the minimum criteria for Projects (Code/Tool/documentation), The Project Coordinator notifies the Project Leader that the request has been accepted, and at the same time notifies the Review team that a new project has been submitted, including al the information requested in the project criteria

Step 4: Project Coordinator proceeds to create a new Wiki page for the project including all the information sent by the project leader. project coordinator uses one of these project wiki template:

Also Project coordinator creates a mailing list for the project leader and sets him as admin

Step 5: Project Coordinator notifies project leader and Review team about the created wiki page, providing the link to the wiki page.

  • Review team might provide comments for further improvement of the wiki page if necessary
  • Project leader should request a wiki account to be able to update his own wiki page after wards

Step 6: Project coordinator updates the Wiki project inventory, Dashboard and open hub with the information regarding the new created project

Step 7: Project is set in the agenda for monitoring over the next 3 months to check how has been developing


Step 8: Every 3 months, project co-ordinator monitors the activity on the wiki page for new updates and on the Openhub for commits and level of activity Findings are then reported on the Dashboard as comments

Step 9: if the project has not been updated and has no activities after six months of creation, project coordinator sends an email to the project leader, CC: project review team regarding the lack of activity and asks for a feedback and status to see how has been developing.The findings are then updated on the dashboard.

Step 10: Over the next 6 months the project is monitored again for activity. If no updates has occurred since its inception after 12 months, project is then set as inactive and project leader is notified about the status. Project coordinators updates the inventory setting the project under the 'inactive category' Dashboard is updated



Reference Material

Project Review Guidelines

GITHUB OWASP

OpenHub

Projects Slides

Primary Wiki Page

This category currently contains no pages or media.