search

code4lib / code-of-conduct

Code4lib code of conduct
https://code4lib.org/
Creative Commons Zero v1.0 Universal
84 stars 75 forks source link

resurrecting PR #20 #50

Closed thatandromeda closed 6 years ago

thatandromeda commented 9 years ago

20 has been languishing for years and should be resolved prior to conference. It appears to contain:

This PR applies the first of these, and does not apply the second two. If @dltj , @kcoyle, or anyone else would like to remove reference to specific sanctions, please open a separate PR that is limited in scope to that one change and make your case in comments - we are clearly going to need more discussion to reach consensus.

anarchivist commented 9 years ago

I would like to clarify the "IRC channel administrators" issue, but I'm otherwise :+1: on this.

This repository has been active recently; is it worth making the main list (or the conference list) aware of these changes?

kcoyle commented 9 years ago

I don't recall what I was thinking before. Today the list of sanctions looks more to me like guidance for organizers, and kind of has their back if they make one of those decisions. The other wording fixes look ok to me. The one that might be controversial is the change from "threatens" to "demeans" -- I think this speaks to the difference between harassment and discrimination, and I don't know how we want to deal with this. I'd be fine with a combined 'antiharassment/anti-discrimination' code. I think that antiharassment speaks more to sexual content, while anti-discrimination covers race, religion, etc. Presumably we wish to address the latter as well.

yo-bj commented 9 years ago

Do you think a change to include both words would help? Possibility: "threatens and/or demeans" to replace "threatens"?

kcoyle commented 9 years ago

I'd happy go with "threatens or demeans" - just skipping the and/or

anarchivist commented 9 years ago

:+1: to @kcoyle's suggestion.

yo-bj commented 9 years ago

+1

dltj commented 9 years ago

+1 to @kcoyle's suggestion.

yo-bj commented 9 years ago

I move to get this merged with amendments to the specific lines pointed out in the discussion.

thatandromeda commented 9 years ago

I have amended the PR to address feedback and emailed c4l to invite them to have a look.

There are some event-specific contacts that the c4l15 organizers need to fill in, and I don't see an obvious link on the conference web site; can someone who is involved with conference organizing herd those cats? Also someone who is not me should merge the PR if there are no further issues.

anarchivist commented 8 years ago

Resurfacing this pull request. I have a branch on my fork that addresses the line-length issue and replaces the reference to the Zoia admins with more explicit instructions on how to use @helpers publicly or via a private message. Compare here.

I did not change political beliefs to political affiliation.

@thatandromeda - feel free to grab that commit if you'd like to add it to this branch, or let me know if it merits further discussion. Like you, I'm hoping we can get this in before the 2016 conference (even though this was opened before the 2015 conference!).

jcoyne commented 8 years ago

:+1:

anarchivist commented 7 years ago

Bump? It's been over two years since this PR was opened.

escowles commented 7 years ago

I am 👍 on merging this, with @anarchivist's changes (https://github.com/code4lib/antiharassment-policy/pull/50#issuecomment-171154849)

anarchivist commented 7 years ago

I reckon we should tag someone on the LPC too, since it'll probably impact the website. @joshuago78 @highermath ping?

gmcharlt commented 7 years ago

+1 for merging @anarchivist's commit bb515f8e7e0025d45

gmcharlt commented 7 years ago

Per discussion today during the duty officer's meeting, @anarchivist and I are not planning on merging commit bb515f8 or any other change to the code of conduct right before the conference is to begin. This pull request really ought to be resolved before the next conference, however.

yo-bj commented 6 years ago

Bump - is it time to revisit this PR and decide if we will accept the changes or not?

anarchivist commented 6 years ago

I'm 👍 on the changes.

yo-bj commented 6 years ago

I think it's safe to pull this one in - I'll ping the LPC channel in Slack to give them a heads up on the changes, but any changes should be done by next week (month before the conference).

yo-bj commented 6 years ago

Posted to both the listserv and the LPC channel on Slack last week/early this week, and no comments either way. Since there are no comments, an Owner can merge away.