[Owasp-leaders] Local Event Attendees - Code of Conduct
adrian.hayes at owasp.org
Wed May 29 02:20:01 UTC 2013
Michael and Matt,
I think the conference policies will do fine. Cheers for the help!
OWASP New Zealand Chapter Leader (Wellington)
On 29/05/13 13:24, Matt Tesauro wrote:
> I created a Code of Conduct back in November of 2010 when I was on the
> Here's the Google Doc:
> Assuming you see what I do on Google docs, it should also include
> edits made by the board members at that time.
> It was intended to outline the expected behavior of the community
> which was "inspired" by some actions on the leaders list. I raised
> the point that we cannot hold community members up to a standard that
> doesn't exist. This was my attempt to document that standard.
> This was also when the global committees were first taking off and the
> final disposition and publishing was handed over to the membership
> committee. From my recollection, my version was not well received and
> I'm not sure what, if any, final version got published by the
> membership committee. Its been ~2.5 years since that happened so
> don't rely on my recollection as historical fact.
> If this is something that would help in your case, I'm happy to work
> with you on this using my initial draft as a starting point.
> -- Matt Tesauro
> OWASP WTE Project Lead
> http://AppSecLive.org - Community and Download site
> OWASP OpenStack Security Project Lead
> On Tue, May 28, 2013 at 1:41 PM, Michael Coates
> <michael.coates at owasp.org <mailto:michael.coates at owasp.org>> wrote:
> We have an anti harassment policy* that is included in conference
> This would be an ideal document to link from within our chapter
> handbook too.
> * Approved Dec 2012 -
> Michael Coates | OWASP | @_mwc
> On Mon, May 27, 2013 at 7:15 PM, Jim Manico <jim.manico at owasp.org
> <mailto:jim.manico at owasp.org>> wrote:
> (speaking for myself only)
> I really think this covers most code of conduct issues:
> and https://www.owasp.org/index.php/OWASP_Codes_of_Conduct
> The conflict I see is that OWASP is radically an OPEN
> organization, and it's really difficult to ban people from
> meetings without causing a stir. I think we want to err on the
> side of being tolerant.
> Are there specific issues you are facing at your chapter that
> need to be addressed? I'm happy to take this offline with you
> and help where I can or point you in the direction of the
> appropriate full time staff member. It's not really possible
> to codify basic respect, and since we are largely a
> organization of professional hackers, behavior in this
> specific sub-group tends to be a bit, ahem, out of the norm. :)
> Anyhow, let me know how I can help.
> > Thanks Jim, but let me explain a little further.
> > I'm after something that says, for example, "if you come to
> an OWASP
> > event, even if you're just a member of the public with no
> real OWASP
> > affiliation, you are expected to act professionally, etc or
> bad things
> > will happen". I haven't found a part of the handbook that
> outlines that
> > for the general public, or am I just missing it?
> > I am aware of the codes of conduct for various OWASP affiliates
> > (https://www.owasp.org/index.php/OWASP_Codes_of_Conduct),
> however that
> > does not seem to cover those without any real affiliation
> with OWASP.
> > The other options is to not fix it until it's broken (which
> was my
> > initial feeling), however the real goal here is to make sure
> > who attends our events feels comfortable doing so. For the
> person who
> > made the request, having a public document we can all look
> at would go a
> > long way to achieving that, even if the only real result is
> she feels
> > like we're listening and we actually care.
> > Adrian Hayes
> > OWASP New Zealand Chapter Leader (Wellington)
> > On 28/05/13 13:07, Jim Manico wrote:
> >> The OWASP Chapter Leaders Handbook addresses most code of
> conduct issues.
> >> https://www.owasp.org/index.php/Chapter_Leader_Handbook
> >> Aloha,
> >> Jim
> >>> Hi Leaders,
> >>> One of our attendees has raised a concern that there
> doesn't appear to
> >>> be any obvious code of conduct for regular attendees at
> our chapter
> >>> meetings and local OWASP day.
> >>> Is there something already in place we can point to? How
> are other
> >>> chapters handling this?
> >>> She would like us to come up with one (for example
> >>> http://confcodeofconduct.com/) just in case one day
> someone steps out of
> >>> line and we need to take action. This isn't in relation to
> anything that
> >>> has happened at an OWASP NZ event, however she has had
> some issues with
> >>> one individual at other security related events.
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
> <mailto:OWASP-Leaders at lists.owasp.org>
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org <mailto:OWASP-Leaders at lists.owasp.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Leaders