The current versions (all DRAFT) are listed below. See each tab for more project details. The Codes of Conduct are all licensed with a [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0 license].

+

The current versions (all now Stable Release Quality) are listed below. See each tab for more project details or read the summary pamphlet (English version [https://www.owasp.org/index.php/File:OWASP_Codes-of-Conduct_Pamphlet.pdf PDF] and [https://www.owasp.org/index.php/File:OWASP_Codes-of-Conduct_Pamphlet.docx MS Word]) and [http://www.appsecusa.org/p/codesofconduct.pdf presentation]. The Codes of Conduct are all licensed with a [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0 license].

What other types of organization might be able to support OWASP's mission? What are the most important things they should do?

What other types of organization might be able to support OWASP's mission? What are the most important things they should do?

Line 113:

Line 133:

Join in the [https://lists.owasp.org/mailman/listinfo/owasp-codes-of-conduct OWASP Codes of Conduct Mailing List] with your suggestions and feedback.

Join in the [https://lists.owasp.org/mailman/listinfo/owasp-codes-of-conduct OWASP Codes of Conduct Mailing List] with your suggestions and feedback.

−

|}

+

=== <div id="compliance">Statements of Compliance</div> ===

+

The implications and format of any statements of compliance is currently being discussed on the Codes of Conduct Project mailing list. The [https://lists.owasp.org/pipermail/owasp-codes-of-conduct/2011-September/000012.html thread starts here].

Revision as of 14:56, 27 March 2013

Project's Purpose

OWASP needs to take advantage of every opportunity to affect software development everywhere to achieve our mission "to make application security visible so that people and organizations can make informed decisions about application security risks"

At the Summit 2011 in Portugal, the idea was created to try to influence educational institutions, government bodies, standards groups, and trade organizations. We set out to define a set of minimal requirements for these organizations specifying what we believe to be the most effective ways to support our mission. We call these requirements a “code of conduct” to imply that these are normative standards, they represent a minimum baseline, and that they are not difficult to achieve.

This project develops and maintains OWASP Codes of Conduct, and began with those initially created at the following working sessions at the 2011 OWASP Summit:

Statements of Compliance

The implications and format of any statements of compliance is currently being discussed on the Codes of Conduct Project mailing list. The thread starts here.

Project Details

Click on the other tabs to see project information on each of the codes, including contributors, releases, assessment status and prior versions. All the Codes are discussed on a single shared mailing list. It is free and open.

Lost? Not What You Were Looking For?

These Codes relate to OWASP's aspirations for other types of organization. If you were looking for OWASP internal strategic and operational policies and processes, you might want to look at some of the following. They are not part of the OWASP Codes of Conduct Project.