[Owasp-board] Update to Bylaws

Fabio Cerullo fcerullo at owasp.org
Wed Mar 26 20:11:39 UTC 2014

Fair enough...a dispute resolution process should be part of the chapter
leader handbook.

In that case, I support the changes suggested to the bylaws.

I just want to avoid the situation in which any dispute among members ends
up in the Global Board mailing list.

Thanks for your comments.


On Wednesday, March 26, 2014, Sarah Baso
<sarah.baso at owasp.org<javascript:_e(%7B%7D,'cvml','sarah.baso at owasp.org');>>

> +1
> On Mar 26, 2014, at 12:53 PM, GK Southwick <genevieve.southwick at owasp.org>
> wrote:
> After following this further down the rabbit hole, I'm in agreement with
> Josh. The bylaws shouldn't state anything about the Community Manager's
> involvement, but the Chapter Leader's Handbook should certainly have a
> section on Conflict Resolution that involves the Community Manager. As I
> mentioned in my introductory email yesterday afternoon:
>    - Chapter/member disputes. One of my many hats here at OWASP is
>    mediation. If an issue arises in your Chapter, that you feel needs to be
>    brought to the attention of the Foundation, please bring it to me first. I
>    should, by default, be informed of any issues that require the attention of
>    anyone outside of your immediate chapter, so that I may assist with
>    intervention and determine if it needs to be escalated further up the chain
>    of command. If I am unable to mediate to the satisfaction of all parties
>    involved, I will gladly assist in bringing the matter to the Board of
>    Directors and step out of the process, so that they can make the case
>    determination.
> This does not mean that the Community Manager should be mentioned in the
> bylaws. As Josh mentioned, if it's gotten so far that the Board needs to be
> involved, the matter should already have been brought to my attention by
> the Chapter Leader prior to that. Now that I understand the distinction
> that Josh is making there, I'm in complete agreement.
> I will handle mediation of Chapter issues, prior to them being brought to
> the attention of the BoD - in fact, I'll bring them to the BoD myself, if
> an amicable resolution can't be reached, but my involvement should be
> addressed in the Chapter Handbook Rules & Regs. Not the Foundation Bylaws.
> -= GK
> Community Manager
> OWASP Foundation
> gksouthwick at owasp.org
> +01.415.742.2342
> On Wed, Mar 26, 2014 at 1:42 PM, Josh Sokol <josh.sokol at owasp.org> wrote:
> Fabio,
> I'm not sure we have the same vision as to what the OWASP Community
> Manager role is.  If they are engaged with the community, as they should
> be, then they should already be aware of any issues.  If an issue escalates
> to the point where a leader is revoking someone from participating, then we
> have clearly moved beyond the issue resolution phase and into the action
> justification phase.  The Chapter Leader Handbook would be an ideal place
> to talk about your process for issue resolution, including escalation to
> the Community Manager, but I disagree that the Community Manager should be
> fielding appeals for revocation as they would have already been biased by
> the issue resolution that took place beforehand.  It's like saying "I
> couldn't help fix the problem so I'm just going to decide to kick you out
> and I don't really feel like I was wrong therefore I won't raise the issue
> with the Board."  Does that make sense?
> This Bylaw change was only meant to grant leaders the ability to revoke
> and provide a path for appeal.  I don't think that we need to put a whole
> dispute resolution process into the Bylaw item.
> ~josh
> On Wed, Mar 26, 2014 at 11:54 AM, Fabio Cerullo <fcerullo at owasp.org>wrote:
> Josh,
> I don't want to be a pain and really appreciate your efforts in drafting
> this doc.
> My only intent is to clarify the Global Board role and establish a clear
> escalation path through the Community Manager.
> Here goes an updated wording.. please feel free to modify it at will:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20140326/3ebf0c46/attachment.html>

More information about the Owasp-board mailing list