OWASP Project Manager Activity Reports/December 10 2012

Jump to: navigation, search

OWASP Project Manager Report

Work accomplished since November 12, 2012

  • Project Numbers
    • Active Projects: 120
    • Inactive Projects: 66
    • Merged Projects: 42

Project Manager Q4 Objectives

  1. Identify and initiate 3 grant opportunities.
  2. Complete metadata for Salesforce import related to projects.
  3. Finalize and launch the Project database communication tool and webpage.
  4. Complete the project lifecycle redesign.
  5. Complete Version 2013 of the Project Handbook.

Currently Working On

  • Grant Opportunities Recap & Updates
    • Guidebooks Proposal: We are in the process of submitting DHS required tax paperwork so we can receive payment.
    • Amount: $25,000
    • ESAPI Proposal: This proposal has been submitted, and we are waiting to hear back from the DHS.
    • Amount: $25,000
    • Google Grants: This proposal has been submitted. We should hear back from Google in January 2013.
    • Amount: $120,000 a year in Google Adwords Money
    • ModSecurity Proposal: I've already started the process for the OWASP ModSecurity Proposal. Ryan and I are currently working towards developing a plan for the project.
  • Salesforce Metadata Migration
    • The Salesforce metadata migration is now complete.
    • All project data is up-to-date based on the GPCs project inventory spreadsheet.
    • I am currently working with Kate to develop a form in Salesforce that will help us ask active project leaders to update their information directly through the form.
  • Project Processes & Lifecycle Development
    • Process form development: Completed via Salesforce forms.
    • Project Stage Benefits: Proposal completed and in the process of being discussed.
    • Project Graduation Process: Proposal completed and in the process of being reviewed.
    • Project Graduation Criteria: Still in development.
    • Project Migration Process: Still in development.
  • SourceForge Update
    • Audrey from Geeknet has responded to our proposal.
    • The Geeknet team has decided not to accept any of our options, see below:
    • Option 1: OWASP would like to propose that Geeknet waive either all or a percentage of the invoice fee, and redistribute the funds as a donation to the OWASP Foundation.
    • Option 2: OWASP would like to propose a 1 year corporate membership, and a 6 month online rotating banner advertisement in exchange for $10,000 being deduction from the Invoice in question. Total value: $17,500 in OWASP Services.
    • However, they did deduct $2500 from the original invoice: Update Geeknet Invoice.
    • We have agreed to accept this new proposal, and we are currently processing their payment.
  • AppSec APAC 2013: Planning
    • OSS & OPT forms are up.
    • I developed banners for each event: Projects Page.
    • I launched individual communication pieces this morning announcing the "call for entries": LinkedIn, Blog, Twitter.
    • I am attending the conference to help coordinate the event, and I am leading the Chapter Leader Workshop with the help of a translator.

Important GPC Meeting Outcomes and Discussion Points

  1. GPC Meeting: November 16 2012 Project Manager Report
  2. GPC Meeting: November 30 2012 Project Manager Report
  3. GPC Meeting: December 07 2012 Project Manager Report
  4. The ModSecurity proposal grant writing is in progress.
  5. SourceForge: They have responded. They decided to decline both options proposed by OWASP, but they have deducted $2500 from the original bill. We are currently processing the new invoice.
  6. AppSec APAC 2013: Call for Entries for the Open Source Showcase & OWASP Projects Track were launched again. Justin, Sam ,and possibly Nishi and Keith will attend.
  7. Part-Time Project Support Volunteer Role for Guidebook Projects: The final applicant count was 14 volunteers. I am currently processing the applications, and I will allocate roles come next week.
  8. FOSDEM: The application for a stand was submitted this week. If we get the stand, Seba and Martin K. will manage it for OWASP.
  9. Nishi: Will touch base with Matt Tesauro regarding the wiki file size requirement.
  10. Question for Justin: Have you spoken to James Greenberg from AppSec Labs? Have they come to a decision regarding their license choice, and whether they are choosing to continue as an OWASP Project?
  11. Question: Do we have criteria that measures whether a project is active or not?: Answer: The OpsTeam is working on creating an e-mail through Salesforce that will ask all current 'Active' project leaders to give us a status update. Additionally, it will give them an opportunity to update their information.
  12. Active Project Criteria: We discussed the idea of requiring project leaders to send us an update every six months, or annually. The aim is to make sure a project is still active.
  13. Project Update required information would be something along the lines of: Update the wiki with links and announcements, a summary of what you have accomplished, and a summary of your future plans.