[Global_conference_committee] 2013 OWASP Summit

Thu Jun 16 17:21:48 EDT 2011

Any additional comments on the path forward?  I'd like to get a mailing list
setup for this initative, assemble the team and start the planning process

On Tue, Jun 7, 2011 at 12:50 PM, Mark Bristow <mark.bristow at owasp.org>wrote:

> Helen,
>
> This was just a thought of mine for a way to increase the attractiveness of
> being an OWASP global sponsor.
>
> -Mark
>
>
> On Tue, Jun 7, 2011 at 9:20 AM, Helen Gao <heleng at owasp.org> wrote:
>
>> Hi, Mark.
>>
>> I believe global conference sponsorship has great potential.  Could you
>> tell me what you mean by "perhaps global sponsorship packages come with an
>> exclusive Summit sponsorship"?
>>
>> On Mon, Jun 6, 2011 at 11:36 AM, Mark Bristow <mark.bristow at owasp.org>wrote:
>>
>>> GCC,
>>>
>>> As per my thread to the board this morning it looks like we are on the
>>> hook for planning the next summit in 2013.  I think this is a good thing as
>>> we have the most experience in planning large scale events.  One major
>>> difference between the Summit and a normal conference is the content.  This
>>> year, almost all of the sessions were setup as working sessions rather than
>>> "speaking" style sessions.  I think this worked out really well and seemed
>>> to be very well received by the attendees there were definitely some areas
>>> that could be improved with our execution of this (web
>>> participants especially) but I think with some more up-front
>>> scheduling/planning we can make this even more successful.  One thing I
>>> think is important is to start planning this event EARLY, in fact we may
>>> already be a bit late in getting started.  I know for some of us this means
>>> we may have to plan two events simultaneously but hey, we did volunteer to
>>> be on this committee right? :-P
>>>
>>> In general I think we should aim for:
>>>
>>>    - An accessible event
>>>       - In a "hub" city with easy access to the venue for intl travelers
>>>       (we should discuss the virtues of an in-town vs somewhat remote venue,
>>>       isolated venues keep everyone on the property)
>>>       - Better web/telepresence support
>>>       - Social Media Integration
>>>       - Low cost for paid attendees
>>>       - Target 500 attendees
>>>    - A Collaborative Event
>>>       - Working sessions
>>>       - Collaborative environment ("Code Jam" areas, Villas, Small "BOF"
>>>       areas for ad-hoc meetings)
>>>       - Networking/Meet new people/share ideas in the bar, networking
>>>       events, fun stuff, organized optional trips....
>>>    - A Productive Event
>>>       - Capture Outcomes in (near) real time
>>>       - Provide a ecosystem for innovation instead of a prescription for
>>>       it
>>>       - Ensure the right people are there to make the biggest impact
>>>       (OWASP Leaders, Leaders in AppSec, Browsers, Mobile, Developers,
>>>       Managers.....)
>>>
>>> Here's my proposed plan, there are lots of details in each of these
>>> steps, but this is high level, some items can be worked simultaneously:
>>>
>>>    1. Work with the Board to establish a sensible budget for the event.
>>>     Last year the foundation spent about $180k on the event (total cost was
>>>    almost $240k, incl all travel).  I'm honestly not sure what our projected
>>>    2013 COH will look like so we need to get this number from the board.
>>>    2. Generate a straw man budget based on the Foundation $ that can be
>>>    used and targets for sponsorship (perhaps global sponsorship packages come
>>>    with an exclusive Summit sponsorship?).  The budget should break out:
>>>       1. Operational Budget (facility, AV etc)
>>>       2. Logistical Support (Having full time staff on this is a must)
>>>       3. Catering/Entertainment
>>>       4. OWASP Funded Attendee Travel/Lodging
>>>    3. Develop a list of target cities for investigation by the Summit
>>>    team
>>>    4. Send out survey to OWASP Steakholders looking for topics,
>>>    suggestions, like/dislikes from the last summit
>>>    5. Work with OWASP Leaders for conceptual content ideas that may
>>>    impact venue choices (lots of small rooms for BoF, need lots of internet
>>>    pipe, remote participation needs.....)
>>>    6. Develop evaluation criteria for selecting a venue
>>>    7. Send out a call for venues (we can use OCMS to manage these)
>>>       1. Send directly to some venues/tourism boards in target cities
>>>       2. Send to OWASP Leaders for local teams to propose sites
>>>    8. Review submissions, select venue and set event date (Thinking Q1
>>>    or Q2 of 2013 would be good but should vary with location) - I think we
>>>    should have this complete by Sept/Oct of this year.
>>>    9. Work to develop "scheduled" content plan and allocate space for
>>>    the "unscheduled" stuff
>>>    10. Define lodging options and develop packages for paid attendees
>>>    (may want to secure outside travel support at this point)
>>>    11. Define criteria for sponsored attendees
>>>    12. Begin to work logistics (Travel, Lodging, AV, Catering ......) at
>>>    this point in time, these actives are a bit far out to plan well.
>>>
>>> Thoughts?  Comments? Rude Remarks?
>>>
>>> --
>>> Mark Bristow
>>> (703) 596-5175
>>> mark.bristow at owasp.org
>>>
>>> OWASP Global Conferences Committee Chair - http://is.gd/5MTvF
>>> OWASP DC Chapter Co-Chair - http://is.gd/5MTwu
>>> AppSec DC Organizer - https://www.appsecdc.org
>>>
>>>
>>> _______________________________________________
>>> Global_conference_committee mailing list
>>> Global_conference_committee at lists.owasp.org
>>> https://lists.owasp.org/mailman/listinfo/global_conference_committee
>>>
>>>
>>
>>
>> --
>> Helen Gao
>>
>
>
>
> --
> Mark Bristow
> (703) 596-5175
> mark.bristow at owasp.org
>
> OWASP Global Conferences Committee Chair - http://is.gd/5MTvF
> OWASP DC Chapter Co-Chair - http://is.gd/5MTwu
> AppSec DC Organizer - https://www.appsecdc.org
>
>

-- 
Mark Bristow
(703) 596-5175
mark.bristow at owasp.org

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