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 "Projects Reboot 2012"

From OWASP
Jump to: navigation, search
m (fixing auto tab selection)
 
(48 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
+
#Redirect [[Category:OWASP_Project#Participating_in_a_Project]]
 
 
'''Welcome the the OWASP Project Reboot Page:
 
'''
 
 
 
''What is the OWASP Project ReBoot initiative?''
 
 
 
OWASP needs to refresh, revitalize & update its projects. We need to make the software development community more aware of our efforts and demonstrate the foundations library of solutions & guidance designed to help with the secure application development lifecycle.
 
 
 
The proposal for this initiative is here:
 
 
 
'''[https://docs.google.com/a/owasp.org/file/d/0B5Z9zE0hx0LNSUZvOWVKd1JRWnlVaGJMcjB3SEN3Zw/edit Project Re-Boot Proposal]'''
 
 
 
To that end we have a budget to fund various project related activities. We hope putting some financial support behind projects will re-energise our community and hopefully deliver some great high quality material which can be used to support software developers and testers for years to come:<br><br>
 
 
 
'''Current Submissions''' <br>
 
'''[[OWASP Application Security Guide For CISOs]]''' <br>
 
'''[[OWASP Development Guide]]'''<br>
 
 
 
'''Activity types''':<br>
 
 
 
'''Type 1''': Update, rewrite & complete guides or tools.<br>
 
This "type" is aimed at both existing and new tools or guides which require development effort to update, augment, rewrite, develop in order to achieve a high quality release quality product.<br><br>
 
 
 
Examples:<br>
 
#"Mini" Project based summits: Expenses associated with getting global workshops, with the aim of releasing a new version of a project.<br>
 
#Paying contributors for their time and effort.<br>
 
#Paying for user guides etc to be professionally developed (technical writing etc).<br><br>
 
 
 
'''Type 2''': Market, Training, Awareness, increase adoption.<br>
 
Existing, healthy robust tools and guides can utilise Type 2 activities to help with creating awareness and increasing adoption of that project.<br>
 
 
 
Examples:<br>
 
#Assisting with expenses associated with marketing a project.<br>
 
#Costs facilitating OWASP project focused training and awareness events<br>
 
 
 
 
 
'''How are we going to fund this??'''<br>
 
We are requesting all OWASP chapters which are in a healthy financial position to pledge 25% of their chapters funds to pay for this initiative.<br>
 
 
 
Donate $1.00 to help save a current or future software application [http://www.firstgiving.com/fundraiser/projectreboot/owasp-project-reboot Click Here]
 
 
 
The Foundation shall also support this initiative with additional funding.<br>
 
The goal is to accumulate a budget of $100K which shall be appointed to projects undergoing this reboot.<br>
 
 
 
[https://docs.google.com/a/owasp.org/spreadsheet/pub?hl=en_US&hl=en_US&key=0Atu4kyR3ljftdEdQWTczbUxoMUFnWmlTODZ2ZFZvaXc&output=html - Chapter Funds]
 
 
 
'''Can I apply for this Reboot?'''<br>
 
You certainly can, assuming you are an OWASP member.<br>
 
If you feel your project is ready or has potential you can apply for the reboot programme.<br>
 
 
 
 
 
'''How does funding work?'''<br><br>
 
'''Type 1''': Funding can be applied for as required if travel/mini summit etc is to be expensed as part of the reboot. Development activities; payment to contributors shall be at 50% and 100% milestones.<br>
 
Milestones are agreed prior to project reboot initiation.<br>
 
Once the 50% milestone is reached the work done to date shall be reviewed by a member of the [https://www.owasp.org/index.php/Category:Global_Projects_Committee - GPC] and also another nominated OWASP reviewer (generally an OWASP leader).<br>
 
 
 
'''Type 2''': Funding is supplied as required. Items to be funded are agreed prior to reboot initiation.<br>
 
Invoices for the required services are sent directly to the foundation for payment.
 
 
 
 
 
'''How do I apply?'''
 
Send in a proposal with the following information:
 
 
 
# Project name and description. Including reboot project lead and any team members.
 
# Re boot type (Type 1 or Type 2)
 
# Goals of the reboot
 
# Timeline for the 50% milestone and the 100% milestone. Suggested milestone reviewers (Generally OWASP Leaders or other industry experts)
 
# Budget required and how you shall spend it.
 
 
 
Want to support this initiative or learn more? Contact [mailto:[email protected] Eoin Keary]
 

Latest revision as of 16:44, 25 November 2015