[Global_conference_committee] GCC VOTE: OWASP GCC 2011 Plan
Ralph Durkee
ralph.durkee at owasp.org
Mon Dec 20 17:14:03 EST 2010
I'm going to have to vote no for now.
On 12/20/2010 10:18 AM, Mark Bristow wrote:
> All,
>
> Here is the new Vote thread for the GCC. Please, let's not have any
> debate in this thread as this is for the VOTE. If you feel that we
> should not approve because it requires additional debate, simply vote
> to deny the motion. I've pulled in the changes from the other thread
> already.
>
> We will be using the new voting rules as listed here:
> http://www.owasp.org/index.php/Global_Conferences_Committee_Governance
>
> Thanks,
> -Mark
>
> Mark Bristow: Approve
> John Wilander:
> Lucas Ferreira:
> Richard Greenberg:
> Ralph Durkee:
> Neil Matatall:
> Cassio Goldschmidt:
>
>
> ===============================
>
> *Goals*
>
> 1. Have a Global Appsec in NA, SA, EU, Asia in 2011
> 2. Promote OWASP Projects/Initiatives at OWASP Conferences
> 3. Enhance Services for Conference Planners
> 4. Reach out to developers (have 20% of attendees in a dev position)
> 5. Reach out to non-members (have 70% of attendees at cons non-members)
> 6. Bring more into the fold (Generate 300 new/renewed members at
> conferences)
> 7. Streamline Sponsorships (Global Conference Sponsors, Targeted
> Conference Sponsors)
> 8. Revise GCC Governance
> 9. Have a profit of $200k in 2011 across all conferences
>
>
> *Policy Changes*
>
> * Change Conference Types to include:
> o OWASP Global AppSec Conferences (Currently
> AppSec Conferences)
> o OWASP Regional/Theme Conference (currently
> Regional, all regional cons will be encouraged have to
> have a unique
>
>
> theme, development, Research, PHP, Government, Browsers …..)
> * GCC Member attendance at conferences Global AppSec
> and Regional/Theme level cons (as available by GCC members and
> budget)
> o GCC Representative shall not be intimately involved with
> the conference planning to provide an objective assessment.
> o Members will have the opportunity to request travel to
> scheduled events and travel will be assigned based on
> proximity to the event, cost and member availability.
> o GCC member shall interface with the local planning
> committee at least 1 month before trip (attend planning call)
> o Interact with planners/attendees while at conference
> o Interact with Sponsors
> o At the next GCC meeting the traveling member will be
> expected to provide an post trip report covering
> + Assessment of facility
> + Event Marketing Strategy
> + Examination of Event Budget
> + Estimation of Speaker Quality
> + Sponsor engagement/cost-effectiveness & feedback
> + Any notable comments from planners/attendees
> + Any unique outstanding elements
> + Any issues
> * GCC Member signature authority for OWASP
> (Leverage By-Lawys Article VI Section 1 - Designate as Agent)
> o Alleviate need of OWASP Board to sign contracts (currently
> a significant bottleneck)
> o All conference related contracts will be required to go
> through the GCC
> o In general will be responsibility of Chair, however all
> committee members shall be authorized to sign on
> conference business (no single point of failure)
> o GCC members will not be permitted to sign contracts for
> conferences they organize (except when signature is
> required immediately)
> o Will be offered up before the board
> * All OWASP Branded events MUST use the new conference management
> system
> o For OWASP Events only, not applicable to regular chapter
> meetings
> o It’s important to manage the schedule and enforce brand
> management
> o Any conference not registered & approved will not receive
> OWASP funds or support
> o Will take effect once system is in place
> * All Global AppSec conferences must accommodate
> an OWASP Track
> o Will not represent more than 1/3 of content (can be half
> day, full day, full conference as applies to the
> individual conference)
> o Joint venture with Projects Committee
> o Regional/theme events will have this available to them
>
> *Initiatives*
>
> * OWASP Conference management system (Goal 1, 3)
> o We need a system to take in applications for events, vett
> them, approve them, and schedule them. The current
> process of people emailing Kate, Me or the board is not
> acceptable with the number of events we have
> o I see this as critical to establishing control over the
> OWASP schedule and is a top priority
> * OWASP AppSec Track (Goal 2)
> o Partnership with projects committee
> o Have a cadre of speakers, ready to go with presentations
> about OWASP projects/activities
> o Require all OWASP Regional and AppSec events to have an
> “OWASP Track” of at least 6 presentations from this pool,
> managed, selected, and funded by the GCC and the GPC
> * OWASP Global Conference Sponsors (Goal 3, 7)
> o Provide unified sponsorships for the Global AppSec Conferences
> o Split revenues among individual conferences budget
> o Streamlines our sponsorships
> o Conference planners are welcome to elicit additional
> sponsorships
> * Central conference support services
> (Goal 3)
> o Investigate for-hire international conference support
> companies
> + Event logistics companies
> o Investigate costs for hiring conference organizer
> + Foundation Employee
> * Conference Marketing (Goal 3)
> o OWASP Conference Twitter accounts
> o OWASP Conference Domain Names
> + Register Names only
> + http://www.AppSecNA.org <http://www.appsecna.org/>
> + http://www.AppSecUS.org <http://www.appsecus.org/>
> + http://www.AppSecEU.org <http://www.appseceu.org/>
> + http://www.AppSecAsia.org <http://www.appsecasia.org/>
> + http://www.AppSecSA.org <http://www.appsecsa.org/>
> + If already owned by a conference, buy them
> out/transfer to GCC Control
> + GCC will re-direct to any hosting service once the
> conference has been assigned
> + Conference can still register AppSecXX2011.org and
> we can just redirect as appropriate
> + Helps maintain consistency in URLs between years
> o Conference Twitter Accounts
> + Like domains, turned over to planners for their use
> as appropriate
> + @OWASPConfrences – held by the GCC for announcements
> + @OWASPAppSec – held by the GCC for announcements
> + @AppSecNA
> + @AppSecUS
> + @AppSecEU
> + @AppSecAsia
> + @AppSecSA
> o Use of Short URLS on the owasp.org <http://owasp.org/> website
> + ex https://owasp.org/AppSecBR points to the wiki
> page for this year’s conference
> o Regional Targeted Mailing Lists
> + To reduce OWASP All traffic
> * OWASP Merchandise Model(Goal 3, Goal9)
> o A shippable “OWASP Store” with OWASP branded items for
> sale at conferences
> o Already exists, just need to formalize
> * OWASP Conference Marketing (global, regional, electronic, print)
> (Goal 4,5,6)
> o Procure Booth space at developer focused conferences
> o Provide budget for OWASP Schwag for use at OWASP Booths in
> other conferences
> o Evaluate other advertising mechanisms for conferences
>
> *Budget*
>
> * $7500 for conference support (schwag/tables) targeting developer
> conferences
> * $500 OWASP GCC Technology Needs
> o Domain Names
> o Other tech solutions + planning tools
>
>
> * $15,000, OWASP Track Travel expenses (cap, will try and get indv
> company sponsorships)
> * $10,000 GCC Member at all conferences (approx $1500/AppSec, $800
> Regional)
> * Budget requires board approval
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/global_conference_committee/attachments/20101220/89feba9e/attachment-0001.html
More information about the Global_conference_committee
mailing list