LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  November 2012

CODE4LIB November 2012

Subject:

Re: anti-harassment policy for code4lib?

From:

Jon Stroop <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 26 Nov 2012 19:15:45 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (217 lines)

It's sad that we have to address this formally (as formal as c4l gets 
anyway), but that's reality, so yes, bess++ indeed, and mjgiarlo++, 
anarchivist++ for the quick assist.

The responses to the list in the past couple of hours alone suggest that 
this is something much of the community would want to get behind. To 
that end, and as a show of (positive) force--not to mention how cool our 
community is--I think it might be neat if we could find a way to make 
whatever winds up being drafted something we can sign; i.e. attach our 
personal names. I don't know how that would work exactly...maybe via the 
wiki (where it seems to me a lot of good info goes to die) or the 
code4lib Github (slightly better since you could link to your 
credentials in a an environment much larger than our own, and everyone 
could have a copy), but something along those lines. I'm happy to help 
if I can.

Anyway, just a thought.
-Jon

-- 
Jon Stroop
Digital Initiatives Programmer/Analyst
Princeton University Library

[log in to unmask]

http://pudl.princeton.edu
http://findingaids.princeton.edu


On 11/26/12 6:33 PM, Michael J. Giarlo wrote:
> All,
>
> Building on what Bess and others have written, and on the GitHub repo that
> anarchivist set up, I've contributed a rough draft of a Code4Lib code of
> conduct:
>
> https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md
>
> This strawperson code of conduct is based on DLF Forum's, which is based on
> the Ada Initiative's sample policy. It is modified slightly to reflect a
> broader scope of the conference, conference social events, the IRC channel,
> and the mailing list.
>
> Throw darts, rinse, repeat.
>
> -Mike
>
>
> On Mon, Nov 26, 2012 at 6:10 PM, Robert Sanderson <[log in to unmask]>wrote:
>
>> +1, of course :)
>>
>> You might wish to consider some further derivatives/related pages:
>>      http://www.diglib.org/about/code-of-conduct/
>>      http://wikimediafoundation.org/wiki/Friendly_space_policy
>>      https://thestrangeloop.com/about/policies
>>      http://www.apache.org/foundation/policies/anti-harassment.html
>>
>> Rob
>>
>>
>>
>> On Mon, Nov 26, 2012 at 3:57 PM, Mariner, Matthew <
>> [log in to unmask]> wrote:
>>
>>> +1 for all of the below
>>>
>>> Matthew C. Mariner
>>> Head of Special Collections and Digital Initiatives
>>> Assistant Professor
>>> Auraria Library
>>> 1100 Lawrence StreetDenver, CO 80204-2041
>>> [log in to unmask]
>>> http://library.auraria.edu :: http://archives.auraria.edu
>>>
>>>
>>>
>>>
>>>
>>> On 11/26/12 3:51 PM, "Tom Cramer" <[log in to unmask]> wrote:
>>>
>>>> +1 for Bess's motion
>>>> +1 for Roy's expansion to C4L online interactions as well as face to
>> face
>>>> +1 for Karen's focus on general inclusivity and fair play
>>>>
>>>>> For me the hardest thing is how one monitors and resolves issues that
>>>>> arise. As a group with no formal management, I suppose the conference
>>>>> organizers become the "deciders" if such a necessity arises. If it's
>>>>> elsewhere (email, IRC) -- that's a bit trickier. The Ada project's
>>>>> detailed guides should help, but if there is a policy it seems that
>>>>> there necessarily has to be some responsible "body" -- even if ad hoc.
>>>>
>>>> It seems to me that there would be tremendous benefit in having
>>>>
>>>> 1.) an explicit statement of the community norms around harassment and
>>>> fair play in general. In the best case, this would help avoid
>>>> uncomfortable or inappropriate situations before they occur.
>>>>
>>>> 2.) a defined process for handling any incidents that do arise, which in
>>>> the case of this community I would imagine would revolve around
>>>> reporting, communication, negotiation and arbitration rather than
>>>> adjudication by a standing body (which I agree is hard to see in this
>>>> crowd). I know several high schools have adopted peer arbitration
>>>> networks for conflict resolution rather than referring incidents to the
>>>> Principal's Office--perhaps therein lies a model for us for any
>> incidents
>>>> that may not be resolved simply through dialogue.
>>>>
>>>> - Tom
>>>>
>>>>
>>>>
>>>> On Nov 26, 2012, at 2:32 PM, Karen Coyle wrote:
>>>>
>>>>> Bess and Code4libbers,
>>>>>
>>>>> I've only been to one c4l conference and it was a very positive
>>>>> experience for me, but I also feel that this is too valuable of a
>>>>> community for us to risk it getting itself into crisis mode over some
>>>>> unintended consequences or a "bad apple" incident. For that reason I
>>>>> would support the adoption of an anti-harassment policy in part for its
>>>>> consciousness-raising value. Ideally this would be not only about
>> sexual
>>>>> harassment but would include general goals for inclusiveness and fair
>>>>> play within the community. And it would also serve as an acknowledgment
>>>>> that none of us is perfect, but we can deal with it.
>>>>>
>>>>> For me the hardest thing is how one monitors and resolves issues that
>>>>> arise. As a group with no formal management, I suppose the conference
>>>>> organizers become the "deciders" if such a necessity arises. If it's
>>>>> elsewhere (email, IRC) -- that's a bit trickier. The Ada project's
>>>>> detailed guides should help, but if there is a policy it seems that
>>>>> there necessarily has to be some responsible "body" -- even if ad hoc.
>>>>>
>>>>> kc
>>>>>
>>>>>
>>>>> On 11/26/12 2:16 PM, Bess Sadler wrote:
>>>>>> Dear Fellow Code4libbers,
>>>>>>
>>>>>> I hope I am not about to get flamed. Please take as context that I
>>>>>> have been a member of this community for almost a decade. I have
>>>>>> contributed software, support, and volunteer labor to this community's
>>>>>> events. I have also attended the majority of code4lib conferences,
>>>>>> which have been amazing and life-changing, and have helped me do my
>> job
>>>>>> a lot better. But, and I've never really known how to talk about this,
>>>>>> those conferences have also been problematic for me a couple of times.
>>>>>> Nothing like what happened to Noirin Shirley at ApacheCon (see
>>>>>> http://geekfeminism.wikia.com/wiki/Noirin_Shirley_ApacheCon_incidentif
>>>>>> you're unfamiliar with the incident I mean) but enough to concern me
>>>>>> that even in a wonderful community where we mostly share the same
>>>>>> values, not everyone has the same definitions of acceptable behavior.
>>>>>>
>>>>>> I am watching the toxic fallout from the BritRuby conference
>>>>>> cancellation with a heavy heart (go search for "britruby conference
>>>>>> cancelled" if you want to catch up and/or get depressed). It has me
>>>>>> wondering what more we could be doing to promote diversity and
>>>>>> inclusiveness within code4lib. We have already had a couple of
>>>>>> harassment incidents over the years, which I won't rehash here, which
>>>>>> have driven away members of our community. We have also had other
>>>>>> incidents that don't get talked about because sometimes one can feel
>>>>>> that membership in a community is more important than one's personal
>>>>>> boundaries or even safety. We should not be a community where people
>>>>>> have to make that choice.
>>>>>>
>>>>>> I would like for us to consider adopting an anti-harassment policy
>> for
>>>>>> code4lib conferences. This is emerging as a best practice in the
>> larger
>>>>>> open source software community, and we would be joining the ranks of
>>>>>> many other conferences:
>>>>>>
>> http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Adoption.
>>>>>> The Ada Initiative has a great discussion of why adopting an
>>>>>> Anti-Harrassment policy is a good choice for a conference to make, as
>>>>>> well as some example policy statements, here:
>>>>>> http://adainitiative.org/what-we-do/conference-policies/ Here is a
>>>>>> summary:
>>>>>>
>>>>>>> Why have an official anti-harassment policy for your conference?
>>>>>>> First, it is necessary (unfortunately). Harassment at conferences is
>>>>>>> incredibly common - for example, see this timeline
>>>>>>> (http://geekfeminism.wikia.com/index.php?title=Timeline_of_incidents
>> )
>>>>>>> of sexist incidents in geek communities. Second, it sets expectations
>>>>>>> for behavior at the conference. Simply having an anti-harassment
>>>>>>> policy can prevent harassment all by itself. Third, it encourages
>>>>>>> people to attend who have had bad experiences at other conferences.
>>>>>>> Finally, it gives conference staff instructions on how to handle
>>>>>>> harassment quickly, with the minimum amount of disruption or bad
>> press
>>>>>>> for your conference.
>>>>>> If the conference already has something like this in place, and I'm
>>>>>> just uninformed, please educate me and let's do a better job
>>>>>> publicizing it.
>>>>>>
>>>>>> Thanks for considering this suggestion. If the answer is the usual
>>>>>> code4lib answer (some variation on "Great idea! How are you going to
>>>>>> make that happen?") then I hereby nominate myself as a member of the
>>>>>> Anti-Harrassment Policy Adoption committee for the code4lib
>> conference.
>>>>>> Would anyone else like to join me?
>>>>>>
>>>>>> Bess Sadler
>>>>>> [log in to unmask]
>>>>>> Manager, Application Development
>>>>>> Digital Library Systems & Services
>>>>>> Stanford University Library
>>>>> --
>>>>> Karen Coyle
>>>>> [log in to unmask] http://kcoyle.net
>>>>> ph: 1-510-540-7596
>>>>> m: 1-510-435-8234
>>>>> skype: kcoylenet

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager