<meta content="text/html; charset=ISO-8859-1"
<body bgcolor="#FFFFFF" text="#000000">
Well said Martin. I say we first identify what the necessary core
deliverables are, then seek bids, then see what we need to spend.
Much better process.<br>
I plan on talking to Kate about this as soon as we can both find
time to speak, then I'll bring everyone into the conversation to
figure out what the necessary items are.<br>
I am 100% ok with letting Kate or Sarah lead this process. I would
just like to have a say. :) That is all.<br>
Aloha + More soon,<br>
I totally agree this is necessary. Instead of allocating 30k, would it not
be better to get quotes first?
We all know how this works. If you tell what the budget is, it will be
On Sat, Apr 7, 2012 at 10:34 PM, Mark Bristow <a class="moz-txt-link-rfc2396E" href="mailto:email@example.com"><firstname.lastname@example.org></a>wrote:
<pre wrap="">OWASP board,
As much of the meeting Thursday related to various challenges in
Owasp's marketing and now that we've canceled the summit, I'd like to
propose that OWASP set aside 30k or so of that budget from this year
to hire a 3rd party marketing firm with the following objectives:
- Revisit the main OWASP logo/brand and update it
- Develop OWASP brand derived logos for our top 10 projects
- Develop slick sheets for our top 10 projects
- Develop an OWASP slick sheet for handing out to potential members at
OWASP booth events and such
- Produce a professional OWASP corporate member pack
- Produce professional sponsorship packs for conference sponsorships
- Produce a slick sheet for each of the upcoming global AppSecs for
handing out at booth events
- Develop a marketing strategy with a target of doubling our corporate
- Develop a strategy for marketing our events (and increase
I also think hiring a 3rd party to execute on the OWASP "brochureware"
and associated wiki template design would add some vibrancy to our web
presence, however this effort may alone be 10k to have it done right.
In my opinion, given the amount of traffic the wiki gets, this should
also be a funding priority.
I think in addition to pumping funds into projects (which I fully
support and is much needed) I think we should use this opportunity to
develop some centralized assets that we can provide to help get the
word out and execute on evangelizing application security issues.
Just some observations/recommendations.
Sent from my wireless device
Owasp-board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Owaspemail@example.com">Owaspfirstname.lastname@example.org</a>
<a class="moz-txt-link-freetext" href="https://lists.owasp.org/mailman/listinfo/owasp-board">https://lists.owasp.org/mailman/listinfo/owasp-board</a>
Committees-chairs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Committeesemail@example.com">Committeesfirstname.lastname@example.org</a>
<a class="moz-txt-link-freetext" href="https://lists.owasp.org/mailman/listinfo/committees-chairs">https://lists.owasp.org/mailman/listinfo/committees-chairs</a>
<div class="moz-signature">-- <br>
Connections Committee Chair<br>
Cheatsheet Series Product Manager<br>
OWASP Podcast Producer/Host<br>
<a class="moz-txt-link-abbreviated" href="mailto:email@example.com">firstname.lastname@example.org</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.owasp.org">www.owasp.org</a></div>