Difference between revisions of "How to Host a Conference/Policies and Requirements"

From OWASP
Jump to: navigation, search
m
Line 1: Line 1:
 
<font size=2pt>
 
<font size=2pt>
 
These are the requirements imposed on any event using the OWASP brand.  All Events must be coordinated with the Foundation and receive pre-approval.  Event requests should be submitted via the [https://ocms.owasp.org/ OWASP Conference Management System (OCMS)].  If you do not have an account, you can signup for an OCMS account [https://ocms.owasp.org/accounts/register here], please use an @owasp.org email address if available.
 
These are the requirements imposed on any event using the OWASP brand.  All Events must be coordinated with the Foundation and receive pre-approval.  Event requests should be submitted via the [https://ocms.owasp.org/ OWASP Conference Management System (OCMS)].  If you do not have an account, you can signup for an OCMS account [https://ocms.owasp.org/accounts/register here], please use an @owasp.org email address if available.
 +
 +
  
 
{{:Global Conferences Committee/Policies}}
 
{{:Global Conferences Committee/Policies}}
  
 
</font>
 
</font>

Revision as of 23:29, 31 March 2013

These are the requirements imposed on any event using the OWASP brand. All Events must be coordinated with the Foundation and receive pre-approval. Event requests should be submitted via the OWASP Conference Management System (OCMS). If you do not have an account, you can signup for an OCMS account here, please use an @owasp.org email address if available.


If you have questions or require an exception to any of these please contact the OWASP Staff.

Comprehensive tracking of committee votes was not started until January 2011, policies with an NA entered into the "votes" column were conducted before this policy was implemented. Although the Global Conference Committee was retired effective April 1, 2013, the policies established by the committee remain in full effect.

Policy Rationale Last Updated Applicability Votes
All content must be vendor neutral OWASP Core Value N/A All Events - Core Value N/A
All content must be made available to the public after the conference OWASP Core Value N/A All Events - Core Value N/A
All calls for papers, training and registration must be open to the public OWASP Core Value N/A All Events - Core Value N/A
All events must be conducted in a manner consistent with the OWASP Mission, Principles and Code of Ethics OWASP Core Value N/A All Events - Core Value N/A
OWASP Event Definitions These definitions were established to define the different categories of OWASP events to support OWASP GCC Planning and Policies. 12/22/2010 All Events Vote Thread
OWASP Event Requirements These definitions were established to define requirements imposed on individual events by type. N/A All Events N/A
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
  • Global AppSec Conference - 10% of event profits up to Profit Goal set in annual Foundation Budget($10,000 for multi-chapter events), 40 % of event profits in excess of Profit Goal. No profit cap.
  • Local and Regional Events - 90% of event profits up to $5,000 USD, 40% of event profits in excess of $5,000 USD. No profit cap.
In addition to the Membership Committee membership split that provides funds to local chapters, it is also appropriate to allow local chapters to leverage the hard work that goes into planning events as additional revenue streams. The board considered weighing the needs of the OWASP Foundation, Local Chapters entrepreneurship, the desire not to create "haves and have not" chapters within OWASP in addition to many other factors when setting this policy. 2012/12/05 All Events Board Voting Record
All Events must be coordinated with the Global Conferences Committee and receive their approval These ensures coordination of event schedules, content and budget priorities N/A All Events N/A
Events must have an OWASP Wiki Page The Wiki remains the authoritative source of OWASP information N/A All Events N/A
Only OWASP Board members or their designates may enter into contracts on behalf of the foundation Required by the OWASP By-Laws N/A All Events N/A
All finances must be handled by the OWASP Foundation unless exceptions are granted by the Global Conferences Committee This ensures the central management of Foundation resources for activities occurring under the OWASP Brand N/A All Events N/A
Free admission should be made available for OWASP Leaders, Committee and Board members OWASP Board Decision N/A All Events N/A
OWASP individual members in good standing shall receive $50 off admission to all OWASP events charging more than $50 entry fee. OWASP Membership Perk N/A All Events N/A
A complete budget must be submitted and approved by the Global Conferences Committee It is the responsibility of the Global Conferences Committee to ensure that OWASP Foundation resources are appropriately managed as it relates to OWASP conferences. This requirement ensures GCC visibility into conference expenditures and allows the GCC to assist where appropriate. N/A Regional/Theme Conferences N/A
A board member must be present at all OWASP AppSec and Regional Conferences to provide a welcoming statement OWASP Board Decision N/A Regional/Theme Conferences N/A
Global AppSec Conferences must include training As the flagship events for OWASP Global AppSec Conferences must also have a training component. N/A Global AppSec Conferences N/A
Global AppSec Conferences must charge an admission fee Global AppSec Conferences are large expenditures for the OWASP foundation. In order to ensure that the foundation can recover some or all of these costs, an admission fee must be charged. N/A Global AppSec Conferences N/A
Sessions must be recorded and posted to the public after the conference As the flagship events for OWASP Global AppSec Conferences must also provide video coverage and post it post conference. See the [Global Conference Resources] for information on additional resources. N/A Global AppSec Conferences N/A
There must be at least one networking event at the conference As the flagship events for OWASP Global AppSec Conferences must have a networking event. N/A Global AppSec Conferences N/A
All Training providers are required to sign a Training Instructor Agreement Clearly outline responsibilities and provide some legal cover for the foundation. N/A Training N/A
Training revenue will be split 60/40 (OWASP/Training Provider) GCC has set what it considers a fair policy in order to share training profits with training providers N/A Training N/A
Free training should be made available for OWASP Leaders. This must be included in the Training Instructor Agreement Board Policy N/A Training N/A
Speakers must sign a Speaker Agreement The allows OWASP to use the speaker's materials as well as their likeness as well as set some boundaries for content. Electronic signatures are permissible. N/A Speakers N/A
Speakers will not receive compensation for their speaking engagement This policy allows OWASP to keep admissions costs low so that OWASP can help spread knowledge of application security issues to the widest audience. Exceptions to this policy may be granted in certain cases so contact the Global Conferences Committee if you need an exception. N/A Speakers N/A