'''The Global Conferences Committee was created during the OWASP EU Summit in Portugal 2008. The Global Conferences Committee exists to coordinate and facilitate OWASP conferences and events worldwide.''' The committee is governed by the [[Global Conferences Committee Governance]] document

The Global Conferences Committee was created during the OWASP EU Summit in Portugal 2008. The Global Conferences Committee exists to coordinate and facilitate OWASP conferences and events worldwide. The committee is governed by the Global Conferences Committee Governance document

Develop a system to take in applications for all non-chapter meeting events, vet them, and schedule them. This system shall serve as the "official" registration path for all events and allow the GCC to get a firm grip on the OWASP Event Calendar.

Preparing for Release

Release - 3/5/2011

Mark (Code), Lucas & Neil (Alpha Testing, Requirements)

OWASP Global Conference Sponsors

2

3, 7

Provide unified sponsorship mechanism for all Global AppSec conferences. This will help us plan our conference revenue annually and help sponsors plan for their spending (identified as an issue by several vendors). This is intended to augment, not replace individual conference sponsorships.

Joint venture with the GPC. The track would consist of a cadre (10-20) of speakers from inew/high profile OWASP projects. The GCC would manage these speakers through an internal call for papers that would be vetted by the GCC/GPC for some of our best speakers from high profile projects. As a new conference requests an OWASP Speaking track (or for Global AppSec conferences, this will be required) the GCC would reach out to the selected presenters to verify their availability for the event and provide a list of 6-7 speakers to the local event coordinators for the schedule.

Planning for AppSecUSA release in Sept.

June 2011

Ralph

OWASP Marketing at Conferences

3

4,5,6

Promote OWASP at targeted industry and developer events. Provide OWASP support and schwag for OWASP booths at other conferences

Access to any/all of these resources must be first pre-coordinated with the Foundation via the OWASP Conference Management System (OCMS). All requests for assistance need to go through this system for review and approval.

General

OWASP Registration System - OWASP is now using an event interfaceOfficial OWASP Event registration system for ALL OWASP events (Conferences, Events and Chapter Meetings) contact us for more information.

Video

OWASP Video Cameras

OWASP Currently owns 5 sets of consumer grade video cameras (Canon VIXIA HF M300), tri-pods, memory cards, and audio connection equipment. For examples of the video taken from these cameras see the AppSec DC Vimeo stream. The cameras can shoot HD Video and have an audio input jack for taking in a house line. The system also has a QNAP TS-459 PRO network attached storage device that can be used for on-site reliable storage and backup of the video.

Video Editing/Post Processing via IEHD Productions

Basic Editing (trimming the "fat" from the beginning/end of the video)

Removing any artifacts from the video/audio leveling

Trans-Coding to MPEG4 or other suitable format for online video

Upload to a online account Vimeo et all (OWASP Provided Acct)

Adding OWASP/Conference graphic watermark

Adding intro/end slides with basic presentation details

$40.00 per finished presenter of approx. 60 minutes with no minimum

Full Post-Production

Basic Post Plus....

Inter splicing slides from various formats not limited to .ppt, .pdf, .odp

and other key sources. (client provided notations for slide transitions)

$60.00 per finished presenter of approx. 60 minutes with no minimum

On site Video Production

One HD 3 chip camera per room/track with operator & fluid head tripod

Audio setup to camera from podium or mixer

Obtaining presentations from speakers if not provided previously

Notating of time code for slide transitions

First Track: $1,100.00/day

Each Additional Track: $550.00/day

+ any travel outside Southern California

Completion/turn around model
30+ speakers with production and/or post production is 4-6 weeks with projects
uploading starting second week after conference end. Smaller or larger
conferences/projects are adjusted accordingly.

Local host chapters will share in OWASP event profits under the following schedule. In the case of multiple host chapters, the host chapters will be responsible for determining the division before the event. Policy Document

