Difference between revisions of "OWASP Project Manager Activity Reports/February 11 2013"

From OWASP
Jump to: navigation, search
Line 36: Line 36:
 
==Currently Working On==
 
==Currently Working On==
 
*'''Grant Opportunities Recap & Updates'''
 
*'''Grant Opportunities Recap & Updates'''
**Guidebooks Proposal: We are in the process of invoicing for this grant award. We will be given the funds in 3 installments over the course of the project.  
+
**Guidebooks Proposal: We are still waiting for the first payment.
 
**Amount: $25,000
 
**Amount: $25,000
**ESAPI Proposal: Deb, our DHS representative, has let me know that this proposal is still under review.  
+
**ESAPI Proposal: This proposal is still under review.
 
**Amount: $25,000
 
**Amount: $25,000
**Google Grants: We have been accepted into the Google Grants scheme. I am waiting to hear back from the Google for Non-Profits team for confirmation of the award.
+
**Google Grants: We have been awarded this grant. Working on developing strategies to implement/use these funds.  
 
**Amount: $120,000 a year in Google Adwords Money
 
**Amount: $120,000 a year in Google Adwords Money
**ModSecurity Proposal: Ryan and I are working together to develop the first draft of the proposal.   
+
**ModSecurity Proposal: This proposal is now complete, and it has been submitted and accepted by DHS 
 +
**Amount: $30,000
 +
**'''OWASP Static Analysis Tools Funding Opportunity: DHS'''
 +
**There is a possibility of funding some of our Static Analysis tools.
 +
**The interested party is a different department within the DHS.
 +
**I am currently in talks with the DHS representative responsible for these initiatives.   
  
*'''AppSec APAC 2013: Planning'''
+
*'''Total Grant Funds Awarded: $145,000 for 2013 so far.'''    
**We have now selected our two OPT speakers.
+
**Dennis Groves: OWASP AppSensor the future of Application Security.
+
**Jim Manico: Using ESAPI for Java to Build Secure Web Applications.
+
**They are both registered, and have their travel arrangements sorted.   
+
  
 
*'''New Project Web Page'''
 
