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

From OWASP
Jump to: navigation, search
Line 16: Line 16:
  
 
Here's the simple process for starting a new OWASP Project.
 
Here's the simple process for starting a new OWASP Project.
 
+
<br>
 +
<br>
 
* Get the following information together:
 
* Get the following information together:
  
A PROJECT
+
A - PROJECT
# Project Name,  
+
# Project Name,
# Project Purpose,
+
# Project purpose / overview,
# Project License,
+
# Project Leader,
+
# Project Maintainer,
+
# Project Contributor(s),
+
# [http://globalprojectscommittee.wordpress.com/2009/07/27/what-is-the-3x-slide-presentation-thing/ Conference style presentation that describes the tool in at least 3 slides],
+
# [http://globalprojectscommittee.wordpress.com/2009/07/21/what-is-this-project-flyerpamphlet-thing/ Project Flyer/Pamphlet (PDF file)],
+
 
# Project Roadmap,
 
# Project Roadmap,
# Project main links,  
+
# Project links (if any) to external sites,
 +
# [http://www.owasp.org/index.php/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).
 +
<br>
 +
*As your project reaches a point that you'd like OWASP to assist in its promotion, the GPC will need the following to help spread the word about your project:
 +
 
 +
# [http://globalprojectscommittee.wordpress.com/2009/07/27/what-is-the-3x-slide-presentation-thing/ Conference style presentation that describes the tool/document in at least 3 slides],
 +
# [http://globalprojectscommittee.wordpress.com/2009/07/21/what-is-this-project-flyerpamphlet-thing/ Project Flyer/Pamphlet (PDF file)],
 +
<br>
 +
* If possible, get also the following information together:
  
 
B – FIRST RELEASE
 
B – FIRST RELEASE
 
# Release Name,
 
# Release Name,
# Release main features,
+
# Release Description,
# Release downloadable file link  
+
# Release Downloadable file link  
 
# Release Leader,
 
# Release Leader,
 
# Release Contributor(s),
 
# Release Contributor(s),
 
# Release Reviewer,
 
# Release Reviewer,
# Release Mentor (if any),
 
 
# Release Sponsor(s) (if any),
 
# Release Sponsor(s) (if any),
# Release Flyer/Pamphlet,
+
# Release Notes
# Release Roadmap,
+
# Release Main Links (if any),
# Release Main Links,
+
<br>
 
+
* Note: For Project/Release Leader, Contributors and Reviewers please create a [http://www.owasp.org/index.php?title=Special:UserLogin wiki accounts] and please send the links off. See [[Tutorial]] and [[:User:Mtesauro|here]] how to do it and [[:Category:OWASP Live CD Project|here]] an example of how it will be used.
* Note: For Project Leader, Maintainer, Contributors, Reviewer and Mentor please create a [http://www.owasp.org/index.php?title=Special:UserLogin wiki accounts] and please send me off the links. See [[Tutorial]] and [[:User:Mtesauro|here]] how to do it and [[:Category:OWASP Live CD Project|here]] an example of how it will be used.
+
<br>
 
+
 
* 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] 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!
 
* 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] 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!
 
+
<br>
 
* Check out the '''[[Guidelines for OWASP Projects]]'''.
 
* Check out the '''[[Guidelines for OWASP Projects]]'''.
  
 
[[Category:OWASP Project]]
 
[[Category:OWASP Project]]
 
[[Category:How To]]
 
[[Category:How To]]

Revision as of 14:27, 27 August 2010

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:

A - PROJECT

  1. Project Name,
  2. Project purpose / overview,
  3. Project Roadmap,
  4. Project links (if any) to external sites,
  5. Project License,
  6. Project Leader name,
  7. Project Leader email address,
  8. Project Leader wiki account - the username (you'll need this to edit the wiki),
  9. Project Contributor(s) (if any) - name email and wiki account (if any),
  10. Project Main Links (if any).


  • As your project reaches a point that you'd like OWASP to assist in its promotion, the GPC will need the following to help spread the word about your project:
  1. Conference style presentation that describes the tool/document in at least 3 slides,
  2. Project Flyer/Pamphlet (PDF file),


  • If possible, get also the following information together:

B – FIRST RELEASE

  1. Release Name,
  2. Release Description,
  3. Release Downloadable file link
  4. Release Leader,
  5. Release Contributor(s),
  6. Release Reviewer,
  7. Release Sponsor(s) (if any),
  8. Release Notes
  9. Release Main Links (if any),


  • Note: For Project/Release Leader, Contributors and Reviewers please create a wiki accounts and please send the links off. See Tutorial and here how to do it and here an example of how it will be used.


  • 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!