[Global_conference_committee] ACTION REQUIRED: New "Rochester Security Summit " event application

Mon Apr 4 17:01:11 EDT 2011

Most partner events do not include significant costs and are more
co-marketing then a co-sponsored event.

A co-marketed event generally involves OWASP promoting the event with the
event providing OWASP a booth and using the OWASP logo in their promotion,
OWASP isn't involved at all in the planning.  On occasion OWASP is asked to
pride small items (like lanyards) outside of the marketing materials needed
to support the OWASP presence (mostly at no-charge events).  OWASP generally
receives no financial compensation for this.

A co-hosted event is one where OWASP and the other organization(s) all
contribute to the planning, event management, promotion and other aspects of
the event.  In these cases OWASP has a direct presence on the conference
organizing team and may provide either cash or items to directly support the
conference.  This might be paying for the Venue, Catering, Schwag, Speaker
Travel et all.  OWASP also will get involved in managing the content in
these events (as if it's not vendor agnostic content, OWASP would have to
pull out as it violates our core values) and may/may not provide speakers at
the overall event management team's discretion.  From a financial
perspective OWASP assumes both the risk of a loss and a portion of the
profits from the event.

I think RSS fits somewhere in the middle here.  However if we are going to
be supplying the event schwag, lanyards, and speaker travel, I'd like to see
some commitment on the financial side (profit or loss) and I'd likely
categorize it as a partnered-regional event.

-Mark

On Mon, Apr 4, 2011 at 4:43 PM, Ralph Durkee <ralph.durkee at owasp.org> wrote:

