[Owasp-board] Meetups

Bev Corwin bev.corwin at owasp.org
Tue Mar 10 11:45:15 UTC 2015

Thanks for the policy info, very helpful. Good to know. Best wishes, Bev

On Tue, Mar 10, 2015 at 7:38 AM, Noreen Whysel <noreen.whysel at owasp.org>

> Hi Bev,
> This is the full policy on geographic area from Chapter 3 of the Chapter
> Leader Handbook:
> https://www.owasp.org/index.php/Chapter_Handbook/Chapter_3:_How_to_Start_a_Chapter
> Geographic area
> An OWASP local chapter organizes OWASP activity in a given geographical
> area. A person or a group (the "founding members") can request to start a
> new chapter in a geographical area not currently served by an OWASP group.
> One key to a successful OWASP chapter is selecting the right geographical
> area. Naturally the geographical area should not overlap with an existing
> chapter. OWASP chapters promote face-to-face meetings and the geographical
> area covered should be no more than a reasonable travel for a meeting. On
> the other hand the area should be large enough to serve enough people who
> are interested in web application security and enough people to be active
> in the chapter.
> Noreen Whysel
> Community Manager
> OWASP Foundation
> On Mar 10, 2015, at 5:22 AM, Bev Corwin <bev.corwin at owasp.org> wrote:
> Hi Noreen,
> If there is policy, please share it. I wasn't able to find one. Thank you
> and best wishes.
> Sincerely,
> Bev
> On Mon, Mar 9, 2015 at 11:41 PM, Noreen Whysel <noreen.whysel at owasp.org>
> wrote:
>> Hi Bev,
>> I am not aware of that specific restriction, although I would assume that
>> members of a chapter would expect meetings to be held within their local
>> areas most of the time. If a meeting were held outside the chapter area,
>> and especially if there is already another chapter in the proposed meeting
>> location, we would expect the courtesy of inviting the other group to
>> participate, or at least informing them of the meeting in case there is a
>> potential conflict or competing event.
>> I am aware that the Brooklyn chapter has tentatively planned a May
>> meeting in Midtown Manhattan. Brooklyn is located in very close quarters
>> with NYC, LI and NJ and these chapters share some of its leadership, so I
>> am assuming that there has been discussion among the chapters involved.
>> Given this point I wonder if it is less about territory and more about
>> developing the Brooklyn chapter within its own community. Has there been
>> difficulty finding meeting space? Are there organizations and institutions
>> in Brooklyn that we should be trying to connect with?
>> There are other chapters with similar satellite type relationships, which
>> you may want to look to for guidance, although my impression is that the
>> NYC relationship is strong. Chapters may in fact choose to connect with or
>> provide support to other chapters that are not nearby. We hope that in
>> the long run these relationships serve to strengthen the OWASP community
>> at large.
>> Noreen Whysel
>> Community Manager
>> OWASP Foundation
>> On Mar 9, 2015, at 11:00 PM, Bev Corwin <bev.corwin at owasp.org> wrote:
>> Dear OWASP Board and Leaders,
>> Are OWASP Chapters geographically limited by their local areas as in
>> 'territories" for where they decide to hold meetups? For example, if the
>> OWASP Brooklyn Chapter decided to hold a meetup in say, Anchorage, for
>> example, would that be a problem? Or, perhaps OWASP Brooklyn meetups wanted
>> to share a meetup with some other group in say, for example, Boston? Is
>> there some kind of organization "territorial" limitation to locations based
>> on the group's locations? If this is a policy, please kindly point me to
>> the link. I have not been able to find it. Thank you and best wishes.
>> Sincerely,
>> Bev
>> _______________________________________________
>> Owasp-board mailing list
>> Owasp-board at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-board
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20150310/2a0f049b/attachment-0001.html>

More information about the Owasp-board mailing list