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 "Working Sessions Methodology"

From OWASP
Jump to: navigation, search
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
# Each Working Session must have a Chair and a Secretary.
+
== Working Session Rules ==
# The OWASP Board invites the Working Session Chair and this one invites the Secretary.  
+
# Each Working Session must have a Chair and a Operational Manager.
 +
# The OWASP Board invites the Working Session Chair and this one invites the Operational Manager.  
 
# Although every registered people can (and is invited to) attend '''all''' Working Sessions, in terms of '''discussion''', each Working Session Chair may choose from two available options:
 
# Although every registered people can (and is invited to) attend '''all''' Working Sessions, in terms of '''discussion''', each Working Session Chair may choose from two available options:
 
## "Everybody is a Participant",
 
## "Everybody is a Participant",
 
## "Participants + Attendees".
 
## "Participants + Attendees".
# Working sessions that are under 7 attendees will be removed from the Summit agenda.
 
# The chair is responsible for recruiting attendees.
 
 
# The Working Session must be lead by its chair accordingly to the [http://www.robertsrules.org/rulesintro.htm Roberts Rules of Order].
 
# The Working Session must be lead by its chair accordingly to the [http://www.robertsrules.org/rulesintro.htm Roberts Rules of Order].
# Working Sessions will produce Motions of OWASP Initiatives, Statements, and Decisions.
+
# Working Sessions will produce Motions of OWASP Initiatives, Statements, and Decisions = Outcomes / Deliverables.
 
# All Motions will be approved by Simple Majority of the participants.
 
# All Motions will be approved by Simple Majority of the participants.
# The Secretary must write down all approved Motions.
+
# The Operational Manager must write down all approved Motions.
 
# OWASP Board Reserves Veto and Tabling Authority.
 
# OWASP Board Reserves Veto and Tabling Authority.
 +
 +
== Working Session Promotion ==
 +
# The chair is responsible for promotion of their working session, describing its specific purpose and goals in order to recruit attendees and garner publicity.
 +
# Chairs will need to make sure their working group page is managed.
 +
# Our goal is to get a minimum of 7 attendees for each session.

Latest revision as of 16:26, 28 January 2011

Working Session Rules

  1. Each Working Session must have a Chair and a Operational Manager.
  2. The OWASP Board invites the Working Session Chair and this one invites the Operational Manager.
  3. Although every registered people can (and is invited to) attend all Working Sessions, in terms of discussion, each Working Session Chair may choose from two available options:
    1. "Everybody is a Participant",
    2. "Participants + Attendees".
  4. The Working Session must be lead by its chair accordingly to the Roberts Rules of Order.
  5. Working Sessions will produce Motions of OWASP Initiatives, Statements, and Decisions = Outcomes / Deliverables.
  6. All Motions will be approved by Simple Majority of the participants.
  7. The Operational Manager must write down all approved Motions.
  8. OWASP Board Reserves Veto and Tabling Authority.

Working Session Promotion

  1. The chair is responsible for promotion of their working session, describing its specific purpose and goals in order to recruit attendees and garner publicity.
  2. Chairs will need to make sure their working group page is managed.
  3. Our goal is to get a minimum of 7 attendees for each session.