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  July 2019

CODE4LIB July 2019

Subject:

Re: From the Community Support Squad wrt "Note [admiistratativia]"

From:

EDWIN VINCENT SPERR <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 3 Jul 2019 18:46:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

This seems like an excellent time to re-up a call for semi-formalizing Code4Lib as an organization.

I know that folks really aren't thrilled with things like committees and quorums, but ultimately, groups that take collective decisions need a *mechanism* for doing so.



Edwin V. Sperr, MLIS
AU/UGA Medical Partnership
Office of Graduate Medical Education
Clinical Information Librarian

St. Mary’s Hospital
1230 Baxter Street
Athens, GA 30606

p: 706-389-3864
e: [log in to unmask]<mailto:[log in to unmask]> | [log in to unmask]<mailto:[log in to unmask]>
w: medicalpartnership.usg.edu<http://www.medicalpartnership.usg.edu/>


________________________________
From: Code for Libraries <[log in to unmask]> on behalf of Kate Deibel <[log in to unmask]>
Sent: Wednesday, July 3, 2019 2:02 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] From the Community Support Squad wrt "Note [admiistratativia]"

Yes, you, Francis, and Mark publicly committed to working to expand the role of the CSS/CSVs at C4L19 via Mark's lightning talk. You three did drop the ball in announcing the conference volunteers would be continuing their roles. They were vetted and approved for the conference only. People may have objections to them serving community conduct roles in other venues. Furthermore, you have restricted participation to a narrow group. Not everyone could be a CSV at a conference. Maybe they weren't able to attend? Maybe they had additional duties to perform?

All that is a separate issue from the "request" (really a directive since it comes from a place of authority) being told to stop posting. Yes, it does effectively hinder future harm from that conversation, but it also constrains any productive conversation as well. This is where the opaqueness debate comes in. There was no awareness of the CSS, its membership, and its authority (which the current CoC implies they have no enforcement). Furthermore, halting a conversation until the CSS group issues a PR is opaque because we have no timeframe or window into that process.

Finally, I ask you all to consider the effects of basing CoC conversations around git terminology. Not everyone uses git or has a GitHub account. Not everyone gets git terminology. It took me more than a few minutes to remember what else PR could mean besides "public relations." How will the CSS support people ensure that git is not a barrier to community participation.

Katherine Deibel | PhD
Inclusion & Accessibility Librarian
Syracuse University Libraries
T 315.443.7178
[log in to unmask]
222 Waverly Ave., Syracuse, NY 13244
Syracuse University


-----Original Message-----
From: Code for Libraries <[log in to unmask]> On Behalf Of Anne Slaughter
Sent: Wednesday, July 3, 2019 1:36 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] From the Community Support Squad wrt "Note [admiistratativia]"

Seconding Francis' points, and adding that this "failure" does not rest on his shoulders. Mark, Francis, and I publicly committed in San Jose to working to expand the role of the CSS/CSVs to better support the community in situations like this. This work unfortunately hasn't been on any of our front burners yet for all the reasons you might suspect in a volunteer leadership role. But we have a systemic issue with the community's code of conduct. It is written to specifically restrict enforcement to the annual conference, which by definition doesn't give any clear or transparent guidance in dealing with issues outside of the conference proceedings. The work to address that starts now with the process Bobbi introduces in her message, and I assure you that we are committed to doing it openly. It's absolutely not ideal that it's happening in a reactive rather than proactive state, and for that I apologize as well.

Anne Slaughter
Director of Technology Services
Reaching Across Illinois Library System
Burr Ridge Office
Phone: 630.734.5127
Fax: 630.734.5050
[log in to unmask]
https://www.railslibraries.info



On Wed, Jul 3, 2019 at 11:50 AM -0500, "Francis Kayiwa" <[log in to unmask]<mailto:[log in to unmask]>> wrote:


Heya Kate my responses interleaved. For starters if there's any opacity I will take this as my fault/oversight. You, Anne, Mark and I spoke in San Jose about the transition to the CSSCSV group after the conference and promised to work on this once we were done. Unfortunately I've been dealing with lots of personal grief and this took less priority....

On 7/3/19 12:37 PM, Kate Deibel wrote:
> Honestly, this is worrisome to me.
>
> First, who are the members of the Community Support Squad? I can find no mention of it anywhere on the website or the wiki. And it's disturbing that such a group let such a coincidence in lack of coverage occur. Yes, there were people listed for the 2019 conference, but to our knowledge, that was to be only for the conference.

It is the same group that was volunteered at the conference.

https://2019.code4lib.org/conduct/#officers

We didn't expect every one to want to continue but all the volunteers offered to hang on during the transition process which once again I failed to deliver on.

>
> Two, shutting down any conversation while an unknown cabal (redundant, I know) discusses a solution that is to come with no projected timeline not only shuts down hurt but also prevents people from speaking up against any hurt that has or is still happening. Imagine if you had done this exact intervention yesterday after the emails about how the C4L mailing list was only to about CODE. You would have prevented the many posters who stood up to counter that narrative. Any teaching moments or learning that have come afterwards would also have been squashed. All that would remain would be the unchallenged statements of what the C4L community is only about: code. That silence would speak way more hurt. Sure, the Community Support Squad will eventually raise a solution... I mean a "pull request"...

Bobbi pointed out (and I told you about a week ago via our DM twitter that we were mostly out). Now it is fair to imagine if I'd actually followed through on establishing a CSSCSV group as I promised you that this perhaps could have been handled very differently. Again. Blame me for this and that would be fair.

>
> It's uncomfortably ironic in that this conversation started with concerns about the transparency of the authorship and the procedures behind the sexual harassment articles but is now being "handled" by an opaque process where we are told to wait until the mystery box goes ping.
>

I disagree here. The process isn't opaque. The processes will be discussed and we welcome PR's via the aforementioned pull request.
Furthermore if that doesn't work, you and others are welcome to send messages to [log in to unmask]

I want to stress, I've gone rogue here and I am speaking without consulting with the rest of the CSSCSV team.

Cheers,
./fxk

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

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