>  I'm not sure what the difference would be.  The arrangement seemed similar
> to other partner events.
>
> -- Ralph
>
>
> On 4/4/2011 4:09 PM, Mark Bristow wrote:
>
> So we do not have a partnering agreement then?  This is an ISSA event which
> your asking OWASP to support?
>
> On Mon, Apr 4, 2011 at 3:45 PM, Ralph Durkee <ralph.durkee at owasp.org>wrote:
>
>>  I'm CC-ing Andrea Cogliati, as he was last year and still is the OWASP
>> Rochester Chapter President, and was the primary contact.
>>
>> There was no profit/loss agreement, so there was no opportunity for a loss
>> for OWASP.  After the event Rochester ISSA shared revenue with OWASP through
>> the Rochester Chapter donate paypal.   I think the cost of the shwag was
>> subtracted from that amount, and the rest was allocated to the Rochester
>> Chapter.
>>
>> -- Ralph
>>
>> On 4/4/2011 3:23 PM, Mark Bristow wrote:
>>
>> How did profit/loss sharing work?
>>
>> On Mon, Apr 4, 2011 at 3:16 PM, Ralph Durkee <ralph.durkee at owasp.org>wrote:
>>
>>>  There wasn't a formal agreement last year, but through email the
>>> agreement was pretty much the same as what is proposed for this year, except
>>> that the lanyards and give-aways were for 200 attendees instead of 300.  Tom
>>> B was scheduled to speak, but had to cancel due to a conflict, so OWASP only
>>> cover the cost of one speaker instead of 2 last year, but the plan was for 2
>>> speakers last year.
>>>
>>> -- Ralph
>>>
>>>
>>>
>>>
>>> On 4/4/2011 3:06 PM, Tom Brennan wrote:
>>>
>>> Show him last years "agreement"
>>>
>>> On Apr 4, 2011, at 1:45 PM, Ralph Durkee <ralph.durkee at owasp.org> wrote:
>>>
>>>   By hard $ are you referring to something other than shwag give-aways
>>> or speaker?
>>>
>>> On 4/4/2011 2:01 PM, Mark Bristow wrote:
>>>
>>> Well this is a different type then others we have actively working.
>>>
>>> When we are asked to put up hard $ as a partner, there is usually a
>>> description of how the profits/loss will be distributed.
>>>
>>>  On Mon, Apr 4, 2011 at 1:57 PM, Ralph Durkee <ralph.durkee at owasp.org>wrote:
>>>
>>>>  Agreed on the thousands, the concept was that each provides comparable
>>>> value estimated at about $3,100 in the agreement.   How is this much
>>>> different from other partner agreements?
>>>>
>>>>
>>>>
>>>> On 4/4/2011 1:37 PM, Mark Bristow wrote:
>>>>
>>>> Ralph,
>>>>
>>>> I'd disagree.  It appears that OWASP is being asked to bring significant
>>>> (at least for us) resources for this event.  I'd like to know if/how we plan
>>>> to recover those costs and what recovery schedule is between the different
>>>> organizations.  We may have done it a bit more loosly in the past, however
>>>> we are going to need to work to get a better handle on these types events
>>>> where OWASP has a more active participation beyond a co-marketing agreement.
>>>>
>>>> Looking at the agreement, OWASP is being asked to provide:
>>>>
>>>>    - 300 Attendees of Schwag
>>>>    - 2 Speakers
>>>>    - 300 Attendees of Lanyards
>>>>    - Standard "booth" stuff (Promotional materials for vendor table,
>>>>    co-marketing items)
>>>>
>>>> 300 Schwag and Lanyards can cost thousands of dollars in addition to
>>>> thousands of dollars in travel for speakers.
>>>>
>>>> -Mark
>>>>
>>>> On Mon, Apr 4, 2011 at 1:19 PM, Ralph Durkee <ralph.durkee at owasp.org>wrote:
>>>>
>>>>>  They talked about it, and the RSS, ISSA and local OWASP leadership
>>>>> didn't seem to think the formal revenue loss/share agreement was not
>>>>> appropriate, necessary or fit well with the typical partnership agreement.
>>>>> We didn't have a formal agreement last year, and yet there was informal
>>>>> revenue sharing through the chapter donation.  For one thing it would seem
>>>>> inappropriate for the GCC / and/or the OWASP board to agree to a potential
>>>>> revenue loss, for a third party conference.  it certainly brings a lot of
>>>>> complexity to something that should be a simple agreement similar to other
>>>>> partner conferences.
>>>>>
>>>>> -- Ralph
>>>>>
>>>>> On 4/4/2011 10:52 AM, Mark Bristow wrote:
>>>>>
>>>>> Ralph.  I just looked over the partner agreement.  What are the splits
>>>>> for profits/sponsorship dollars from the conference?  I noticed this was not
>>>>> in there.
>>>>>
>>>>> On Wed, Mar 23, 2011 at 9:54 PM, Ralph Durkee <ralph.durkee at owasp.org>wrote:
>>>>>
>>>>>>  Yes it was reviewed in a meeting Monday with local OWASP leadership
>>>>>> and tonight with the RSS leadership, next the ISSA officers.  Hope to have
>>>>>> it ready for committee review by Friday.
>>>>>>
>>>>>> -- Ralph
>>>>>>
>>>>>>
>>>>>> On 3/23/2011 5:17 PM, Mark Bristow wrote:
>>>>>>
>>>>>> Ralph,
>>>>>>
>>>>>> Any movement on that partner agreement?
>>>>>>
>>>>>> On Tue, Mar 22, 2011 at 11:50 AM, OWASP Conference System <
>>>>>> conferences at owasp.org> wrote:
>>>>>>
>>>>>>> Global Conferences Committee,
>>>>>>>
>>>>>>> A new event "Rochester Security Summit " on 2011-10-04 to 2011-10-05
>>>>>>> has been submitted for review.  Additional details are below:
>>>>>>>
>>>>>>> Name: Rochester Security Summit
>>>>>>> Type: Partner Event
>>>>>>> Details: http://ocms.owasptools.org/events/26
>>>>>>>
>>>>>>> Venue: Hyatt
>>>>>>> Event URL: http://www.rochestersecurity.org/
>>>>>>> Host Chapter: Rochester OWASP
>>>>>>>
>>>>>>> The Rochester Chapter of the Information Systems Security Association
>>>>>>> (ISSA), in association with  Rochester Chapter of the Open Web Application
>>>>>>> Security Project (OWASP), is pleased to announce that the 6th Annual
>>>>>>> Security Summit will be held Tuesday October 4th and Wednesday October 5th,
>>>>>>> 2011 in Rochester NY. The conference will be held 8:00 AM to 5:00 PM each
>>>>>>> day.
>>>>>>>
>>>>>>> Partner Org: Rochester ISSA Chapter
>>>>>>> Facility Cost: 0.00
>>>>>>> Operations Cost: 0.00
>>>>>>> Partner Agreement: TBD
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> http://ocms.owasptools.org/events/26
>>>>>>>
>>>>>>> Regards,
>>>>>>> The OCMS System
>>>>>>> _______________________________________________
>>>>>>> Global_conference_committee mailing list
>>>>>>> Global_conference_committee at lists.owasp.org
>>>>>>> https://lists.owasp.org/mailman/listinfo/global_conference_committee
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>
>>>   _______________________________________________
>>> Global_conference_committee mailing list
>>> Global_conference_committee at lists.owasp.org
>>> https://lists.owasp.org/mailman/listinfo/global_conference_committee
>>>
>>>
>>
>>
>> --
>> Mark Bristow
>> (703) 596-5175 <%28703%29%20596-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
>
>

-- 
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/20110404/8321efe6/attachment-0001.html 