An OWASP project is a collection of related tasks that have a defined roadmap and team members. OWASP project leaders are responsible for defining the vision, roadmap, and tasks for the project. The project leader also promotes the project and builds the team. OWASP currently has over 142 active projects, and new project applications are submitted every week.
This is one of the most popular divisions of OWASP as it gives members an opportunity to freely test theories and ideas with the professional smith and wesson m&p advice and support smith and wesson m&p of the OWASP community. Every project has an associated mail list. You can view all the lists, examine their archives, and subscribe to any project by visiting the OWASP Project Mailing Lists page. A summary of recent project announcements is available on the OWASP Updates page.
All OWASP tools, document, and code library projects are organized into the following categories: Incubator smith and wesson m&p Projects: smith and wesson m&p OWASP Incubator projects smith and wesson m&p represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway. Lab Projects: OWASP Labs projects represent projects that have produced an OWASP reviewed deliverable of value. smith and wesson m&p Flagship Projects: The OWASP Flagship designation is given to projects smith and wesson m&p that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole. smith and wesson m&p Who Should Start an OWASP Project? Application Developers. Software Architects. Information Security smith and wesson m&p Authors. Those who would like the support of a world wide professional community to develop or test an idea. Anyone wishing to take advantage of the professional body of knowledge smith and wesson m&p OWASP has to offer. Contact Us
If you have any questions, please do not hesitate to contact the OWASP Projects Manager, Samantha Groves by using the form provided here. Please allow five working days for your question or comment to be answered. This is due to the large amount of queries the foundation staff receive every day. We thank you for your patience. Social Media
We recommend using the links below to find our official OWASP social media channels. These are a great way to keep in touch with the different initiatives going on at OWASP throughout the world. They are all updated regularly by chapter leaders, project smith and wesson m&p leaders, the OWASP Board Members, and our OWASP Staff. If you have any questions or concerns about any of these accounts, smith and wesson m&p please smith and wesson m&p drop us a line using our "Contact Us" form found above.
The first thing you have to do if you want to start a new project is submit a new OWASP Project application. Please submit a new project application here . You will need to gather the following information smith and wesson m&p together for your application:
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). Check out the Guidelines for OWASP Projects . Grant Spending Policy Project Spending Policy Project Sponsorship Operational Guidelines OWASP Recommended Licenses
Why are you recommending these licenses? Which other open source licenses are eligible for an OWASP project? Allow commercial uses of your work? Yes No Allow modifications of your work? Yes, no restriction except attribution Yes, as long as modification are also opensource No ToolProject (Non-WebBased) Apache 2.0 (fewest restrictions, even allowing proprietary modifications and proprietary smith and wesson m&p forks of your project, and more up-to-date than BSD license) GPL 3.0 (requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project) Sorry, such licenses are not opensource and are not eligible to become an OWASP Sponsored Project. If this is really what you want, consider using CC-BY-ND or CC-BY-NC-ND. See http://creativecommons.org/choose for more information and note that they label these two license as "not a Free Culture License" Tool Project (WebBased) AGPL 3.0 (prevents GPL
No comments:
Post a Comment