Task Force/OWASP Projects

From OWASP
Jump to: navigation, search

This task force is focused on OWASP Projects with a first focus on cleaning up the OWASP incubator list

Current To-do list

Tracking of current stuff is done temporary here as we plan to use Jira in the long run.

To-do list: Future Tasks

  • Gather support and funding to have 1 large OWASP Summit.
  • Design a more sustainable revenue stream using the Project’s IP.
  • Identify & promote cross-project collaboration to move clusters of projects forward, with e.g. work groups that work on a certain domain.
  • Start a task force of people with spare cycles that can help projects that need extra man-power of are falling behind in delivery of new releases (especially the flag ship projects).

Completed Tasks

Failed Tasks

Execution Power

This task force exists on the assumption that it has a mandate from the OWASP leaders to act on behalf of the OWASP community on what is best for OWASP Projects. We are in the process of submitting a Committee Proposal for Project reviews

If somebody (namely an OWASP Leader or Board member) disagree with any of the decisions made, he/she has two options:

  • join this Task Force/Committe
  • create another equivalent 'OWASP Projects group' and do a better job there

note that Committee 2.0 will change this as this task force might converge to a new Committee or fall under one if needed

Current Members

  • Johanna Curiel
  • Timo Goosen
  • Abbas Naderi
  • Jason Johnson
  • Noreen Whysel - OWASP Community Manager (Staff)
  • Azzedine Islam Mennouchi

OWASP Projects Task Force (Concept)

This is a new type of OWASP initiative, focused on 'getting things done', the concept is still evolving but here are the current (in draft) guiding principles:

  1. this 'task force is an invitation-only group' (to join the task force, requests should be made directly with existing task force members)
  2. all existing members have VETO power, and it is assumed that all decisions are backed up with all existing members
  3. only existing members can send the invitations
  4. there is a 1 month minimum activity required (or the member is temporarily out).
  5. invitations are automatically approved in 24h
  6. existing members can VETO new members (and existing members can be kickout by majority)
  7. there an one special member who has veto power the responsibility to enforce the 'one month contribution MIA scenario' (i.e. to kick out the 'non contributing members')
  8. all communication MUST be made (as much as practically possible) under public mediums: Wiki, public mailings, public Hangout sessions
  9. there are NO decisions made BEHIND closed doors, or without a solid digital (hyperlinkable) trail

Discussions

Google Group You must be logged in your OWASP Google App account to view and post to the group.