[Owasp-board] Request for Comment - New Event Profit Split Policy

Mark Bristow mark.bristow at owasp.org
Tue Jul 17 20:47:13 UTC 2012

I agree with josh on #1.  The profit targets should be set in outyear
budget planning with it locked in at the beginning of each OWASP FY.  The
mechanics of this as proposed are a bit odd.  My only point is that the
targets should be set BEFORE the CFP goes out so applicants have clear
expectations set.

Otherwise I'm personally fine with this as written.  I'm not in favor of
Josh's proposed changes in #2.  As written this provides an avenue for
chapters to raise significant funds from events while ensuring that the
foundation also recovers it's capital investments/costs in a "chapters
first" model.  IMO this is a good balance of the priorities.

On Tue, Jul 17, 2012 at 3:35 PM, Josh Sokol <josh.sokol at owasp.org> wrote:

> 1. The point about when the profit target is determined is unclear.  Does
> this mean for the US event that we are determining the target after the
> event has taken place or is this for the next year's event?  Why are we
> using the US event to determine the timing for other events.  IMHO, we
> should be able to set the profit target for the following year's event
> within 60 days of the completion of the current year's event.
> 2. I am fine with the percentage splits here, but do not agree with the
> $5,000 value at which they happen.  This is more than enough for a smaller
> chapter holding an event, but for a larger chapter, such as my Austin
> chapter, our event would have to profit $18,750 in order for us to raise
> our annual budget of roughly $10,000.  In other words, this $5,000 number
> does not allow us to scale profit splits well as chapter sizes grow.  My
> suggestion would be to make $5,000 the base number here UNLESS a chapter
> running an event has submitted a budget showing annual expenses greater
> than that amount, in which case they are allowed up to that amount at the
> 10/90 split.  A subtle change, but one which I believe is necessary in
> order for this policy to scale appropriately.
> 3. I agree that the Chapters committee should be responsible for
> monitoring chapter accounts, budgets, and expenses as necessary.
> 4. I agree that the Chapters committee will need to establish new
> guidelines similar to those of the Conferences committee for local and
> regional events held by the chapters.
> ~josh
> On Tue, Jul 17, 2012 at 1:54 PM, Sarah Baso <sarah.baso at owasp.org> wrote:
>> Global Conferences and Chapters Committee Members (and other interested
>> community members) -
>> Kate Hartmann and the Board of Directors have drafted a proposed policy
>> for profit sharing and financial oversight of future OWASP events. A copy
>> of this drafted policy is attached (for those of you without google docs)
>> and also available here:
>> https://docs.google.com/a/owasp.org/document/d/159bD2oeAmM2yfPNeq5wHvIvHcl10Hl-c3Um2GXAW81Y/edit
>> The Board intends to finalize this policy at their next meeting
>> (scheduled for August 13, 2012), and have requested that you submit any
>> comments, questions, or concerns for their consideration by that time.
>> Thank you in advance for taking the time to read and review this document!
>> --
>> Sarah Baso
>> Director
>> OWASP Foundation
>> sarah.baso at owasp.org
>> +1.312.869.2779
>> _______________________________________________
>> Owasp-board mailing list
>> Owasp-board at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-board
> _______________________________________________
> Owasp-board mailing list
> Owasp-board at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-board

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: <http://lists.owasp.org/pipermail/owasp-board/attachments/20120717/ed433e19/attachment.html>

More information about the Owasp-board mailing list