[Global_conference_committee] Experience with UK Conference?

Mark Bristow mark.bristow at owasp.org
Fri Nov 19 20:42:08 EST 2010


Debbie,

We have not hosted an AppSec in the UK.  However I've copied the local
chapter leader Justin Clarke to see if he has any insights.

-Mark

On Fri, Nov 19, 2010 at 10:36 PM, Debbie Christofferson <
debbiechristofferson at earthlink.net> wrote:

> Do any of you have experience with conference in UK area?
> We are looking to host our first conference for ISSA CISO Executive Forum
> and possibly to partner.
> We have a very active UK chapter, hence the decision to host in UK.
> Likely we will partner, although that is a decision to be determined on
> best way to approach and our UK chapter will be very involved in process and
> decisions, plus our planning team for the European 2011 event.
>
> Thank you so much for feedback!
> Debbie Christofferson, CIPP/IT, CISSP, CISM
> ISSA International Board Director & Chair CISO Advisory Council
> 480-988-4194
> DebbieChristofferson at earthlink.net
> >From Phoenix Arizona Base
>
>
> -----Original Message-----
> >From: global_conference_committee-request at lists.owasp.org
> >Sent: Nov 19, 2010 12:40 PM
> >To: global_conference_committee at lists.owasp.org
> >Subject: Global_conference_committee Digest, Vol 25, Issue 10
> >
> >Send Global_conference_committee mailing list submissions to
> >       global_conference_committee at lists.owasp.org
> >
> >To subscribe or unsubscribe via the World Wide Web, visit
> >
> https://lists.owasp.org/mailman/listinfo/global_conference_committee
> >or, via email, send a message with subject or body 'help' to
> >       global_conference_committee-request at lists.owasp.org
> >
> >You can reach the person managing the list at
> >       global_conference_committee-owner at lists.owasp.org
> >
> >When replying, please edit your Subject line so it is more specific
> >than "Re: Contents of Global_conference_committee digest..."
> >
> >
> >Today's Topics:
> >
> >   1. GCC 2011 Draft Plan (Mark Bristow)
> >
> >
> >----------------------------------------------------------------------
> >
> >Message: 1
> >Date: Fri, 19 Nov 2010 16:41:00 -0200
> >From: Mark Bristow <mark.bristow at owasp.org>
> >Subject: [Global_conference_committee] GCC 2011 Draft Plan
> >To: Eoin <eoin.keary at owasp.org>, John Wilander
> >       <john.wilander at owasp.org>,      Kate Hartmann <
> kate.hartmann at owasp.org>,
> >       Lucas Ferreira <lucas.ferreira at owasp.org>,      Mark Bristow
> >       <mark.bristow at owasp.org>, Neil Matatall <neil at owasp.org>,
> Ralph
> >       Durkee <ralph.durkee at owasp.org>,        Richard Greenberg
> >       <richard.greenberg at owasp.org>
> >Cc: global_conference_committee
> >       <global_conference_committee at lists.owasp.org>
> >Message-ID:
> >       <AANLkTikA_wc76gsLH330HUK8u3kV9jbTd1G-AxPCC0_e at mail.gmail.com>
> >Content-Type: text/plain; charset="windows-1252"
> >
> >GCC,
> >
> >
> >
> >After the outcomes of our meetings, several conversations with some of
> you,
> >the board, OWASP Members and my own thoughts, and with the Summit coming
> up,
> >I?ve been putting together a straw man plan and goals for the GCC in
> >2011.  This
> >is a bit of a long document, and there are more questions than answers in
> >many places, but I think it?s a good start and appreciate your inputs and
> >comments.
> >
> >
> >I'd like to have a meeting in early December to discuss and vote on a plan
> >to refine into Portugal.
> >
> >
> >Available in google doc form here:
> >
> https://docs.google.com/a/owasp.org/document/d/1sOs9dY9zKLlLaaJMcOvz2nhM8T2OAWQlVciAGM5c5XA/edit?hl=en
> >
> >
> >
> >*General Thoughts*
> >
> >How do we better engage developers?  How do we provide significant value
> to
> >them and encourage them to come to conferences?  We need to improve in
> this
> >area to help further the OWASP mission.
> >
> >
> >
> >*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:
> >      - OWASP Global AppSec Conferences (Currently AppSec Conferences)
> >      - OWASP AppSec Conferences (can only be used by global cons, and by
> >      conferences who have already used this name twice by the end of
> >2011, moving
> >      forward, only new Global AppSecs can use this name)
> >      - OWASP Regional/Theme Conference (currently Regional, all regional
> >      cons will now have to have a unique theme, development, PHP,
> Government,
> >      Browsers ?..)
> >   - GCC Member attendance at conferences Global AppSec and Regional/Theme
> >   level cons (as available by GCC members and budget)
> >   - GCC Member signature authority for OWASP (Leverage By-Lawys Article
> VI
> >   Section 1 - Designate as Agent)
> >      - Alleviate need of OWASP Board to sign contracts (currently a
> >      significant bottleneck)
> >      - All conference related contracts will be required to go through
> the
> >      GCC
> >      - In general will be responsibility of Chair, however all committee
> >      members shall be authorized to sign on conference business (no
> >single point
> >      of failure)
> >      - GCC members will not be permitted to sign contracts for
> conferences
> >      they organize (except when signature is required immediately)
> >      - Requires Board Vote
> >   - All OWASP Branded events MUST use conference mgmt system to use brand
> >   (must be enforced)
> >      - See initiatives
> >      - It?s important to manage the schedule and enforce brand management
> >      - Any conference not registered & approved will receive no funds or
> >      support
> >   - All Global AppSec and Regional/Theme conferences must have OWASP
> Track
> >      - See Initiatives, joint venture with Projects Committee
> >
> >
> >
> >*Initiatives*
> >
> >   - OWASP Conference management system (Goal 1, 3)
> >      - 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
> >      - I see this as critical to establishing control over the OWASP
> >      schedule and is a top priority
> >   - OWASP AppSec Track (Goal 2)
> >      - 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 Con Sponsors (Goal 3, 7)
> >      - Provide unified sponsorships for the Global AppSec Conferences
> >      - Split revenues among individual conferences budget
> >      - Streamlines our sponsorships
> >      - Does not interfere with existing conference sponsorships
> >   - Central conference support services  (Goal 3)
> >      - Investigate for-hire international conference support companies
> >      - Investigate costs for hiring conference organizer
> >      - Get board approval
> >   - Conference Marketing (Goal 3)
> >      - OWASP Conference Twitter accounts
> >      - OWASP Conference Domain Names
> >         - Register Names only
> >         - http://www.AppSecNA.org
> >         - http://www.AppSecUS.org
> >         - http://www.AppSecEU.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 AppSecUS2011.org and we can just
> >         redirect as appropriate
> >         - Helps maintain consistency in URLs between years
> >      - 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
> >      - Use of Short URLS on the owasp.org website
> >         - ex https://owasp.org/AppSecBR points to the wiki page for this
> >         year?s conference
> >      - Regional Targeted Mailing Lists
> >         - To reduce OWASP All traffic
> >       - OWASP Merchandise Model(Goal 3, Goal9)
> >      - A shippable ?OWASP Store? with OWASP branded items for sale at
> >      conferences
> >      - Already exists, just need to formalize
> >   - OWASP Conference Marketing (global, regional, electronic, print)
> (Goal
> >   4,5,6)
> >      - Procure Booth space at developer focused conferences
> >      - Provide budget for OWASP Schwag for use at OWASP Booths in other
> >      conferences
> >      - Evaluate other advertising mechanisms for conferences
> >
> >
> >
> >*Budget*
> >
> >
> >   - $200k 2011 target conference revenue (Goal 9)
> >   - $5000 for conference support (schwag/tables) targeting developer
> >   conferences
> >   - $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)
> >
> >
> > *Governance *
> >
> >   - Using existing OWASP By-Laws as guide, establish rules for committee
> >   - Define process for member election, evaluation and resignation
> >   - Define process for chair election, evaluation and resignation
> >   - Define GCC  Service Term (With or Without Term Limits)
> >   - Committee member requirements
> >
> >
> >
> >*Technology Needs*
> >
> >   - Global_Conferences_Committee at owasp.org account (managed by chair,
> >   redirects to all GCC Members, for registration of domains, twitter et
> all)
> >   - Regional Mailing List solution
> >   - Short URLS (http://www,owasp.org/AppSecBR)
> >   - http://conferences.owasp.org (redirect to conference wiki page)
> >   - Event Management Solution
> >   - Conference Twitter/Email Accounts/domain names
> >
> >
> >
> >--
> >Mark Bristow
> >
> >OWASP Global Conferences Committee Chair - http://is.gd/5MTvF
> >AppSec DC 2010 Organizer - https://www.appsecdc.org
> >OWASP DC Chapter Co-Chair - http://is.gd/5MTwu
> >-------------- next part --------------
> >An HTML attachment was scrubbed...
> >URL:
> https://lists.owasp.org/pipermail/global_conference_committee/attachments/20101119/4439bcdf/attachment.html
> >
> >------------------------------
> >
> >_______________________________________________
> >Global_conference_committee mailing list
> >Global_conference_committee at lists.owasp.org
> >https://lists.owasp.org/mailman/listinfo/global_conference_committee
> >
> >
> >End of Global_conference_committee Digest, Vol 25, Issue 10
> >***********************************************************
>
>
> Debbie Christofferson, CISSP, CISM
> 480-988-4194
> DebbieChristofferson at earthlink.net
> _______________________________________________
> Global_conference_committee mailing list
> Global_conference_committee at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/global_conference_committee
>



-- 
Mark Bristow

OWASP Global Conferences Committee Chair - http://is.gd/5MTvF
AppSec DC 2010 Organizer - https://www.appsecdc.org
OWASP DC Chapter Co-Chair - http://is.gd/5MTwu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/global_conference_committee/attachments/20101119/9053400d/attachment-0001.html 


More information about the Global_conference_committee mailing list