[Owasp-leaders] rough consensus & running code

Bev Corwin bev.corwin at owasp.org
Thu May 4 16:16:54 UTC 2017


@Liam - Lets create a committee of members and chapter leaders for all
owasp chapters, and I will give you a long list of the flaws.

On Thu, May 4, 2017 at 11:42 AM, Liam Smit <liam.smit at gmail.com> wrote:

> Hi Bev
>
> If you think there is a flaw then please point it out and offer a fix
> (improvement) for it. If your suggested improvement is deemed good by the
> OWASP community at large then it stands a chance of replacing the flaw.
>
> Please repeat this for the "many flaws".
>
> Many thanks and kind regards,
>
> Liam
>
> On Thu, May 4, 2017 at 5:32 PM, Bev Corwin <bev.corwin at owasp.org> wrote:
>
>> Sounds like the Chapter Leader Handbook needs to be voted on by members.
>> There are many flaws. Also, staff, chapter leaders and board need some
>> training in user experience, member experience, and grassroots
>> communications outreach. These top down methodologies and processes are
>> contrary to OWASP values and core principles. They are being hijacked by
>> staff to bottleneck and constrain chapter leaders, mostly to protect their
>> jobs. Bottlenecking needs to be prohibited. Big problem at OWASP.
>>
>> On Thu, May 4, 2017 at 11:28 AM, Tiffany Long <tiffany.long at owasp.org>
>> wrote:
>>
>>> Hey Tom and Bev!  It seems you are ahead of the curve.  This document
>>> was set to be released to the community with the Ops Update Blog post
>>> accompanied by the following text:
>>>
>>> Chapter Orientation:
>>>> Since September all new chapters were requested to have an Orientation
>>>> meeting via Gotomeeting.  Since then these meetings have been refined into
>>>> a  series of standing one on one appointments for any Chapter Leaders
>>>> starting a new chapter, any new chapter leaders who wish to join, and any
>>>> current leaders who want to take a refresher.
>>>
>>>
>>>
>>>>
>>>> So far reactions have been good.  Many experienced chapter leaders have
>>>> expressed a wish for this when they got started and follow up emails with
>>>> procedural questions have dropped from an average of 5 per new chapter to
>>>> 10 total in the last 8 months.  We have also seen an uptick in new chapters
>>>> using funds and getting multiple leaders on board.  All of these are
>>>> indicators of early chapter health.  Board members, staff, and the
>>>> community can read the draft outline of the orientation.  The document will
>>>> be made public in the form of the Chapter FAQ in the next few weeks.
>>>
>>>
>>>
>>> It has long been noted that new chapter leaders tick the box that says
>>> that they have read the Chapter Leader Handbook, but often do not
>>> understand what help they can get from the foundation or how funding works.
>>> This document is a draft outline of the most commonly asked questions about
>>> being a chapter leader.
>>>
>>>
>>> The orientation is divided into three parts, the first addresses how to
>>> build a chapter, how to reach out to audiences and tactics that other
>>> chapters have used to flourish. The second part covers our vendor
>>> neutrality policy and other rules and privileges for chapter leaders.
>>> Finally we discuss funding in-depth.
>>>
>>>
>>> Some conversations are expected to be had again when chapter leaders are
>>> not overwhelmed with questions. In the outline you will see these topics
>>> marked with statements like "reach out to me." Every point in this
>>> orientation outline is simply a rehash from the Chapter Leader Handbook.
>>>
>>> Tiffany Long
>>> Community Manager
>>>
>>> On Thu, May 4, 2017 at 4:07 PM, Bev Corwin <bev.corwin at owasp.org> wrote:
>>>
>>>> PS: Re: Document: https://docs.google.com/document/d/1uupqip9TiejURb
>>>> znt_Dk6t1H--8foRJxcVQ2gdmUj-s/edit?ts=590a0fcc
>>>>
>>>> On Thu, May 4, 2017 at 11:04 AM, Bev Corwin <bev.corwin at owasp.org>
>>>> wrote:
>>>>
>>>>> Note that you cannot "edit" or "comment" on this document. The tone is
>>>>> very *not* right for "consensus". In fact, it is authoritarian in tone and
>>>>> intent. Sounds like OWASP Staff are revolting against local chapters
>>>>> and making the OWASP Global staff the new "kings" of OWASP Chapters. Do you
>>>>> think that this this appropriate?
>>>>>
>>>>> Bev
>>>>>
>>>>> On Thu, May 4, 2017 at 10:59 AM, Tom Brennan - OWASP <tomb at owasp.org>
>>>>> wrote:
>>>>>
>>>>>> @OWASP we reject kings, presidents and voting. we believe in rough
>>>>>> consensus and running code
>>>>>> <https://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project#Core_Values>,
>>>>>> your attendance is requested to join the next global board meeting on May
>>>>>> 9th
>>>>>>
>>>>>> Details:
>>>>>> https://www.owasp.org/index.php/Board
>>>>>>
>>>>>> Join us share your ideas, concerns and suggestions in person or
>>>>>> virtually
>>>>>> <https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference>
>>>>>>
>>>>>> On behalf of the 2017 Board of Directors thank you for caring and
>>>>>> sharing.
>>>>>> https://www.owasp.org/index.php/About_The_Open_Web_Applicati
>>>>>> on_Security_Project#2017_Elected_by_Membership.2C_Global_Boa
>>>>>> rd_Members
>>>>>>
>>>>>> Tom Brennan
>>>>>>
>>>>>> _______________________________________________
>>>>>> OWASP-Leaders mailing list
>>>>>> OWASP-Leaders at lists.owasp.org
>>>>>> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> OWASP-Leaders mailing list
>>>> OWASP-Leaders at lists.owasp.org
>>>> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> 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/20170504/3ee71697/attachment-0001.html>


More information about the OWASP-Leaders mailing list