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 "How to Start an OWASP Project"
m (→OWASP Recommended Licenses) |
|||
Line 34: | Line 34: | ||
<br> | <br> | ||
− | ==OWASP Recommended Licenses== | + | ==OWASP Recommended Licenses== |
− | + | {{Recommended_Licenses}} | |
− | |||
− | |||
− | { | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Project Release == | == Project Release == |
Revision as of 20:20, 9 December 2012
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.
- Available Grants to consider if you need funding - Click Here
- 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
- Project Name,
- Project purpose / overview,
- Project Roadmap,
- Project links (if any) to external sites,
- 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).
OWASP Recommended Licenses
Why are you recommending these licenses?
Which other open source licenses are eligible for an OWASP project?
Choosing a license under which an artifact is distributed and enforcing the license are prerogatives of the copyright holders over that artifact. By default, each contributor is copyright holder over the contributed piece. Contributors must all agree on the license and cooperate in enforcing it or must assign their copyright to the entity which becomes responsible for choosing and enforcing the license.
OWASP is a collaborative initiative for the public good and most of its output is expected to be functional, rather than aesthetic. The problem OWASP tackles is so large that OWASP acknowledges a need to collaborate with the commercial world. Therefore, in order to become an OWASP Sponsored Project, you should be comfortable with:
- Allowing arbitrary uses for your work, for example for commercial purposes. (If you disagree, consider using CC-BY-NC.)
- Revealing to the world your project's source code (its form preferred for modification).
- Allowing your work, under certain conditions (see below), to be modified by others and redistributed. (If you disagree, consider using CC-BY-ND.)
Artifact | Under what conditions can your work be modified and redistributed? | |||
---|---|---|---|---|
As long as modifications are licensed in the same spirit | If credit is appropriately given to you | Under any circumstances | ||
Standalone Tool | Run locally |
|
|
|
Consumed over the network |
| |||
Library |
| |||
Document (includes E-Learning, presentations, books etc.) |
|
|
Project Release
- As your project reaches a point that you'd like OWASP to assist in its promotion, the OWASP Global Projects Committee will need the following to help spread the word about your project:
- Conference style presentation that describes the tool/document in at least 3 slides,
- Project Flyer/Pamphlet (PDF file),
- If possible, get also the following information together:
B – FIRST RELEASE
- Release Name,
- Release Description,
- Release Downloadable file link
- Release Leader,
- Release Contributor(s),
- Release Reviewer,
- Release Sponsor(s) (if any),
- Release Notes
- 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, fill out the new project form. 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!
- Check out the Guidelines for OWASP Projects.
Project Forms
Project Transition Application
Incubator Project Graduation Application