Global Conferences Committee
About the Committee
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
- Mark Bristow (U.S, 2011 Chair Election)
- John Wilander (Sweden)
- Lucas Ferreira (Brazil)
- Richard Greenberg (US)
- Ralph Durkee (US)
- Neil Matatall (US)
- Cassio Goldschmidt (US and SA)
- Benjamin Tomhave (US)
- Mohd Fazli Azran (Malaysia)
Operational Support: Sarah Baso
Date: Monday April 11, 2011
Time: 5:00pm/17:00 GMT
Dial in: 1-866-534-4754 code:42398
Committee meeting minutes - Committee Meeting minutes taken by the GCC Chair at each GCC meeting.
How to Host a Conference - The comprehensive guide for hosting an OWASP event.
- Have a Global Appsec in NA, SA, EU, Asia in 2011
- Promote OWASP Projects/Initiatives at OWASP Conferences
- Enhance Services for Conference Planners
- Reach out to developers (have 20% of attendees in a dev position)
- Reach out to non-members (have 70% of attendees at cons non-members)
- Bring more into the fold (Generate 300 new/renewed members at conferences)
- Streamline Sponsorships (Global Conference Sponsors, Targeted Conference Sponsors)
- Revise GCC Governance
- Have a profit of $200k in 2011 across all conferences
|Revise GCC Governance||1||8||Generate self governance document for voting rules, quorum and other functional committee requirements||Complete - Global Conferences Committee Governance||January 2011||All Committee Members|
|OWASP Conference Management System (help)||1||1, 3||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.||In Development V0.01||Feb 2011||Richard, All Review|
|OWASP AppSec Track||3||2||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.||Not Started||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||Applications accepted via OCMS||In progress||Mark|
|OWASP Conference Marketing - Attendees||3||4,5,6||Provide additional mechanisms for marketing conferences to attendees||None||TBD||Neil|
|OWASP Conference Marketing - Sponsors||3||4,5,6||Provide additional mechanisms for marketing conferences to Sponsors||None||TBD||Neil, Richard|
|Conference Web Marketing||4||3||Obtain Twitter accounts, domain names, and @owasp.org email addresses for use by approved conferences. See Global Conference Resources||Complete||Complete||Mark|
|Central Conference Support Services||4||3||RegOnline is setup. Investigate costs for hiring a conference organizer.|| RegOnline - Complete
Conference Organizer - Investigate
|OWASP Short URLS||5||3||Provide short URLs on the OWASP website (e.g. https://owasp.org/AppSecBR) to make it easier to access content on the wiki, especially in emails and the like||Need to investigate with Larry||TBD||Ralph|
|Regional targeted mailing lists||5||3||Provide email lists for targeted, regional email distributions. Only GlobalAppSec conferences will be advertised on OWASP-ALL||Need to investigate leveraging Salesforce for this.||TBD||Ralph|
|OWASP Merchandise Model||6||3,9||Provide OWASP Merchandise for sale at conferences||May be a bit OBE as Kate has established something similar already. May just need an "inventory" we can send places.||TBD||None|
If you have questions or require an exception to any of these please contact the OWASP Staff.
|All content must be vendor neutral||All Events - Core Value|
|All content must be made available to the public after the conference||All Events - Core Value|
|All calls for papers, training and registration must be open and promoted to the public||All Events - Core Value|
|Selecting Committee Members (Training or Papers) must not submit||All Events|
|Use the conference website/wikipage to submit papers. It must supports blind paper submissions.||All Events|
|All events must be conducted in a manner consistent with the OWASP Mission, Principles and Code of Ethics||All Events - Core Value|
|OWASP Event Definitions||All Events|
|OWASP Event Requirements||All Events|
| 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||All Events|
|All finances must be handled by the OWASP Foundation||All Events|
| Complimentary conference admissions are provided to speakers, volunteers, staff, Global Board members and active OWASP Leaders.
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.
|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||Global AppSec Conferences|
|There must be at least one networking event at the conference||Global AppSec Conferences|
|All Training providers are required to sign a Training Instructor Agreement||Training|
|Training revenue will be split 60/40 (OWASP/Training Provider)||Training|
| 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.
|Speakers must sign a Speaker Agreement||Speakers|
|Speakers will not receive compensation for their speaking engagement||Speakers|
|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
Date of last update: 2010-07-10 Updated by: Mark Bristow
Accomplishments for this Month
Planned for Next Month