[Owasp-leaders] rough consensus & running code

Bev Corwin bev.corwin at owasp.org
Mon May 8 14:01:39 UTC 2017

Thank you Andrew, we know that you tried, and appreciate that. It was a
good exercise, regardless, even for the new ideas. We must do better in the
future. Receiving budget requests is a sign that there are good people out
there willing to help OWASP build value. We all know that this "myth" that
the "centralized" global OWASP would like to support local chapter efforts
- and that is part of the reasoning in limiting local chapters - but it
doesn't really work. Need to build better workflows for incorporating local
activities, including sponsors, projects, co-marketing activities,
community building activities, memberships, and other value creating
activities. OWASP global should be more focused on creating more member and
community value overall, creating more revenue generating activities than
just events and trainings, breaking down silos created by vendors,
empowering chapter leaders and local chapters to build local community,
memberships, and spend less time creating value and profits for vendors.
OWASP is not a large corporation or a gov't agency. It does not need
costly, burdensome red tape. It is a small non profit organization and
needs to create value for members and the community, and to streamline
administrative costs. For every dollar spent on admin, we should be asking:
"Can this be done by a volunteer?" and "Does this create value for our
members and community?". Every staff person should be engaging chapter
leaders and volunteers to help them reduce their burden, not to increase it
with non value creating activities. There need to be clear deliverables for
staff with timelines with deadlines, performance metrics, and empowering
chapter leaders and volunteers to build strong, vibrant chapters by
engaging with their local communities with local sponsors, co-marketing
agreements and building strong membership bases. Perpetuating this strategy
of "strangling" local chapters and empowering "staff" vendors must be
reversed. Not to mention the externalizing of OWASP IP and relationships,
it damages the organization long term if perpetuated. More workflows that
empower local chapter leaders and volunteers need to be implemented, and as
a backup resilience strategies, every staff member and board member should
have at least one or two "volunteers" who can do their job in the interim
while the organization seeks their replacements, or if future budgets
cannot sustain the current death spiral. Sincerely, Bev

On Mon, May 8, 2017 at 2:06 AM, Sean Auriti <sean.auriti at owasp.org> wrote:

> Thank you Andrew.  I hope the budget requests I submitted on January 31st
> can be voted on during tomorrow's board meeting.
> On Mon, May 8, 2017 at 12:16 AM, Andrew van der Stock <vanderaj at owasp.org>
> wrote:
>> The main thing to note here is that I think next year's budget
>> discussions needs to kick off with fervour much earlier than we did last
>> year. I tried (I really did) by talking about the 2017 budget in July,
>> September, October's f2f, November, December and January's board meetings.
>> But it just never really got much traction.
>> I think the problem with asking the community for input is that I
>> received around a $1m of ad hoc ideas, but had no formal way of tracking
>> them, so they sort of got lost. I will look into making a google form or
>> similar this time around so we can track them better. We must manage to
>> policy, and not to individual requests, so I will be looking at a way to
>> bring this together for future years so there is transparency. However, the
>> requests from the NY/NJ chapter alone exceeded this year's total spend by
>> $380k. So we can do some of it, but without growing our membership and
>> sponsorship opportunities, we can't do it all.
>> thanks,
>> Andrew
>> _______________________________________________
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-leaders
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20170508/d1c0890d/attachment.html>

More information about the OWASP-Leaders mailing list