Difference between revisions of "How to Start an OWASP Project"

From OWASP
Jump to: navigation, search
m
(write-up of new process)
Line 1: Line 1:
 +
== So you want to start a project... ==
 +
 
Starting an OWASP Project is easy.  You don't have to be an application security expert.  You just have to have the drive and desire to make a contribution to the application security community.
 
Starting an OWASP Project is easy.  You don't have to be an application security expert.  You just have to have the drive and desire to make a contribution to the application security community.
  
Here are some of the procedures and guidelines for running a successful OWASP project:
+
Here are some of the guidelines for running a successful OWASP project:
  
* The best OWASP projects are strategic - they make it easier to produce secure applications by filling a gap in the application security knowledgebase or technology support.
+
* The best OWASP projects are strategic - they make it easier to produce secure applications by filling a gap in the application security knowledge-base or technology support.
  
 
* You ''can'' run a single person project, but it's usually best to get the community involved.  You should be prepared to support a mailing list, build a team, speak at conferences, and promote your project.
 
* You ''can'' run a single person project, but it's usually best to get the community involved.  You should be prepared to support a mailing list, build a team, speak at conferences, and promote your project.
  
* To get your project started, please contact [https://www.owasp.org/index.php/Global_Projects_and_Tools_Committee OWASP Global Projects Committee] or the OWASP [mailto:paulo.coimbra(at)owasp.org Project Manager] directly. We'll get you set up with a project wiki page, a mailing list, and subscribe you to the OWASP-Leaders list. You'll be part of setting OWASP's direction!
+
* You can contribute existing documents or tools to OWASP! Assuming you have the intellectual property rights to a work, you can open it to the world as an OWASP Project. Please coordinate this with OWASP by contacting owasp(at)owasp.org.
  
* We will create a wiki page as the official homepage for your project.  It will contain the <nowiki>[[Category:OWASP Project]]</nowiki> tag at the bottomIt will also be listed in the appropriate category on the [[:Category:OWASP Project|OWASP Projects]] page, which means that, initially, until being [[:Category:OWASP Project Assessment|assessed]], it will be placed alphabetically within the [[:Category:OWASP_Project#Alpha_Status_Projects|‘Alpha Status Projects’]] category. Exceptions to this initial placement will be made for projects that have been sponsored within [[:Category:OWASP_Project#Season_of_Code_Projects|OWASP 'Seasons of Code’]]. In this case, the projects will be listed on the category with the same name.
+
* You should promote your project through the OWASP channels as well as by outside meansGet people to blog about it!
  
* Each project page should contain a short description of what the project is about, a link to the project mailing list, contact information for the project leader, and any other information.  Screenshots are highly encouraged.
+
== Creating a new project ==
  
* You can have as many wiki pages as you want to support your project.  Please feel free to create them yourself.  Everything posted on the wiki is reviewed by many people around the world.
+
Here's the simple process for starting a new OWASP Project.
  
* You can contribute existing documents or tools to OWASP! Assuming you have the intellectual property rights to a work, you can open it to the world as an OWASP Project.  Please coordinate this with OWASP by contacting owasp(at)owasp.org.
+
* Get the following information together:
 +
*# Project name
 +
*# Project leader(s) (name and email)
 +
*# Short project description (1-2 sentences)
 +
*# Detailed description/roadmap for future development
 +
*# Chosen open-source license
 +
*# Project contributors (if any)
 +
*# Sponsor organizations (if any)
 +
*# Main links (existing information on the web, if any)
 +
*# Related OWASP Projects
  
* You should promote your project through the OWASP channels as well as by outside meansGet people to blog about it!
+
* To get your project started, send the info above to the [[Global Projects Committee|OWASP Global Projects Committee]] or the OWASP [mailto:paulo.coimbra(at)owasp.org Project Manager] directlyWe'll review the information and get you set up with a project wiki page, a mailing list, and subscribe you to the OWASP-Leaders list. You'll be part of setting OWASP's direction!
  
 +
* Check out the [[Guidelines for OWASP Projects]].
  
 
[[Category:OWASP Project]]
 
[[Category:OWASP Project]]
 
[[Category:How To]]
 
[[Category:How To]]

Revision as of 16:47, 17 March 2009

So you want to start a project...

Starting an OWASP Project is easy. You don't have to be an application security expert. You just have to have the drive and desire to make a contribution to the application security community.

Here are some of the guidelines for running a successful OWASP project:

  • The best OWASP projects are strategic - they make it easier to produce secure applications by filling a gap in the application security knowledge-base or technology support.
  • You can run a single person project, but it's usually best to get the community involved. You should be prepared to support a mailing list, build a team, speak at conferences, and promote your project.
  • You can contribute existing documents or tools to OWASP! Assuming you have the intellectual property rights to a work, you can open it to the world as an OWASP Project. Please coordinate this with OWASP by contacting owasp(at)owasp.org.
  • You should promote your project through the OWASP channels as well as by outside means. Get people to blog about it!

Creating a new project

Here's the simple process for starting a new OWASP Project.

  • Get the following information together:
    1. Project name
    2. Project leader(s) (name and email)
    3. Short project description (1-2 sentences)
    4. Detailed description/roadmap for future development
    5. Chosen open-source license
    6. Project contributors (if any)
    7. Sponsor organizations (if any)
    8. Main links (existing information on the web, if any)
    9. Related OWASP Projects
  • To get your project started, send the info above to the OWASP Global Projects Committee or the OWASP Project Manager directly. We'll review the information and get you set up with a project wiki page, a mailing list, and subscribe you to the OWASP-Leaders list. You'll be part of setting OWASP's direction!