[Global_chapter_committee] [Global_conference_committee] [owasp-board] Re: [Committees-chairs] 2012 Speaker Agreement Update

Seba seba at owasp.org
Wed Mar 28 18:27:26 UTC 2012


A general remark from my side: only use the speaker agreement when in doubt.
We use this agreement very pragmatically in Belgium and have only pointed
to it upfront to speakers when we thought a certain speaker/topic could
become a commercial talk.

Otherwise: minimize the red tape :-)

--seba

On Wed, Mar 28, 2012 at 8:22 PM, Teresa Stevens <
teresa-ann-stevens at comcast.net> wrote:

> I agree with Josh. Thanks,
>
> Teresa Stevens, CISSP, MSIA, PMMC
> Information Security Specialist – Team Leader
> San Francisco Bay Area
> 510-842-8868 (home), 510-872-2187 (cell)
>
>
> From: Josh Sokol <josh.sokol at owasp.org>
> Date: Wed, 28 Mar 2012 11:13:22 -0500
> To: Mark Bristow <mark.bristow at owasp.org>
> Cc: "owasp-board at owasp.org" <owasp-board at owasp.org>, "
> committees-chairs at lists.owasp.org" <committees-chairs at lists.owasp.org>,
> global_conference_committee <global_conference_committee at lists.owasp.org>,
> global_chapter_committee Committee <
> global_chapter_committee at lists.owasp.org>, Eoin <eoin.keary at owasp.org>
> Subject: Re: [Global_chapter_committee] [Global_conference_committee]
> [owasp-board] Re: [Committees-chairs] 2012 Speaker Agreement Update
>
> I agree with what Jason said.  I see no reason why a person should not be
> able to include a company logo in a slide deck regardless of whether they
> are a corporate member or not.  My $0.02:
>
> * If the event has a presentation template, then corporate logos should be
> limited to only the "About Me" page of the presentation.
>
> ~josh
>
> On Wed, Mar 28, 2012 at 9:20 AM, Mark Bristow <mark.bristow at owasp.org>wrote:
>
>> I think these are reasonable changes except the no-logo on the "about me"
>> slide.  I think that's fine if we put a boundry on the size.  The GCC is in
>> the final process of selecting a new presentation template, so this will be
>> easy to add.
>>
>> On Tue, Mar 27, 2012 at 12:29 PM, Eoin <eoin.keary at owasp.org> wrote:
>>
>>> I am happy with vendor logo as long as content isn't a vendor pitch or
>>> vendor bespoke (ip) and covers off an issue which is in the open  body of
>>> knowledge.
>>>
>>>
>>> Eoin Keary
>>> BCC Risk Advisory
>>> Owasp Global Board
>>> +353 87 977 2988
>>>
>>>
>>> On 27 Mar 2012, at 16:13, Jason Li <jason.li at owasp.org> wrote:
>>>
>>> Agreed on the use of the template.
>>>
>>> What's the purpose of the restriction on the company logo?
>>>
>>> Is it an attempt to spur corporate membership? Is it meant to remove the
>>> "vendor"-ness of a talk?
>>>
>>> If the former, I think it actually comes across as off-putting and might
>>> have the opposite effect... If the latter, then the inclusion of the
>>> company logo if and only if they are an OWASP supporter seems overly
>>> restrictive IMHO in comparison to the goal.
>>>
>>> What about updating the template to include a specific place and limited
>>> small size for a logo and mandating the use of the template? That would
>>> limit how much a presenter could plaster their logo across a presentation.
>>>
>>> -Jason
>>>
>>> On Tue, Mar 27, 2012 at 9:35 AM, Tom Brennan <tomb at owasp.org> wrote:
>>>
>>>>
>>>> Committee(s);
>>>>
>>>> Today OWASP utilizes a Speaker Agreement that outlines the rules for
>>>> compensation of speakers, required templates, audio/visual, vulnerabilities
>>>> disclosure and a laundry list of other terms.
>>>>
>>>> The Document:  https://www.owasp.org/index.php/Speaker_Agreement
>>>>
>>>> With the upcoming long list of AppSec<Regional>, AppSec<Global> and
>>>> chapter events  globally happening weekly enforcement of this policy or
>>>> event policing of this policy is difficult however the spirit of the
>>>> speaker agreement in keeping OWASP pure to technical, non-evil
>>>> presentations is important. For many firms that employee researchers and
>>>> allow them to present on the company time and include such things as travel
>>>> and lodging to do so they also have policies.  One of those policies is
>>>> many times to utilize a standard company slide template while employed with
>>>> said firm.
>>>>
>>>> In a attempt to appease the corporate overlords; I want to make a
>>>> simple suggestion that we modify the template to include the following
>>>> language and attached logo.   For the new folks...here is a little OWASP
>>>> History for you in 2008 this agreement was actually put online  by Kate
>>>> Hartmann and Jeff williams and Myself as we prepared for the AppSecUSA 2008
>>>> particularly from the audio video perspective as we were going to video
>>>> tape it (1st in OWASP History at the time) and had other liability issues
>>>> around 0-Day disclosure in NYC see edit history:
>>>> https://www.owasp.org/index.php?title=Speaker_Agreement&action=historyand at that event there was only (1) slide deck that was non-compliant by
>>>> my then employer and friend Jeremiah Grossman as there was not a mac
>>>> template available <grin>
>>>>
>>>> ---------------
>>>> For your consideration as Conferences and Chapter committees;
>>>> ---------------
>>>>
>>>> RECOMMENDED CHANGE #1
>>>>
>>>> "CONTENT
>>>> Speakers are encouraged to include their contact information when
>>>> introducing themselves, but may NOT include their logo"
>>>>
>>>> "CONTENT"
>>>> Speakers are encouraged to include their contact information when
>>>> introducing themselves and may include a company logo and a indicator if
>>>> there company is a supporting organization of OWASP Foundation and any
>>>> projects that they are part of"
>>>>
>>>>
>>>>
>>>>
>>>> RECOMMENDED CHANGE #2
>>>>
>>>> If my session includes a presentation, I will use the Conference
>>>> Template (OWASP Powerpoint template - OWASP Keynote Template (Mac) - OWASP
>>>> Impress Template (Open-/LibreOffice)) or if required to utilize a company
>>>> slide template will also include a OWASP logo on each slide (
>>>> https://www.owasp.org/index.php/Marketing#Logos)
>>>>
>>>>
>>>> =======
>>>>
>>>>
>>>> In my opinion now that we have committees that are proxy
>>>> representatives of the owasp membership globally, this this agreement
>>>> should be reviewed by effected committees (conferences and chapters) with
>>>> input from everyone including connections, projects, membership, eduction
>>>> and modified to meet the growth and spirit of the community to attract the
>>>> best and brightest speakers in the world and have minimal restrictions.
>>>>
>>>> To continue this review I have put a copy of this full document in the
>>>> current state in draft/edit more in OWASP googledocs for everyone to
>>>> review, edit and comment on.
>>>>
>>>>
>>>> https://docs.google.com/a/owasp.org/document/d/1OMAcnSEAElI_ENYP73gSZ4VjxG3JguMYZtt09Pi5vV8/edit
>>>>
>>>> We are a week away from APPSECDC and APPSECAPAC and then events
>>>> happening all over 2012 worldwide so although I realize nothing is FAST in
>>>> a democratic rough consensus voting it should not be overly complex to
>>>> start small and then adjust.
>>>>
>>>> Reference Materials
>>>>
>>>> Other speakers agreements to consider in your review of this motion
>>>>
>>>> 1) IEEE -
>>>> http://www.ieee.org/publications_standards/publications/rights/index.html
>>>>
>>>> 2) BlackHat -
>>>> https://www.blackhat.com/html/bh-dc-11/registration/bh-dc-11-cfp_terms.html
>>>>
>>>> 3) Defcon - https://www.defcon.org/html/defcon-19/dc-19-cfp-form.html
>>>>
>>>>
>>>> Fun Fun... but important to not just have a policy as you would agree.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Committees-chairs mailing list
>>>> Committees-chairs at lists.owasp.org
>>>> https://lists.owasp.org/mailman/listinfo/committees-chairs
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
>> Global_chapter_committee mailing list
>> Global_chapter_committee at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/global_chapter_committee
>>
>>
> _______________________________________________ Global_chapter_committee
> mailing list Global_chapter_committee at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/global_chapter_committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/global_chapter_committee/attachments/20120328/ea7ff216/attachment-0001.html>


More information about the Global_chapter_committee mailing list