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 "Task Force/OWASP Projects"
(→Completed Tasks) |
(→Failed Tasks) |
||
Line 1: | Line 1: | ||
This task force is focused on OWASP Projects with a first focus on cleaning up the OWASP incubator list | This task force is focused on OWASP Projects with a first focus on cleaning up the OWASP incubator list | ||
− | |||
− | |||
− | |||
==Execution Power== | ==Execution Power== |
Revision as of 15:08, 15 April 2016
This task force is focused on OWASP Projects with a first focus on cleaning up the OWASP incubator list
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
- Munir Njiru
- Abbas Naderi
- Claudia Aviles Casanovas - OWASP Project Coordinator (Staff)
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:
- this 'task force is an invitation-only group' (to join the task force, requests should be made directly with existing task force members)
- all existing members have VETO power, and it is assumed that all decisions are backed up with all existing members
- only existing members can send the invitations
- there is a 1 month minimum activity required (or the member is temporarily out).
- invitations are automatically approved in 24h
- existing members can VETO new members (and existing members can be kickout by majority)
- 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')
- all communication MUST be made (as much as practically possible) under public mediums: Wiki, public mailings, public Hangout sessions
- 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.