Difference between revisions of "How OWASP Works"

From OWASP
Jump to: navigation, search
m (OWASP Board)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''How OWASP Works'''
+
The Open Web Application Security Project ([[Main_Page|OWASP]]) is the name for all the activities of the [[OWASP Foundation]]. The OWASP Foundation is a [http://www.irs.gov/charities/charitable/article/0,,id=96114,00.html 501(c)(3)] non-profit organization incorporated in the United States of America. OWASP's all-volunteer participants produce free, professional quality, open-source documentation, tools, and standards. The OWASP community facilitates conferences, local chapters, articles, and message forums. Participation in OWASP is free and open to all, as are all the materials we produce.
  
The Open Web Application Security Project (OWASP) is the name for all the activities of the OWASP Foundation. The OWASP Foundation is a 501(c)3 non-profit organization incorporated in the United States of America. OWASP's all-volunteer participants produce free, professional quality, open-source documentation, tools, and standards. The OWASP community facilitates conferences, local chapters, articles, and message forums. Participation in OWASP is free and open to all, as are all the materials we produce.
+
== Management ==
  
'''Management'''
+
OWASP projects are managed using a collaborative, consensus-based process. We do not have a hierarchical structure. Rather, different groups of contributors have different rights and responsibilities in the organization. OWASP is a meritocracy where these rights and responsibilities follow from the skills and contributions of participants. This document outlines our general structure. Individual projects define their own rules to add additional structure to their development processes.
  
OWASP projects are managed using a collaborative, consensus-based process. We do not have a hierarchical structure. Rather, different groups of contributors have different rights and responsibilities in the organization. OWASP is a meritocracy where these rights and responsibilities follow from the skills and contributions of participants. This document outlines our general structure. Individual projects define their own rules to add additional structure to their development processes.
+
== Users ==
  
'''Users'''
+
The most important participants are the people who use our documentation, tools, and standards. The majority of our participants start out as users and guide their participation from the user's perspective. Users contribute to the OWASP projects by providing feedback to project members in the form of bug reports and feature suggestions. Users participate in the OWASP community by helping other users on mailing lists and user support forums.
  
The most important participants are the people who use our documentation, tools, and standards. The majority of our participants start out as users and guide their participation from the user's perspective. Users contribute to the OWASP projects by providing feedback to project members in the form of bug reports and feature suggestions. Users participate in the OWASP community by helping other users on mailing lists and user support forums.
+
== Project Members ==
  
'''Project Members'''
+
A user who contributes to a project in the form of code or documentation becomes a project member. They take extra steps to participate in a project, are active on the project mailing list, participate in discussions, provide comments, enhancements, documentation, suggestions, and criticism. Project members are noted in project credits.
  
A user who contributes to a project in the form of code or documentation becomes a project member. They take extra steps to participate in a project, are active on the project mailing list, participate in discussions, provide comments, enhancements, documentation, suggestions, and criticism. Project members are noted in project credits.
+
== Project and Chapter Leaders ==
  
'''Project and Chapter Leaders'''
+
The OWASP Leaders is the group of individuals who take responsibility for the long-term direction of the projects in their area. There is a single Project Leader for each project which is commissioned directly by the OWASP Foundation Board of Directors. The OWASP Leaders are responsible for making decisions about technical direction, project priorities, schedule, and releases. Collectively, the OWASP Leaders can be thought of as the management of the OWASP Foundation.
  
The OWASP Leaders is the group of individuals who take responsibility for the long-term direction of the projects in their area. There is a single Project Leader for each project which is commissioned directly by the OWASP Foundation Board of Directors. The OWASP Leaders are responsible for making decisions about technical direction, project priorities, schedule, and releases. Collectively, the OWASP Leaders can be thought of as the management of the OWASP Foundation.
+
== OWASP Board ==
 
+
'''OWASP Board'''
+
  
 
The OWASP Board provides guidance to the OWASP Leaders on market direction, fundraising, strategic direction, and vision.  
 
The OWASP Board provides guidance to the OWASP Leaders on market direction, fundraising, strategic direction, and vision.  
  
The board is made up of:
+
The board is made up of:  
 +
 
 +
*[[User:MichaelCoates|Michael Coates]] (Foundation Chair)
 +
*[[User:Wichers|Dave Wichers]]
 +
*[[User:Brennan|Tom Brennan]] (Secretary)
 +
*[[User:Sdeleersnyder|Sebastien Deleersnyder]]
 +
*[[Eoin_Keary]] (Vice Chair)
 +
*[[Matt_Tesauro]] (Treasurer)
  
* [[User:Jeff_Williams|Jeff Williams]] (Foundation Chair)
+
== References ==
* [[User:Wichers|Dave Wichers]] (Conference Chair and Holder of the OWASP Books)
+
* [[User:Dinis.cruz|Dinis Cruz]] (Chief Evangelist)
+
* [[User:Brennan|Tom Brennan]] (Governance)
+
* Sebastien Deleersnyder (Chapters and Projects)
+
  
[[About_OWASP]]
+
[[About OWASP]]

Latest revision as of 14:02, 13 October 2011

The Open Web Application Security Project (OWASP) is the name for all the activities of the OWASP Foundation. The OWASP Foundation is a 501(c)(3) non-profit organization incorporated in the United States of America. OWASP's all-volunteer participants produce free, professional quality, open-source documentation, tools, and standards. The OWASP community facilitates conferences, local chapters, articles, and message forums. Participation in OWASP is free and open to all, as are all the materials we produce.

Contents

Management

OWASP projects are managed using a collaborative, consensus-based process. We do not have a hierarchical structure. Rather, different groups of contributors have different rights and responsibilities in the organization. OWASP is a meritocracy where these rights and responsibilities follow from the skills and contributions of participants. This document outlines our general structure. Individual projects define their own rules to add additional structure to their development processes.

Users

The most important participants are the people who use our documentation, tools, and standards. The majority of our participants start out as users and guide their participation from the user's perspective. Users contribute to the OWASP projects by providing feedback to project members in the form of bug reports and feature suggestions. Users participate in the OWASP community by helping other users on mailing lists and user support forums.

Project Members

A user who contributes to a project in the form of code or documentation becomes a project member. They take extra steps to participate in a project, are active on the project mailing list, participate in discussions, provide comments, enhancements, documentation, suggestions, and criticism. Project members are noted in project credits.

Project and Chapter Leaders

The OWASP Leaders is the group of individuals who take responsibility for the long-term direction of the projects in their area. There is a single Project Leader for each project which is commissioned directly by the OWASP Foundation Board of Directors. The OWASP Leaders are responsible for making decisions about technical direction, project priorities, schedule, and releases. Collectively, the OWASP Leaders can be thought of as the management of the OWASP Foundation.

OWASP Board

The OWASP Board provides guidance to the OWASP Leaders on market direction, fundraising, strategic direction, and vision.

The board is made up of:

References

About OWASP