*'''New Project Web Page'''
**The new [https://www.owasp.org/index.php/Test2test Project Page] design is now complete.
+
**The web page has been launched.
**Please review the page, and note down any comments, changes, etc.
+
**It has replaced the [https://www.owasp.org/index.php/Category:OWASP_Project OWASP Projects Page]  
**I have received great feedback from the OWASP Board. Thank you.
+
**I am focusing on updating and maintaing our projects page at least twice a week.  
**I will send this out to the Leader's List today after our call.  
+
  
*'''[https://docs.google.com/a/owasp.org/document/d/1MpZx5w4TaqS-FoQaEXDhncz6dhG4mdgC4id2HsJQhjc/edit Projects Handbook 2013]'''
+
*'''Projects Handbook 2013'''
**The Projects Handbook is almost complete.  
+
**The Projects Handbook is now live.
**Please review when you get the opportunity, and provide feedback on the last draft.  
+
**Users can download it on the [https://www.owasp.org/index.php/Category:OWASP_Project Projects Web Page].  
**I plan to make this live with the Projects Page.
+
  
*'''[https://fosdem.org/2013/ FOSDEM]'''
+
*'''FOSDEM'''
**Simon Bennetts is presenting ZAP.
+
**FOSDEM went very well for the Event team in Brussels.
**We have been successful with our stand application.
+
**The flyers went down very well.
**Seba and Martin Knobloch will be helping coordinate the OWASP stand.
+
**Simon's presentation on ZAP went very well according to attendees.
**Event: February 2nd & 3rd, Brussels, Belgium.  
+
**The OWASP representatives at the event mentioned that many developers were not aware of OWASP.
**We are working together to get OWASP branded material for the event.  
+
**It is suggested we attend more events like these for outreach.
 +
 
 +
*'''Preparation for London BSides'''
 +
**Fabio Cerullo and I had a conversation about flyers and Schwag for this event.
 +
**We are still in the process of creating, and sourcing items for this.  
 +
**[http://www.securitybsides.org.uk/ Security BSides London]
 +
 
 +
*'''Guidebooks Project Management'''
 +
**The Guidebooks Projects have now begun their work.
 +
**We are using a collaborative Gantt chart tool to manage our work flow.
 +
**Start Date: February 4th 2013
 +
**End Date: June 4th 2013
  
 
==Important GPC Meeting Outcomes and Discussion Points==
 
==Important GPC Meeting Outcomes and Discussion Points==

Revision as of 11:30, 11 February 2013

Contents

OWASP Project Manager Report

Work accomplished since January 14, 2013

  • Project Numbers
    • Active Projects: 129
    • Inactive Projects: 67

Project Manager Q1 2013 Objectives

  1. Continue grant funding research: Target $150 K in 2013.
  2. Finalize and Implement New Project Infrastructure processes.
  3. Coordinate OSS and OWASP Track documentation, guidelines, and processes as they apply to Global AppSec Conferences. (Ongoing for 2013)
  4. Increase Sales Force use for project management.
  5. Complete and Launch Projects page.
  6. Finalize the Project Leader Handbook.

Currently Working On

  • Grant Opportunities Recap & Updates
    • Guidebooks Proposal: We are still waiting for the first payment.
    • Amount: $25,000
    • ESAPI Proposal: This proposal is still under review.
    • Amount: $25,000
    • Google Grants: We have been awarded this grant. Working on developing strategies to implement/use these funds.
    • Amount: $120,000 a year in Google Adwords Money
    • ModSecurity Proposal: This proposal is now complete, and it has been submitted and accepted by DHS
    • Amount: $30,000
    • OWASP Static Analysis Tools Funding Opportunity: DHS
    • There is a possibility of funding some of our Static Analysis tools.
    • The interested party is a different department within the DHS.
    • I am currently in talks with the DHS representative responsible for these initiatives.
  • Total Grant Funds Awarded: $145,000 for 2013 so far.
  • New Project Web Page
    • The web page has been launched.
    • It has replaced the OWASP Projects Page
    • I am focusing on updating and maintaing our projects page at least twice a week.
  • Projects Handbook 2013
  • FOSDEM
    • FOSDEM went very well for the Event team in Brussels.
    • The flyers went down very well.
    • Simon's presentation on ZAP went very well according to attendees.
    • The OWASP representatives at the event mentioned that many developers were not aware of OWASP.
    • It is suggested we attend more events like these for outreach.
  • Preparation for London BSides
    • Fabio Cerullo and I had a conversation about flyers and Schwag for this event.
    • We are still in the process of creating, and sourcing items for this.
    • Security BSides London
  • Guidebooks Project Management
    • The Guidebooks Projects have now begun their work.
    • We are using a collaborative Gantt chart tool to manage our work flow.
    • Start Date: February 4th 2013
    • End Date: June 4th 2013

Important GPC Meeting Outcomes and Discussion Points

  1. GPC Meeting: December 14 2012 Project Manager Report
  2. GPC Meeting: December 21 2012 Project Manager Report
  3. GPC Meeting: December 27 2012 Project Manager Report
  4. GPC Meeting: January 04 2013 Project Manager Report
  5. GPC Meeting: January 11 2013 Project Manager Report
  6. Part-Time Project Support Volunteer Role for Guidebook Projects: The final applicants have been chosen. Cristhian Fabia: Testing Guide; Larry Conklin: Code Review Guide; Dulan Dhana: Development Guide.
  7. I will not have any scheduled GPC meetings for the rest of January. These meetings will be replaced by the OWASP Initiatives Meetings.
  8. Keith suggested that we should try the initiatives meetings for the month of January, and then decide whether we wish to meet more regularly come February. I agree. This is the plan. Please make sure you join the Initiative Meetings for Projects related updates and news.
  9. Projects Handbook 2013- Please review when you get the opportunity, and provide feedback on the last draft. I plan to make this live with the Projects Page.
  10. Keith suggested we develop a project requirement that will identify a project's maturity level both visually and within their documentation.
  11. I tasked myself with developing a template, visual branding, and review criteria to meet this need as I feel it is a very important distinction to make between our projects.