All OWASP Events must be coordinated with OWASP Foundation Staff by submitting an events description via OCMS. An approval that the event will be posted on the OWASP Wiki and Event announcement webpage will be sent from the OCMS input. Any request for funding support must follow normal funding request procedures separate from the OCMS submission.

All Events

Events must have an OWASP Wiki Page, or a webpage showing the OWASP logo and be linked to the OWASP wiki Events Pages

All Events

Only OWASP Board members or their designates may enter into contracts on behalf of the foundation

A “Leader” is defined as a chapter or project leader that is clearly identified on the chapter or project wiki page AND has been documented as a leader in the Foundation’s records.
If a leader registers for a conference complimentary ticket but does not appear for the conference, the chapter will be charged 60% of the retail cost of a conference ticket.

All Events

OWASP individual members in good standing shall receive $50 off admission to all OWASP events charging more than $50 entry fee.

All Events

A complete budget must be submitted if the event requires any funds from the OWASP Foundation and funding requests will be reviewed and approved by OWASP Executive Director. Please submit a requests via our Contact Us link on the OWASP Wiki homepage.

Regional/Theme Conferences

An OWASP leader should be invited to provide welcome and state of the union.

All Events

Global AppSec Conferences must include training

Global AppSec Conferences

Global AppSec Conferences must charge an admission fee

Global AppSec Conferences

Sessions must be recorded and posted to the public after the conference

Each training class allows for two complimentary seats to be made available to OWASP Leaders. This must be included in the Training Instructor Agreement. These are available on a first come basis. Only one training seat per session is allowed per chapter to allow for diversity in distribution of seats.

If a leader registers for a complimentary training seat but does not attend the full training session the chapter will be charged 60% of the retail cost of the training session and the leader will not be given a complimentary ticket (conference or training sessions) for any other Global AppSec events in the following year.

Event organizers must reach out to the WIA program to assist with the program committee and to help find suitable keynote and invited speakers.

Global AppSec Conferences & Regional Events

Event organizers must send an open call for participation for volunteers, papers committee.

Global AppSec Conferences & Regional Events

Event organizers should encourage all training and CFP proposals to go through the “Talk bootcamp” process.

Global AppSec Conferences & Regional Events

WIA initiative should lead a search for women keynotes, featured, panel speakers.

Global AppSec Conferences & Regional Events

Event organizers and WIA initiative should reach out to women speaker lists to encourage training proposals and speakers to submit through the normal CFP process. If there is to be a women in AppSec panels to be organized, the WIA initiative must be involved and feature predominantly women panelists.

Global AppSec Conferences & Regional Events

These aren’t quotas, but a goal. Global events organizers are free to exceed these metrics.

*At least 10% of the program committee must be women, and must include the WIA initiative members
*At least 50% of keynotes and featured speakers must be women
*At least 25% of panel participants must be women. If there are no women participants, the panel should be cancelled.
*At least 10% of talks must be women

If these metrics cannot be reached, the organizing committee should reach out to the Conference Manager for assistance, and must apply for an exception if they can’t be reached after all avenues have been exhausted.

Global AppSec Conferences

These aren’t quotas, but an aspiration goal for regional events. Organizers are free to exceed these metrics.

*At least one of the program / papers committee must be a woman, and should include the WIA initiative members
*At least one of keynotes, featured and invited speakers must be a woman
*At least 25% of panel participants should be women. If a panel has no women participants, it should be cancelled
*At least 10% of talks chosen should be women speakers

Regional Events

As one of their 2011 initiatives, the Global Conferences Committee started a Conference Liaison Program, where a member of the committee is paired with each of the Global AppSec organizing teams in order to assist them with their planning process as well as attend the conference to help trouble shoot any issues and sign necessary paperwork.

The following duties were initially set forth for the GCC liaison:

The GCC member shall:

interface with the local planning committee at least 1 month before trip (attend planning call)

Interact with planners/attendees while at conference

Interact with Sponsors

Sign conference contracts under $20,000 (once approved)

At the GCC meeting following the event, the traveling member will be expected to provide an post trip report covering: