[Owasp-leaders] Proposal for OWASP Global Chapters Committee

Vlad Styran vlad.styran at owasp.org
Mon Sep 3 10:33:50 UTC 2018

Dear all,

Early this year we have experienced a change in how different the treatment of the Chapter needs could be, and the point of this change was ideed the day Tiffany left her position as Community Manager. I had no idea what amount of work and beurocratic burden has been hidden from us until then.

We had a really awkward situation with a meeting funding after that, and I sincerely appreciate the help of NL Chapter and Martin himself, as well as Karen facilitating the resolution of the issue. However, I believe OWASP could operate in a way that prevents such situations from happening and that this kind of escalations is demorsalizing to the Chapter leaders and must be avoided.

That said, I can see both ways in the argument and as much as I would like to prevent it from heating up, I would be happy for the situation to improve. I believe the initiative of re-booting the Global Chapters Committee is a chance to achieve both objectives. I have a list of suggestions for the committee once it’s up and operating, and I and my co-leaders are ready to put effort into this initiative.

Hope my non-native English doesn’t leave much for interpretation between the lines.

Vlad Styran

OWASP Kyiv Chapter Leader
PGP pub key: 87F07F08 <http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19ED24B087F07F08>
Twitter <https://twitter.com/owaspKyiv> Facebook <https://www.facebook.com/owaspkyiv> YouTube <https://www.youtube.com/channel/UCZlgZTJRb4dXhSUFCjwAQzA> Mailing List <https://lists.owasp.org/mailman/listinfo/owasp-kyiv> Slack <https://owasp.slack.com/messages/chapter-ua/> SlideShare <https://www.slideshare.net/owaspKyiv>

> On Sep 2, 2018, at 00:28, Josh Sokol <josh.sokol at owasp.org> wrote:
> Dear OWASP Leaders,
> As per the OWASP Committees 2.0 Operational Model <https://www.owasp.org/index.php/Governance/OWASP_Committees>, approved by a vote of the OWASP Board of Directors on July 16, 2014, I would like to formally propose the creation of a new "OWASP Global Chapters Committee".
> My rationale for the creation of this new committee is that our community has made a number of observations about inadequacies in the ways our Chapters interact with the OWASP Foundation, it's Staff, and the Board.  This committee would serve as a new form of governance within the OWASP Foundation, cutting red tape and empowering our chapter leaders to better serve the mission of OWASP while still adhering to the OWASP Core Values of openness, innovation, being a global community, and integrity.  We will focus on strengthening the OWASP Chapters through education, networking, and driving value to our members.
> Topics that are within scope for the OWASP Global Chapters Committee include, but are not limited to:
> Leadership Requirements: The committee will be responsible for defining requirements for new chapter leaders and create a community vetting process.
> Activity Requirements: The committee will be responsible for defining the minimum activity requirements for chapters and will periodically review chapters for meeting those minimum requirements.
> Mentorship: Programs will be created to pair new chapter leaders together with more experienced ones.  Budgets will be established in order to facilitate mentees attendance of mentor chapter meetings.
> Projects Partnership Tours: To emphasize the importance of projects, a budget will be established for projects to hold regional tours of chapters where they will speak and show off their projects.
> Budgets: The committee will be a resource for OWASP policies and procedures when it comes to the budget process and ensuring that it is being followed.  The committee will help identify opportunities for chapter leaders to spend their money.
> Policy: The committee will review and revise the Chapter Leader Handbook on a periodic basis.  They will assess gaps in existing policies and help to create new policies or redefine existing policies to address gaps.
> Guidance: The committee will serve to help guide other leaders with any questions that they have.  They will assist with finding speakers.  They will help to recommend topics for presentations.
> Feedback: The committee will survey chapter leadership on pertinent topics and be a listening outlet for chapter needs.
> Conflict Resolution: The committee will serve as a tribunal for conflicts among and between chapters.
> Local and Regional Events: The committee will help to guide chapter leaders on how to start and run local and regional events.  A "startup" budget will be formed from existing event revenues in order to seed investment in more events, helping additional chapters to be able to raise enough money to cover their expenses and innovate.
> Board Guidance: The committee will work with the Board on any initiatives they have as they relate to chapter policies, governance, budgets, or otherwise.
> This scoping was developed by myself and Tiffany Long in an effort to cover many of the issues our chapters face on a routine basis.  It is not a comprehensive list and I'd certainly welcome suggestions from others in our community.  Moreso, it is my hope that others will be interested in participating in and contributing to this committee.
> Per the Committee Creation section of the Committees 2.0 Operational Model, this is now up for a community discussion with a Board vote to follow.  I hereby formally request that this be added as a topic for vote at the September 19th OWASP Board meeting.  Thank you.
> Sincerely,
> Josh Sokol
> OWASP Board Member 2014-2017
> OWASP Austin Chapter Leader
> OWASP LASCON Conference Co-Founder
> _______________________________________________
> 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/20180903/07c33bbd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 873 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.owasp.org/pipermail/owasp-leaders/attachments/20180903/07c33bbd/attachment.pgp>

More information about the OWASP-Leaders mailing list