├── OPPOSERS.txt ├── ABSTENTIONS.txt ├── diversity ├── OPPOSERS.txt ├── ABSTENTIONS.txt ├── SUPPORTERS.txt ├── diversity.md └── README.md ├── css_volunteers.md ├── SUPPORTERS.txt ├── transparency_reports ├── 2025_national_conference_annual_report.md ├── 2021_national_conference_annual_report.md ├── 2024_national_conference_annual_report.md ├── 2023_national_conference_annual_report.md ├── 2019_national_conference_annual_report.md ├── 2020_national_conference_annual_report.md └── 2022_national_conference_annual_report.md ├── norms.md ├── how_changes_are_made.md ├── README.md ├── csvcharge.md ├── LICENSE ├── code_of_conduct.md └── procedures.md /OPPOSERS.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /ABSTENTIONS.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /diversity/OPPOSERS.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /diversity/ABSTENTIONS.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /diversity/SUPPORTERS.txt: -------------------------------------------------------------------------------- 1 | Bohyun Kim (@bohyunkim on github, twitter, Slack) 2 | Esmé Cowles (@escowles on github, twitter, Slack, IRC) 3 | Nick Ruest (@ruebot on github, twitter, Slack, IRC 4 | Michael Della Bitta (@mdellabitta on github, twitter, Slack, IRC) 5 | Brian Rogers (@bhar0 on github, twitter, Slack, IRC) 6 | Stuart Forrest (@stareagle on github) 7 | -------------------------------------------------------------------------------- /css_volunteers.md: -------------------------------------------------------------------------------- 1 | Current Community Support Volunteers 2 | ==================================== 3 | 4 | The following **volunteers** for the [Community Support Squad](csvcharge.md) have agreed to list their email addresses here for dealing with [Code of Conduct4Lib](code_of_conduct.md) issues that arise in Code4Lib channels **other** than the annual Code4Lib conference. 5 | 6 | Please respect that these are **volunteers**: they are not available 24/7; there is no guarantee that any CSS members are monitoring the IRC, listserv, Slack, and/or Discord channels outside of the Code4Lib conference days. 7 | 8 | Therefore, it would be helpful to make sure you've provided context for your concern. 9 | 10 | * Eric Phetteplace (phette23@gmail.com) 11 | * Natasha Allen (ndallen@umich.edu) 12 | * Bobbi Fox (bobbi@bobbifox.net) 13 | * Anne Slaughter (anne.slaughter@railslibraries.info) 14 | -------------------------------------------------------------------------------- /SUPPORTERS.txt: -------------------------------------------------------------------------------- 1 | Daniel Chudnov (@dchud on github, twitter, freenode) 2 | Michael B. Klein (@mbklein on github, twitter, freenode) 3 | Michael J. Giarlo (@mjgiarlo on github, twitter, freenode) 4 | Nick Ruest (@ruebot on github, twitter, freenode) 5 | Mark A. Matienzo (@anarchivist on github, twitter, freenode) 6 | Hillel Arnold (@helrond on github, twitter, freenode) 7 | Shaun Ellis (@sdellis on github, twitter) 8 | Cary Gordon (@highermath on github, twitter, freenode) 9 | Andromeda Yelton (@thatandromeda on github, twitter, freenode) 10 | Jon Stroop (@jpstroop on github, twitter, freenode) 11 | Esmé Cowles (@escowles on github, twitter, freenode) 12 | Eric Phetteplace (@phette23 on github, twitter) 13 | Bohyun Kim (@bohyunkim on github, twitter) 14 | Tom Johnson (@no_reply on twitter) 15 | Erin White (@erinrwhite on twitter, github) 16 | Francis Kayiwa (@kayiwa on twitter, github, freenode) 17 | Jay Luker (@lbjay on twitter, github, freenode) 18 | Ross Singer (@rsinger on twitter, github, freenode) 19 | Ed Summers (@edsu on github, twitter, freenode) 20 | Jason Casden (@cazzerson on github, twitter, freenode) 21 | Cynthia Ng (@TheRealArty on twitter, Arty-chan on github, freenode) 22 | Misty De Meo (@mistydemeo on twitter, github, mistym on freenode) 23 | Chad Nelson (@bibliotechy on github, twiiter, freenode) 24 | Bess Sadler (@eosadler on twitter, bess on github and freenode) 25 | Scott Robarts (@srobarts on twitter, srobarts on github) 26 | Helen Halbert (@hhalbert on github) 27 | Mary Jinglewski (@mjingle on twitter, github, and freenode) 28 | Galen Charlton (@gmcharlt on twitter, github, and freenode) 29 | Carsten Klee (@collidoscope on twitter, @cKlee on github) 30 | Tod Robbins (@todrobbins on twitter, github, and freenode) 31 | Megan Kudzia (@mkudzia on twitter, github, and freenode) 32 | Brian Rogers (@bhar0 on github, twitter, Slack, IRC) 33 | Christian Sarason (@cpsarason on github, twitter) 34 | Julie C. Swierczek (@JulieSwierczek on twitter, @js0430 on github) 35 | Stuart Forrest (@stareagle on github) 36 | -------------------------------------------------------------------------------- /transparency_reports/2025_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4Lib 2025 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) were mobilized throughout the conference to respond to violations of the Code4Lib Code of Conduct and address any other related issues. Soojeong Herring was the coordinator and Caleb Derven was the co-coordinator. Ann Marie Mesco, Bobbi Fox, Andromeda Yelton, Thomas Dowling, Natasha Allen, Eric Phettleplace, Mike Giarlo, Kate Lynch, Michelle S. Navarro and Andrew Battelini served as Community Support Volunteers (CSVs) in online and in-person capacities. Esmé Cowles was the Local Planning Committee (LPC) Liaison to the CSS and a CSV. CSVs were provided with background reading before the conference, and an online training session was held prior to the conference in Princeton, N.J. 6 | 7 | There were at least two CSVs on duty in person during all official conference proceedings and the reception. One CSV covered the game night. At every shift during the main conference there was an additional online-only CSV dedicated to monitoring online activity. CSVs were identified by black-and-white striped lanyards and stationed in the back of the conference room. CSVs were made available to take reports in person and via web form. We used a private Slack channel to coordinate logistics, discuss issues, and come to consensus on responses. 8 | 9 | ### Incidents and Responses 10 | 11 | No incidents were reported. 12 | 13 | ### Recommendations/ Observations 14 | 15 | 1. Seating arrangement: Prior to the conference, the coordinator met with Concentra and the LPC members to discuss the seating arrangements for the in-person conference. The initial seating arrangement had the CSVs in the middle of the back row. However, in order to facilitate potentially quick exits for reporting, the final setup entailed two dedicated seats at the rear of the main conference room for the CSV members. This was a useful configuration. 16 | 2. Volunteer recruitment and shifts: There was an increase in CSV Volunteers from 2024, which meant that there was adequate coverage during sessions. 17 | - New CSVs were paired with an experienced volunteer during the shift (two volunteers for each shift) 18 | - There was one online CSV per shift. 19 | 3. Identification on Slack: During the conference, the volunteers identified themselves by adding a purple heart emoji to their Slack ID. Instructions were provided pre-conference in the CSS Volunteer Resources on how to add the purple heart emoji. 20 | 21 | Submitted by Caleb Derven 22 | -------------------------------------------------------------------------------- /transparency_reports/2021_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4lib 2021 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) worked throughout the conference to respond to 6 | violations of the [Code4lib Code of 7 | Conduct](https://github.com/code4lib/code-of-conduct). Eric Phetteplace was CSS 8 | Coordinator and Jeremy Friesen, Anne Slaughter, Wayne Graham, Bobbi Fox, Mike 9 | Giarlo, Ann Marie Mesco, Shawn Averkamp, Louisa Kwasigroch, Kate Lynch, and 10 | Michelle Janowiecki served as Community Support Volunteers (CSVs). Prior to the 11 | Conference, Eric reviewed CSS materials to ensure they were suitable for a 12 | virtual conference. CSVs were provided with background reading before the 13 | conference and with an online training session. 14 | 15 | During the conference, there were at least two CSVs monitoring online activity 16 | during all official conference proceedings. CSVs identified themselves online 17 | with a purple heart 💜 `:purple_heart:` emoji beside their name and announced 18 | themselves on Slack at the beginning of their shifts. We used a private Slack 19 | channel to coordinate logistics, discuss incidents, and come to consensus on 20 | responses. 21 | 22 | ### Incidents and Responses 23 | 24 | 1. Language in an email to all presenters referred to a person's "preferred 25 | pronouns". Community members expressed anger at representing someone's 26 | pronouns as a mere preference. Community Support reached out to Concentra who 27 | immediately agreed to change their language on future communications and 28 | included an apology in the next email to presenters. 29 | 30 | 2. Prior to the conference, a community member reported an incident involving a 31 | pattern of hostile communication. While the CSS agreed that the communication 32 | was unbefitting of a welcoming community, due to the absence of any clear 33 | Code of Conduct violation we decided that there was not an evident need to 34 | take further action with the community members involved. However, we 35 | continued, as always, to monitor closely for the hostile pattern of speech. 36 | 37 | ### Recommendations 38 | 39 | The CSS reiterates the call from the [2019 national conference transparency 40 | report](https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2019_national_conference_annual_report.md) to codify our community values. We 41 | believe this would clarify what being a welcoming community member means, 42 | as opposed to only showing how to avoid Code of Conduct violations. 43 | 44 | 1. The community needs more specifically articulated and codified values. In 45 | addition to the Code of Conduct, this would provide a lens through which the 46 | community understands and models acceptable behavior. 47 | -------------------------------------------------------------------------------- /diversity/diversity.md: -------------------------------------------------------------------------------- 1 | Code4Lib Stands in Support of Diversity, Equity, and Inclusion 2 | ============================================================== 3 | 4 | [![CC0](http://i.creativecommons.org/p/zero/1.0/80x15.png) Licensed under CC0](http://creativecommons.org/publicdomain/zero/1.0/) 5 | 6 | Short link: TBD 7 | 8 | [DRAFT - Please feel free to edit, thank you! - Bohyun] 9 | 10 | 11 | The 2016 US election season has been followed by many appalling acts of hate around the country. For this reason, Code4Lib is re-affirming our unfaltering support and strong commitment to the fundamental values of diversity, equity, and inclusion. Code4Lib has a proud history of recognizing the lack of diversity in the technology sector as a serious problem and acting to address it head-on. In the Code4Lib community, diversity, equity, and inclusion are not mere words. They underpin all we do, through Diversity Scholarships, the Newcomer Dinner, our Code of Conduct, or our decision regarding the speakers, presenters, and location of our next Code4Lib conference. They represent and reflect our shared and cherished understanding that we always solve difficult problems better together 12 | 13 | As technologists, we always look for ways to make things work better. We love efficiency; we love elegance; we aspire to be free of any pain point or bug in everything we design and build. We do this not solely for the sake of efficiency, elegance, and our deeply-rooted desire to improve things. Rather, we look for ways to make things work better for the sake of people. Our ultimate aspiration is to help people get things done with the tools we create with delight. For this reason, we try to understand our users with all their differences in race, sex, sexual orientation, gender identity, religion, disability, age, genetic information, veteran status, ancestry, national or ethnic origin, language, socio-economic background, and citizenship status. This is why we rely on empathy as one of the most important guiding principles in all we do as technologists. Without our caring, our work as developers, designers, information specialists, and IT professionals would be missing its heart.  14 | 15 | As a community that deeply values diversity, equity, and inclusion, Code4Lib will always be a welcoming and safe community for all who are passionate about information and technology. Everyone in our community is valued and respected regardless of what they look like, what their faiths are, what disabilities they may have, how they identify their gender, who they love, where they come from, what language they speak, where they live, or what level of expertise they have. There is no place for bigotry, intolerance, hatred, harassment, or violence in Code4Lib. Today, we stand together in our most forceful support of diversity, equity, and inclusion.  16 | 17 | -------------------------------------------------------------------------------- /norms.md: -------------------------------------------------------------------------------- 1 | Community Norms and Values 2 | ========================== 3 | 4 | ## Introduction 5 | 6 | [BIG TBD HERE!!] 7 | 8 | As it is written on the Code4Lib [website](https://code4lib.org/about/), Code4Lib isn’t entirely about code or libraries. It is a *volunteer*-driven collective of hackers, designers, architects, curators, catalogers, artists and instigators from around the world, who largely work for and with libraries, archives and museums on technology “stuff.” It started in the fall of 2003 as a mailing list when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. 9 | 10 | Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. To that end, we've created an ever-evolving [Code of Code4Lib Conduct](code_of_conduct.md) , which addresses, in general, our expectations of the community. 11 | 12 | This page serves to address some specific norms that we hope to promote for various Code4Lib channels. 13 | 14 | ## The listserv 15 | 16 | The [listserv](https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB) remains a vital part of the Code4Lib community. 17 | 18 | ### Appropriate topics 19 | 20 | Although its formal definition states that it "... provides a forum for discussion all things relating to programming code for libraries. This is a place to discuss particular programming languages, but also provides a place to discuss the issues of programming in libraries in general.", it can also be a place to discuss related topics, such as the issues of being the programmer in a library. The questions of diversity, sexual harassment, microagressions, etc., may all be appropriate related topics of discussion. 21 | 22 | ### Anonymity 23 | 24 | In general the community prefers to know who is writing. Exceptions may arise when the you feel at risk; in that case, the you may contact one or more [Community Support Volunteers](css_volunteers.md) for help forwarding your message. At the least, your message should include a *reason* for why you are choosing to be anonymous. For example: 25 | 26 | * "I'm looking for advice on how to present myself for another job, but my boss doesn't know I'm looking" 27 | * "I'd like some advice in dealing with a programming 28 | conflict, and other members of the team are on this list" 29 | 30 | ### Surveys 31 | 32 | If you wish to ask people on the listserv to participate in a survey, you should minimally identify: 33 | 34 | * yourself 35 | * purpose of the survey 36 | * the reason you're asking **in this listserv** 37 | * what kinds of information you're collecting 38 | * (if collecting identifying information such as email address, name), what you plan to do with it, and how you'll keep it secure. 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | -------------------------------------------------------------------------------- /transparency_reports/2024_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4Lib 2024 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) were mobilized throughout the conference to respond to violations of the Code4Lib Code of Conduct and address any other related issues. Soojeong Herring was the coordinator. Ann Marie Mesco, Bobbi Fox, Andromeda Yelton, Bess Sadler, Michael Giarlo, and Coral Sheldon-Hess served as Community Support Volunteers (CSVs) in online and in-person capacities. Natasha Allen was the Local Planning Committee (LPC) Liaison to the CSS and a CSV. CSVs were provided with background reading before the conference, and an online training session was held prior to the conference in Ann Arbor, MI. 6 | 7 | There were at least two CSVs on duty in person during all official conference proceedings, including the reception and game night, and during every shift there was an additional online-only CSV dedicated to monitoring online activity. CSVs were identified by black-and-white striped lanyards and stationed in the back of the main room. CSVs were made available to take reports in person and via web form. We used a private Slack channel to coordinate logistics, discuss issues, and come to consensus on responses. 8 | 9 | ### Incidents and Responses 10 | 11 | No incidents were reported. 12 | 13 | ### Recommendations 14 | 15 | 1. Seating arrangement: Prior to the conference, the coordinator met with Concentra and the LPC members to discuss the seating arrangements for the in-person conference. The planned set up was to have a separate rectangle table for the CSV members. However, the actual set up was a shared round table other attendees. The shared table became an issue when it was used during the breakout sessions when their seat were occupied by other attendees while the volunteers were away. This was an unexpected situation for the LPC members as well. The coordinators will communicate with future LPCs and Concentra to secure dedicated seating spots for the volunteers. 16 | 1. Volunteer recruitment and shifts: The coordinator called for volunteers before the vetting process with extended due date to encourage participation. However, there were fewer volunteers this year compared to previous years, and CSVs had more shifts to take during the in-person conference. The CSVs held a debriefing meeting and discussed possible one volunteer per shift if the volunteers have previous experience. 17 | - CSV will make sure that new volunteers will be paired with an experience volunteer during the shift (two volunteers for the shifts) 18 | - CSV will brainstorm to invite new members to distribute shifts evenly (e.g. holding a session to introduce and a Q&A session, giving a short presentation during a lightening talk session, etc.). 19 | - CSV will keep the one online volunteer per shift. 20 | 1. Identification on Slack: During the conference, the volunteers identified themselves by adding a purple heart emoji to their Slack ID. Several volunteers reported difficulty in adding the emoji. 21 | - The coordinator will provide clear instructions on how to add a purple heart emoji, ensuring all volunteers can properly identify themselves on Slack during the conference. 22 | 23 | Submitted by Soojeong Herring 24 | -------------------------------------------------------------------------------- /how_changes_are_made.md: -------------------------------------------------------------------------------- 1 | # How Changes are Made to the Code4Lib Code of Conduct 2 | 3 | The purpose of this document is to clearly outline a transparent means of modifying the Code4Lib community's Code of Conduct and related community standards. 4 | 5 | 1) One should submit changes to the Code of Conduct and its related documents as a Pull Request (PR) on [the Code of Conduct repository](https://github.com/code4lib/code-of-conduct). If you are uncomfortable with GitHub and PRs, you can contact the people listed in [css_volunteers.md](https://github.com/code4lib/code-of-conduct/blob/master/css_volunteers.md) and they will help compose one on your behalf. No one has to log into Github if they do not want to. 6 | 7 | It is preferable for changes to be logically segmented as opposed to sets of unrelated edits to different files. For instance, adding a name to SUPPORTERS.txt, fixing a typo in code_of_conduct.md, and adding a list item to norms.md are better as three separate requests than a single monolithic one. 8 | 9 | 2) Pull Requests generate their own discussion threads where questions can be asked and changes may be proposed or incorporated. Changes to the PR must be made or approved by its original author(s); if they do not agree with the changes, then the changes are better suited to becoming a separate PR. As with creating PRs, if you are not comfortable commenting on a PR for any reason, you may reach out to the CSS who will do so on your behalf. Once discussion has ended on a PR, indicated by two weeks without a comment or change submitted, the PR is ready to be reviewed. 10 | 11 | 3) The Community Support Squad (CSS) reviews the changes suggested by the Pull Request and either approves them, rejects them, or re-opens discussion on the PR with further comments, questions, or suggested changes. In order to be approved, a majority of CSS members must vote in favor of the PR. For instance, if three of seven CSS members vote in favor of a PR, while only one votes against it and three abstain, then the PR would be rejected. 12 | 13 | The Community Support Squad may decide that a set of proposed changes are so wide-reaching, or subject to so much disagreement or controversy, that a community-wide vote must be called. 14 | 15 | Examples of changes that call for a community vote are: this document itself, which introduces a new procedure related to the Code of Conduct and changes the nature of the CSS's responsibilities within the Code4Lib community; an addition of an entire section to the Code, such as a new method or philosophy of enforcement; and any change that generates substantial debate within the community or the CSS itself, for instance one with several comments on its PR that represent divergent points of view. 16 | 17 | In those instances, the CSS conducts a community vote with an accessible, web-based form with the following elements: 18 | 19 | - respondent email address, used only to deduplicate responses and not visible outside the CSS 20 | - the proposed changes 21 | - the discussion on GitHub and any additional, relevant resources 22 | - an option to approve or reject the changes 23 | 24 | Community votes will be held open for one month, with a reminder 2 weeks before they close, and changes approved if greater than half of respondents agree with them. 25 | -------------------------------------------------------------------------------- /diversity/README.md: -------------------------------------------------------------------------------- 1 | Post-Election Statement on Diversity, Equity, and Inclusion from Code4Lib 2 | ========================================================================= 3 | 4 | This is a repository to provide a space to draft and allow for dialog in the creation of a statement on diversity for the [Code4lib](http://code4lib.org/) community. 5 | 6 | ## Resources for starting points: 7 | 8 | * Many example statements: [Post-election Statements and Messages that Reaffirm Diversity](http://www.bohyunkim.net/blog/archives/3620) 9 | 10 | ### From Libraries 11 | 12 | * [University of Oregon Libraries](https://web.archive.org/web/20170901161018/https://library.uoregon.edu/sites/default/files/open_letter_diversity_equity_response_2016_2.pdf) 13 | * [Northwestern University Libraries](https://www.linkedin.com/pulse/affirming-library-values-sarah-pritchard) 14 | * [James Madison University Libraries](https://www.lib.jmu.edu/statement-on-jmu-libraries-as-safe-spaces/) 15 | 16 | ### From Library Associations 17 | 18 | * [LITA](http://www.ala.org/news/member-news/2016/11/solidarity-words-solidarity-action) 19 | * [ARL](http://www.arl.org/news/arl-news/4154-research-libraries-and-archives-stand-committed-to-diversity-inclusion-equity-social-justice) 20 | * [ALA](https://americanlibrariesmagazine.org/blogs/the-scoop/statement-libraries-association-diversity-inclusion/) 21 | * [PLA](https://americanlibrariesmagazine.org/blogs/the-scoop/statement-libraries-association-diversity-inclusion/) 22 | * [DLF](https://www.diglib.org/archives/12979/) 23 | 24 | ### From Higher Ed 25 | 26 | * [University of California](https://www.universityofcalifornia.edu/press-room/university-california-statement-election) 27 | * [University of Nevada, Reno](http://www.unr.edu/president/communications/2016-11-10-election) 28 | * [University of Michigan](http://president.umich.edu/news-communications/letters-to-the-community/2016-election-message/) 29 | * [University of Oregon](https://around.uoregon.edu/content/president-schill-emphasizes-need-inclusion-campus) 30 | * [CUNY](http://www1.cuny.edu/mu/forum/2016/11/10/statement-from-chancellor-james-b-milliken-on-the-presidential-election/) 31 | 32 | ### From IT Associations 33 | 34 | * ??? 35 | 36 | ### From Other Organizations 37 | 38 | * [ACLU](https://www.aclu.org/news/aclu-statement-donald-trumps-election) 39 | * [Joint Statement from California Legislative Leaders on Result of Presidential Election](https://web.archive.org/web/20170117223701/http://sd24.senate.ca.gov/news/2016-11-09-joint-statement-california-legislative-leaders-result-presidential-election) 40 | * [Black Lives Matter](https://mic.com/articles/159496/exclusive-black-lives-matter-issues-a-statement-on-trump-s-election#.qcQGBdRR1) 41 | 42 | ## Open questions 43 | 44 | * Add your questions here. 45 | * Don't be shy. 46 | 47 | ## License 48 | 49 | [![CC0](http://i.creativecommons.org/p/zero/1.0/80x15.png) Licensed under CC0](http://creativecommons.org/publicdomain/zero/1.0/) 50 | 51 | ## Discuss 52 | 53 | Discussion is welcome either on the [Code4lib listserv](https://listserv.nd.edu/cgi-bin/wa?SUBED1=CODE4LIB&A=1) or by creating a new issue: https://github.com/code4lib/code-of-conduct/issues/new 54 | 55 | ## Contribute 56 | 57 | ### Using Github (doesn't require knowing Git) 58 | 59 | * The Code4Lib diversity statement and the related stuff is located in a child directory "diversity" inside the 'Code of Conduct' repository 60 | 61 | * See the Contribute Section (https://github.com/code4lib/code-of-conduct/blob/master/README.md#contribute) of the README file of the parent repository 'Code-of-Conduct' 62 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Code4lib Anti-Harassment Policy 2 | =============================== 3 | 4 | This is repository is a space for dialog in the maintenance of an anti-harassment policy for the [Code4lib](http://code4lib.org/) annual conference, mailing list, and other Code4Lib channels. 5 | 6 | Resources for policies/starting points: 7 | 8 | * [The Ada Initiative: Anti-harassment work](http://adainitiative.org/what-we-do/conference-policies/) 9 | * [Geek Feminism Wiki: example anti-harassment policy for conferences](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) 10 | * [how to hack code4lib: don't be sexist/racist/*ist](http://wiki.code4lib.org/index.php/How_to_hack_code4lib#Don.27t_be_sexist.2Fracist.2F.2Aist) 11 | * [MoreThanMen.org Harassment policy examples for conferences ](http://www.morethanmen.org/harassment-policies/) 12 | * [CAUT Anti-harassment and Non-Discrimination Statement](http://www.caut.ca/about-us/caut-policy/lists/administrative-procedures-and-guidelines/caut-anti-harassment-statement) 13 | * [AAI Anti-harassment policy](http://www.atheistalliance.org/activities/23-conventions/507-anti-harassment-policy): This is a good one because it includes a short boilerplate statement for conferences/events, plus a longer document suitable for the organization as a whole. 14 | 15 | ## Code of Code4Lib Conduct 16 | 17 | The [Code of Code4Lib Conduct](code_of_conduct.md) is an evolving document that applies not only to the annual Code4Lib conference, but also to the other ways we interact, including the[Code4lib listserv](https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB), [irc](https://code4lib.org/irc/), and other Code4Lib venues, such as the Slack and Discord channels. 18 | 19 | As we learn and grow, we welcome suggestions for changes. You can [follow our change procedures](https://github.com/code4lib/code-of-conduct/blob/main/how_changes_are_made.md) to make suggestions in one of the following ways: 20 | 21 | * If you are familiar with **git** and **GitHub**, you can fork this repository, make your changes, and submit a Pull Request. See "Contribute", below. 22 | * You may create a new issue: [https://github.com/code4lib/code-of-conduct/issues/new]() 23 | * You can send an email to one or more of the people identified as members of the [Community Support Squad](css_volunteers.md). 24 | 25 | ## License 26 | 27 | [![CC0](http://i.creativecommons.org/p/zero/1.0/80x15.png) Licensed under CC0](http://creativecommons.org/publicdomain/zero/1.0/) 28 | 29 | ## Discuss 30 | 31 | Discussion is welcome here in the repository's [issues](https://github.com/code4lib/code-of-conduct/issues) or the other major Code4Lib channels: the [Code4lib listserv](https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB), [irc](https://code4lib.org/irc/), [Slack](https://code4lib.slack.com/), and Discord. 32 | 33 | ## Contribute 34 | 35 | ### Using Github (doesn't require knowing Git) 36 | 37 | 1. Fork the codebase e.g. to https://github.com/your-username/code-of-conduct (click the "Fork" button in the upright corner of the page) 38 | 1. Click the link for one of the files (e.g. `code_of_conduct.md`) 39 | 1. Click the Edit button 40 | 1. Add a commit summary and (optionally) an extended description 41 | 1. Click the Commit Changes button 42 | 1. Create a pull request by clicking the Pull Request button at the top of the page 43 | 44 | ### Using Git 45 | 46 | 1. Fork the codebase e.g. to https://github.com/your-username/code-of-conduct 47 | 1. Clone your fork locally (`git clone 48 | git@github.com:your-username/code-of-conduct my-code-of-conduct`) 49 | 1. Create a branch to hold your changes (`git checkout -b my-changes`) 50 | 1. Commit the changes you've made (`git commit -am "Some descriptive text around 51 | what you've added"`) 52 | 1. Push your branch to github (`git push origin my-changes`) 53 | 1. Create a pull request e.g. at https://github.com/your-username/code-of-conduct/pull/new/master 54 | -------------------------------------------------------------------------------- /csvcharge.md: -------------------------------------------------------------------------------- 1 | # Community Support Squad Charge 2 | 3 | Community Support Squad (CSS) coordinators and volunteers should be a small group of kind, articulate, and trustworthy people who reflect the diversity of the community. Community Support Volunteers (CSV) will be responsible for: 4 | 5 | * Taking reports of code of conduct violations while at the conference during scheduled shifts 6 | * Referring reporters to appropriate services (e.g. conference staff for incident response, medical or other emergency services) 7 | * Participating in decisions about responses to code of conduct violations 8 | * Participating in responses as appropriate. 9 | 10 | This work is outlined more specifically in the [Procedures](procedures.md) document. 11 | 12 | Volunteers will not: 13 | 14 | * Respond to front-line customer service queries (these are probably best handled by the registration desk) 15 | * Be everyone's pal 16 | * Follow reporters to offsite medical or other services (community support volunteers need to stay onsite; delegate this task to someone the reporter trusts if needed) 17 | * Put themselves in danger (DO NOT DO THIS FOR ANY REASON. Your personal safety supersedes your community support volunteer responsibilities.) 18 | 19 | CSVs will work in scheduled shifts, will be clearly indicated (at a specified location, wearing something distinctive), and available at all official conference events, including social events. There should be enough volunteers that no one has to be constantly on. A CSV should be constantly interruptible, so they shouldn't also be doing noninterruptible conference tasks (e.g. livestreaming). 20 | 21 | CSVs going off-shift should brief those coming on about recent incidents, if applicable. 22 | Conference organizers should recognize the handles that community support volunteers will use to contact them (phone numbers, IRC nicks, etc. - decide in advance and collate this info). They should treat contacts from community support volunteers as priority interrupts. 23 | 24 | ## Coordinators 25 | 26 | In consultation with the previous year’s coordinators, the Local Planning Committee (LPC) will recruit two co-coordinators, working to ensure some measure of diverse representation. LPC will also designate two conference organizers to serve as liaisons to the CSS, commit to becoming familiar with the Code Of Conduct and reporting procedures, and provide backup in incident response. The co-coordinators and LPC liaisons will be vetted by the community through a comment period, handled by previous year’s coordinators/LPC/designee. 27 | 28 | Once vetted, responsibilities of the coordinators include: 29 | 30 | * Send an open call for volunteers to the community 31 | * Review list of volunteers and submit to the community for comment 32 | * Finalize the list of volunteers following the comment period 33 | * Consult last year's organizers for any knowledge they need to transfer relevant to enforcement (e.g. prior incident response; iterations to procedure; or people with ongoing sanctions). 34 | * Familiarize volunteers with procedures and code of conduct, and gather logistical information for planning purposes 35 | * Create a schedule for coverage throughout the conference activities 36 | * Review and prepare training materials; schedule and provide training to volunteers 37 | * Provide guidance throughout the conference to the volunteers and convene conversations to make decisions about reports. 38 | * Decide how conference goers will be able to recognize community support 39 | volunteers, and publicize this 40 | * Ensure that leaders of official off-site events (tours / newcomer dinners, etc) are familiar with Code Of Conduct. 41 | * Ensure Local Planning committee includes a quiet, private space suitable for taking reports in venue requirements. 42 | * Establish lines of communication for CSS (i.e. private Slack channel for communications prior to conference; Signal for on-the-ground communication at the conference) and make sure all volunteers have each others' contact information. 43 | * Investigate local laws that may affect procedures. 44 | 45 | ## Supplies 46 | 47 | * Working, charged phone and charger 48 | * Contact information for senior conference organizers 49 | * Local contact information: emergency services, venue security, taxi companies, mental health crisis hotline, sexual assault crisis hotline 50 | * Venue maps, including accessibility information 51 | * Read/write access to incident logs from all community support volunteers at this event 52 | * Access to a quiet, private space suitable for taking reports 53 | * A copy of the procedures for responding to code of conduct violations 54 | * Paper for recording reports 55 | -------------------------------------------------------------------------------- /transparency_reports/2023_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4Lib 2023 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) were mobilized throughout the conference to respond to violations of the Code4Lib Code of Conduct and address any other related issues. Soojeong Herring, Eric Phetteplace, and Anne Slaughter were coordinators. Ann Marie Mesco, Bobbi Fox, Andromeda Yelton, Francis Kayiwa, Bess Sadler, Carolyn Cole, Sharon Clapp, Michael Giarlo, and Kevin Reiss served as Community Support Volunteers (CSVs) in online and in-person capacities. Esmé Cowles was the Local Planning Committee (LPC) Liaison to the CSS and a CSV. CSVs were provided with background reading before the conference, and an online training session was held prior to the Princeton conference. 6 | 7 | There were at least two CSVs on duty in person during all official conference proceedings, including the reception and game night, and during every shift there was an additional online-only CSV dedicated to monitoring online activity. CSVs were identified by black-and-white striped lanyards and stationed in the back of the main room. CSVs were made available to take reports in person and via web form. We used a private Slack channel to coordinate logistics, discuss issues, and come to consensus on responses. 8 | 9 | ### Incidents and Responses 10 | 11 | 1. Prior to the conference, a registered attendee reached out to the coordinators about whether another individual from whom they’d previously experienced unwanted contact was registered to attend the conference. It was determined that coordinators may confidentially obtain and verify attendance information in response to safety concerns, while minimizing any opportunities for abuse of this information. Additionally, a code phrase was developed to share individually with any attendees expressing similar concerns, to be used in the event of an issue as a discreet way to alert nearby CSVs and activate appropriate bystander interventions or other supportive tactics. CSS procedures have been updated to reflect these decisions for future implementation as needed. 12 | 2. Shortly after the 2023 conference, the Community Support Squad received a report about an individual’s behavior during the 2022 conference in Buffalo. In front of a few people, they used a racist slur about another attendee. Coordinators sent the individual a direct message with a warning that such behavior is a violation of the Code of Conduct and unacceptable in any circumstance. Coordinators will also reach out to the 2024 Scholarship Committee, once established, to recommend that the individual not be allowed to serve as a buddy for scholarship recipients at future conferences because of this unwelcoming behavior. Existing documentation and procedures will ensure this information is shared appropriately in future years. 13 | 14 | ### Recommendations 15 | 16 | 1. In the past, CSVs assigned to online shifts were asked to actively monitor Slack and Twitter, with the option of additional platforms with a Code4Lib presence like Mastodon or Discord. Due to very low volume of backchannel discussions outside of Slack, and the difficulty of monitoring all possible discussions across many disparate platforms, the CSS recommends focusing online monitoring on Slack. Procedural documentation has been updated accordingly. 17 | 2. Regarding the conference stream and related procedures, the CSS has two recommendations: 18 | 1. YouTube comments were initially turned on for the 2023 conference stream, and were turned off upon request from the CSS after this was noticed. The CSS agreed that ongoing practice should remain consistent with the 2019 decision to turn off YouTube commenting ability after inflammatory comments were posted, and has updated procedural documentation and reached out to the Streaming Committee to this effect. 19 | 2. After a lightning talk in which sensitive personal information was revealed, the speaker opted to have their talk removed from the recording that would be posted on YouTube. The CSS recommends that the Streaming Committee establish a means by which speakers can opt to have their talks edited out of recordings in a similar fashion. 20 | 3. Regarding the occasional inclusion of content that is appropriate to the presentation topic but could be harmful to attendees and viewers, the CSS recommends that the Program Committee draft guidance and possible template language for presenters in the handling of such content and the use of content warnings. 21 | 4. 2023 was the first year in which Concentra assisted with CSV recruitment and scheduling, and the CSS recommends continuing with this distribution of responsibilities. 22 | 23 | Submitted by Soojeong Herring, Eric Phetteplace, and Anne Slaughter 24 | -------------------------------------------------------------------------------- /transparency_reports/2019_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4lib 2019 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) worked throughout the conference to respond to 6 | violations of the [Code4lib Code of 7 | Conduct](https://github.com/code4lib/code-of-conduct). Anne Slaughter and 8 | Francis Kayiwa were co-coordinators, and Karen Coyle, Justin Coyne, Shaun Ellis, 9 | Erin Fahy, Bobbi Fox, Wayne Graham, Megan Kudzia, Chad Nelson, Mark Matienzo 10 | (LPC Liaison), and Aaron Collier (LPC Liaison) served as Community Support 11 | Volunteers (CSVs). Prior to the Conference, Anne and Francis revised the 12 | [procedures](https://github.com/code4lib/code-of-conduct/blob/master/procedures.md) 13 | and established a distinct [charge for the 14 | CSS](https://github.com/code4lib/code-of-conduct/blob/master/csvcharge.md). CSVs 15 | were provided with background reading before the conference, and a training 16 | session in San Jose. 17 | 18 | During the conference, there were at least two CSVs on duty during all official 19 | conference proceedings, and during most shifts there was an additional CSV 20 | dedicated to monitoring online activity. CSVs were identified by striped 21 | lanyards and posted in the back of the main room, and available to take reports 22 | in person, via webform, or by phone (using a dedicated burner phone). We used 23 | the Signal app and a private Slack channel to coordinate logistics, discuss 24 | incidents, and come to consensus on responses. 25 | 26 | ### Incidents and Responses 27 | 28 | 1. Commenters on the YouTube stream got into a heated conversation that turned 29 | insulting. CSV stepped in with a general reminder about code of conduct and 30 | the CSS decided to turn off commenting on the stream. 31 | 2. A CSV encountered a hotel guest not affiliated with the conference who was 32 | disturbed by the all-gender restroom signage, and suggested they seek out a 33 | gender-specific restroom. 34 | 3. Comments made publicly about one of the conference speakers on Slack and 35 | Twitter became unwelcoming. 36 | 4. A report was taken regarding a microaggression experienced by an attendee. An 37 | announcement was made from the podium the next morning reminding attendees to 38 | model desired behavior in the community. The statement was intended to 39 | address this report as well as the incident described in #3. 40 | 41 | ### Recommendations 42 | 43 | The coordinators debriefed with each other and with the CSVs. In addition to the 44 | experience and feedback we will use to improve CSS operations in the future 45 | and/or pass on to future coordinators we have the following recommendations for 46 | the community. 47 | 48 | 1. The community needs more specifically articulated and codified values. In 49 | addition to the Code of Conduct, this would provide a lens through which the 50 | community understands and models acceptable behavior. 51 | 2. The CSS should be a standing committee (as articulated in Mark Matienzo's 52 | lightning talk in San Jose). The official enforcement of the Code of Conduct 53 | should not be limited to the annual national conference. This standing 54 | committee would be initially led by Francis Kayiwa, Mark Matienzo, and Anne 55 | Slaughter, along with others in the community to be recruited, and would focus 56 | on revising the current Code of Conduct and establishing standing channels 57 | for detecting, reporting, and responding to violations. We would keep the 58 | email and anonymous webform open for reporting, and have discussions with 59 | CLIR regarding ongoing hosting and storage. 60 | 3. Conference planning considerations: 61 | * A follow-up survey of attendees would be generally useful for the incoming 62 | LPC. If established, this survey should include a mechanism for attendees 63 | to report code of conduct violations. The number of reports was down from 64 | previous years, which could signal fewer actual incidents, but it could 65 | also mean that incidents were not reported. This recommendation is one 66 | measure that may help us reduce barriers to and increase comfort levels 67 | with reporting. 68 | * It would be useful to have some preconference time dedicated to newcomer 69 | onboarding and/or community support-related content. This could take the 70 | form of one or more actual workshops, or a webinar in advance of the 71 | conference. Content could include the supports and tools currently in 72 | place in the community as well as general support for allies such as 73 | active bystander training, identifying and dealing with microaggressions, 74 | etc. 75 | * Briefly introduce all CSVs on stage at beginning of conference to 76 | facilitate recognition and allow them to set a welcoming tone. 77 | -------------------------------------------------------------------------------- /transparency_reports/2020_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4lib 2020 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) worked throughout the conference to respond to violations of the Code4Lib Code of Conduct. Natasha Allen and Eric Phetteplace were co-coordinators. Shawn Averkamp, Jeremy Friesen, Bobbi Fox, Mike Giarlo, Wayne Graham, Ann Marie Mesco, Chad Nelson, and Anne Slaughter served as Community Support Volunteers (CSVs) in online and in-person capacities. Ann Marie Mesco and Ken Rose were our LPC Liaisons this year. CSVs were provided with background reading before the conference, and an online training session was held a few days prior to the Pittsburgh conference. 6 | 7 | There were at least two CSVs on duty during all official conference proceedings, and during every shift there was an additional CSV dedicated to monitoring online activity. CSVs were identified by black and white striped lanyards and posted in the back of the main room. CSVs were made available to take reports in person, via web form, and by phone using a Google Voice number managed by Natasha Allen. Natasha’s Google Voice number was also used as the overnight reporting number. We used a private Slack channel to coordinate logistics, discuss incidents, and come to consensus on responses. 8 | 9 | ### Incidents and Responses 10 | 11 | 1. A report was submitted to the online incident report form from an attendee with a helpful suggestion to edit the signage for the gender-neutral restrooms to indicate whether or not the restrooms had in-stall trash cans. We took their suggestion upon consultation with the LPC and edited the signage to include information about whether or not the restrooms had trash cans in their stalls. 12 | 2. A conference attendee sent an email indicating that a colleague, who also attended the conference, may have unintentionally exposed others to COVID-19. The individual had not been tested as the symptoms were mild, but felt it was important to let the CSS know. Natasha forwarded the information on to the LPC and helped draft a response to the community for transparency purposes. The individual later tested negative for the disease and a follow-up response was sent out to the community. 13 | 14 | ### Recommendations 15 | 16 | The coordinators debriefed with each other remotely via Zoom. The CSVs were debriefed during an asynchronous Slack conversation. Here are our recommendations we hope to pass on to the next LPC group and/or the next CSV committee. 17 | 18 | 1. The 2020 coordinators agree with last year’s CSS that the community needs more specifically articulated and codified values. In addition to the Code of Conduct, this would ground the community’s understanding and modeling of acceptable behavior. 19 | + We believe one of the concrete ways to establish codified values is by creating a process for approving change requests to the CoC on GitHub. We recommend that current CSS Coordinators establish a process with which to send notification to the community of any major change requests in the CoC. This will allow those unfamiliar with or uncomfortable with using GitHub to be a part of the approval process. We recommend leaving open the opportunity for public comment for a period of 7 days, then approving the changes after the 7-day period is complete. Questioned or flagged changes will need to be resolved before approval. Minor changes such as spelling or grammar issues can be changed at the coordinators’ discretion. Of course, any community members can sound off on all changes, including minor ones, given CoC changes occur publicly via GitHub pull requests. 20 | 2. We agree with the 2019 CSS Coordinators that this group should be a year-round standing committee. As Code4Lib is more than an annual conference, the official enforcement of the Code of Conduct should not be limited to the conference. We recommend that current coordinators submit themselves as the current committee members for a period of one year, assuming they are able and willing, and that at least 1-3 more people volunteer to monitor the Google group and web form submissions and discuss any violations that arise regularly during that 1-year period. 21 | 3. We strongly recommend that, at the very least, conference organizers send out a simple post-conference survey every year to gather additional feedback from attendees. A follow-up survey of attendees would be generally useful for the incoming LPC. We recommend providing a space for CoC incidents to be reported as well as an (optional) contact information field to be used for the express purpose of soliciting volunteers for the next year. We noticed multiple committees this year, including our own, struggled to find enough volunteers to carry out duties related to the conference. This survey question could provide a pool of potential volunteers to contact for the following year. 22 | + A more ambitious, related, goal would be to develop an entirely separate C4L conference committee tasked with developing and sending out a yearly survey and potentially coordinating the pool of volunteers. Anyone who might be interested in joining this group for the years 2020-2021 can message Natasha Allen @natasha on slack or email her at [ndallen@umich.edu](mailto:ndallen@umich.edu) 23 | 24 | Submitted by Natasha Allen and Eric Phetteplace 25 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /transparency_reports/2022_national_conference_annual_report.md: -------------------------------------------------------------------------------- 1 | # Code4Lib 2022 Community Support Squad Transparency Report 2 | 3 | ## Summary 4 | 5 | The Community Support Squad (CSS) were mobilized throughout the conference to respond to violations of the Code4Lib Code of Conduct and address any other related issues. Anne Slaughter was the coordinator. Mike Giarlo, Jackie Gosselar, Tess Grynoch, Francis Kayiwa, Ann Marie Mesco, Chad Nelson, Eric Phetteplace, Daniel Sanford, Andromeda Yelton and Bobbi Fox served as Community Support Volunteers (CSVs) in online and in-person capacities. Francis Kayiwa was also the Local Planning Committee (LPC) Liaison to the CSS. CSVs were provided with background reading before the conference, and an online training session was held a few days prior to the Buffalo conference. 6 | 7 | There were at least two CSVs on duty in person during all official conference proceedings, including the reception and game night, and during every shift there was an additional online-only CSV dedicated to monitoring online activity. CSVs were identified by black-and-white striped lanyards and posted in the back of the main room. CSVs were made available to take reports in person and via web form. We used a private Slack channel to coordinate logistics, discuss issues, and come to consensus on responses. 8 | 9 | In a departure from previous in-person conferences, there was only one coordinator instead of two, and the coordinator came on board approximately six weeks before the conference, which dramatically shortened the typical timeframe for planning and volunteer recruitment, vetting, and preparation. Because work needed to start immediately, and because the coordinator had been previously vetted in 2019, 2020, and 2021, there was no coordinator vetting process. In addition, repeat volunteers were not vetted - which was particularly important to the compressed timeline when additional volunteers were needed after the initial recruitment and vetting process. 10 | 11 | ### Incidents and Responses 12 | 13 | No incidents were reported. 14 | 15 | ### Recommendations 16 | 17 | 1. Reserved seats for CSVs in the conference space should be next to each other, and not across an aisle, to facilitate quiet discussion of any issues that arise. 18 | 19 | 2. Regarding the coordinator role: 20 | 1. There should be two CSS coordinators, and the CSS recommends that we implement a new model with each coordinator serving a two-year term that rolls over in alternating years (first year as vice-chair, second year as chair). The relative success of having one coordinator in 2022 was due to the fact that the coordinator had previous experience as a co-coordinator and as a CSV, the 2020-2021 coordinator served as a CSV and sounding board, and the LPC liaison had previous co-coordinator and CSV experience. However, the role requires a great deal of administrative and emotional labor, and it is not ideal for the community, the CSVs, or the coordinator themselves for it to be a solo role. Additionally, in recent history coordinators have served the same term with the norm being 100% turnover from year to year, but institutional/historical knowledge has proven to be critical to many aspects of CSS operations. 21 | 2. Find other ways to make the coordinator job less labor-intensive, and/or more attractive. The 2022 and 2020-2021 coordinators consulted with Concentra on ways the Concentra staff may be able to help reduce some of the administrative workload, and agreed that Concentra staff would assist with some of communications and administrative tasks involved with recruitment and scheduling in 2023. This will be evaluated as part of the post-conference debrief for effectiveness and continued collaboration. They also discussed possible incentives for coordinators, including a formal letter of appreciation for their service, which will be further discussed during the planning process for the 2023 annual conference. 22 | 3. Explore opportunities to streamline the challenging process of identifying and recruiting a sufficient number of volunteers to serve as CSVs. The CSS suggests that the LPC actively assist with the recruitment process, in addition to leveraging Concentra’s participation in the process. 23 | 4. Continue with not offering overnight support, as this is out of scope for a volunteer without the appropriate professional training. In an emergency situation outside of official conference hours, it is likely best for an affected individual to immediately contact emergency services. If a situation arises that doesn’t require emergency services, an affected individual may still make a report via other available means and CSVs will respond in the morning. 24 | 5. Continue with not offering phone support, in conjunction with discontinuing overnight support, and because there are multiple other readily available means of access to the CSS (including Slack, email, report form, and direct in person contact) for expressing concerns and making reports. Coordinators should not feel obligated to incur personal expenses securing a burner cell phone to be passed between volunteers, or for one coordinator to assume 24/7 on-duty responsibilities by publishing and using a Google Voice number that rings to their personal cell phone. 25 | 6. Regarding the procedural changes made to the vetting process for 2022 in the interests of time, the CSS should generally revert back to previously established practices. There was no consensus among the CSVs as to possible acceptable longer-term changes to the process, and general agreement that the vetting of coordinators and volunteers, while not perfect, has value as one method of ensuring community safety. 26 | 7. Continuity of community support outside of the annual conference remains an issue that many of us who are invested in this effort have thus far been unable to sustainably address. A two-year commitment on the part of coordinators may address a small facet of the issue, but it still seems that some additional minimal structure and volunteer support is needed to be able to address any code of conduct issues that arise throughout the year. 27 | 1. The community needs more specifically articulated and codified values. In addition to the Code of Conduct, this would provide a lens through which the community understands and models acceptable behavior. (Recommended in 2019; reiterated by all subsequent coordinators) 28 | 2. The CSS should be a standing committee (as articulated in Maria Matienzo’s lightning talk in San Jose 2019), or have some form of continued ongoing structure for responding to code of conduct concerns. As Code4Lib is more than an annual conference, the official enforcement of the Code of Conduct should not be limited to the conference. (Recommended in 2019; reiterated by all subsequent coordinators. Implementation of various specific ideas articulated in these past reports has been attempted, but from year to year there has typically only been 1-3 involved individuals, and despite the best of intentions they have generally been unable to maintain the high level of commitment and emotional labor required to develop and implement a sustainable ongoing system.) 29 | 1. The 2022 CSS discussed possibilities for a minimum viable structure that would still ensure some level of ongoing attention to code of conduct issues, based on the concept of establishing a pool of people who could discuss and respond to issues as individual bandwidth allows. These ideas included setting up a Slack channel of willing CSV “alumni” from the past several years, or adding those individuals to an announcement-only Google Group to receive reports. These ideas are recorded here for future reference, but are not formal recommendations. 30 | 3. The handling and maintenance of confidential information regarding reporters and those who have been reported on is a weighty responsibility. Recordkeeping and transfer of records has been uneven and involves reliance on oral history. Paper files have been lost in the mail, including reports that identify individuals whose past actions merit continued attention to their patterns of behavior, or potentially being limited in their community participation. The 2022 CSS has no specific recommendations for changes at this time, but acknowledges it as an ongoing concern. 31 | 32 | Submitted by Anne Slaughter 33 | -------------------------------------------------------------------------------- /code_of_conduct.md: -------------------------------------------------------------------------------- 1 | CodeOfConduct4Lib 2 | ================= 3 | 4 | [![CC0](http://i.creativecommons.org/p/zero/1.0/80x15.png) Licensed under CC0](http://creativecommons.org/publicdomain/zero/1.0/) 5 | 6 | Short link: 7 | 8 | Code4Lib seeks to provide a welcoming, professionally engaging, fun, and 9 | safe conference (and ongoing community) experience for everyone. We do not 10 | tolerate harassment in any form. Discriminatory language and imagery, 11 | including sexual or sexualized language and imagery, is not appropriate 12 | for any event venue, including talks, or any community channel such as the 13 | chatroom or mailing list. 14 | 15 | Harassment is understood as any behavior that threatens or demeans another 16 | person or group, or that produces an unsafe environment. It includes, but is not limited to, 17 | offensive verbal comments or non-verbal expressions related to gender, gender 18 | identity, gender expression, sexual orientation, disability, physical 19 | appearance, body size, race, ethnicity, age, religious or political beliefs; sexual, 20 | sexualized, or discriminatory images in public (including online) spaces; 21 | deliberate intimidation, stalking, or following; harassing photography or 22 | recording; sustained disruption of talks or other events; inappropriate physical 23 | contact; and unwelcome sexual attention. 24 | 25 | ## Conflict Resolution 26 | 27 | 1. Initial Incident 28 | 29 | If you are being harassed, notice that someone else is being harassed, 30 | or have any other concerns, __and you feel comfortable speaking with 31 | the offender__, please inform the offender that they have affected you 32 | negatively. The offending behavior may be unintentional, and the 33 | offender and offended may resolve the incident by having that initial 34 | discussion themselves. 35 | 36 | Code4Lib understands that there are many reasons speaking directly to 37 | the offender may not be workable for you (including but not limited to 38 | unfamiliarity with the conference or its participants, [lack of spoons](https://web.archive.org/web/20191117210039/https://butyoudontlooksick.com/articles/written-by-christine/the-spoon-theory/), 39 | or concerns for personal safety). If you do not feel comfortable 40 | speaking directly with the offender for any reason, skip straight to 41 | step 2. 42 | 43 | 2. Escalation 44 | 45 | If the offender insists that they did not offend, if the offender is 46 | actively harassing you, or if direct engagement is not a good option 47 | for you at this time, then you will need a third party to step in. 48 | 49 | If you are at a conference or other community event, 50 | find the on-call [Community Support Volunteer](csvcharge.md) or the event organizer or 51 | staff person, who should be listed on a publicly-accessible website such as the 52 | conference website, [in the Community Support Squad volunteers list](css_volunteers.md), 53 | or [on the Code4Lib wiki](http://wiki.code4lib.org/index.php/Main_Page). 54 | If you can't find either any such people, there will be other staff 55 | available to help if the situation calls for immediate action. 56 | 57 | The primary way to reach a Community Support Volunteer online is to email 58 | the `c4lcommunitysupport@googlegroups.com` address. Messages sent to the CSV list are 59 | visible to all Community Support Volunteers and are kept private. You may 60 | use a throw-away email address if you want to ensure anonymity. 61 | 62 | If you are in the #code4lib IRC channel, the people 63 | designated as channel helpers is `@css`. There is at least one helper 64 | in the channel at most times. Helpers may not be Community Support 65 | Volunteers but know how to direct you to them. 66 | 67 | If you are in the code4lib Slack, you may reach a volunteer by including 68 | either the phrase `c4lcsv` or `c4lcss` in a message posted to a public 69 | channel, such as `#general` or `#code4libcon`. You may also private message 70 | a known member of the Community Support Squad; their names and Slack handles 71 | will be posted on the aforementioned publicly-accessible website(s). 72 | 73 | If you are in the code4lib Discord server, contact anyone who is assigned 74 | the `@community_support_volunteers` role. Those who are designated that role 75 | will have a green highlighted user name. For those who may not be able to see 76 | the color, you will know if someone is a community support volunteer by 77 | clicking on their name/profile and `@community_support_volunteers` will be 78 | listed under roles. On the desktop Discord client you can see a list of 79 | those in this role in the upper right corner. 80 | 81 | The [code4lib listserv](https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB) is 82 | maintained by [Eric Lease Morgan](http://www3.nd.edu/~emorgan/). Our 83 | [Community Support Volunteers](css_volunteers.md) monitor its messages and 84 | may be contacted [via email](mailto:c4lcommunitysupport@googlegroups.com). 85 | 86 | 3. Wider community response to Incident: 87 | 88 | If the incident doesn't pass the first step (discussion reveals offense 89 | was unintentional, apologies offered and accepted, public note or 90 | community is informed of resolution), then there's not much the community 91 | can do at this point since the incident was resolved without outside 92 | intervention. 93 | 94 | If incident results in corrective action, the community should support 95 | the decision made by the Help in Step 2 if they choose corrective action, 96 | like ending a talk early or banning from the listserv, as well as 97 | support those harmed by the incident, either publicly or privately 98 | (whatever individuals are comfortable with). 99 | 100 | If the Help in Step 2 runs into issues implementing the CoC, then the 101 | Help should come to the community with these issues and the community 102 | should revise the CoC as they see fit. 103 | 104 | In Real Life, people will have opinions about how the CoC is enforced. 105 | People will argue that a particular decision was unfair, and others will 106 | say that it didn't go far enough. We wouldn't dream of asking people to 107 | stop people sharing their opinions, but we can steer discussions toward 108 | civil, constructive dialogue that leads to something tangible (e.g., 109 | affirmation of decision, change to the CoC, modification of the decision). 110 | 111 | ## Sanctions 112 | 113 | Participants asked to stop any harassing behavior are expected to comply 114 | immediately. If a participant engages in harassing behavior, organizers may 115 | take any action they deem appropriate, including warning the offender, 116 | expelling the offender from the Code4Lib event, or banning the offender from 117 | a chatroom, Slack workspace, or mailing list. 118 | 119 | Specific sanctions may include but are not limited to: 120 | 121 | * warning the offender to cease their behavior, letting them know that 122 | further reports will result in other sanctions 123 | * requiring the offender to avoid any interaction with, or physical 124 | proximity to, the victim for the remainder of the event 125 | * terminating a talk 126 | * refusing to publish video and/or slides of a talk 127 | * barring a speaker from giving (further) talks at the event 128 | * immediately ending any event volunteer responsibilities and privileges the 129 | offender holds, including requiring that the offender not be allowed to 130 | volunteer for future Code4lib events (either indefinitely or for a specified time period) 131 | * requiring that the offender immediately leave an event and not return 132 | * banning the offender from future events (either indefinitely or for a 133 | specified time period) 134 | * banning the offender from any (or all) online Code4Lib channels 135 | * publishing an account of the harassment 136 | 137 | Code4Lib event organizers can be identified by their name badges, and they will 138 | help participants contact hotel/venue security or local law enforcement, 139 | provide escorts, or otherwise assist those experiencing harassment to feel 140 | safe for the duration of the event. 141 | 142 | In the case of organized events, those responsible for the event should make readily available the following information: 143 | 144 | * **Conference organizer:** [ORGANIZER NAME], [PHONE NUMBER] 145 | * **[CONFERENCE HOTEL NAME]:** [PHONE NUMBER] 146 | * **[MUNICIPALITY] Police Department**: [PHONE NUMBER] 147 | * **[LOCAL SEXUAL ASSAULT/CRISIS LINE]:** [PHONE NUMBER] 148 | * **[TAXI COMPANY NAME]:** [PHONE NUMBER] 149 | * **Community Support Volunteers:** including the [PHONE NUMBER] 150 | * **Code4lib Slack volunteers:** `@css` in any channel 151 | 152 | We expect participants to follow these rules at all conference venues, 153 | conference-related social events, community gatherings, and online 154 | communication channels. 155 | 156 | We value everyone's participation in the Code4Lib community, and will all 157 | work to keep Code4Lib a safe and friendly space for all participants! 158 | 159 | *Based on the [example policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment) 160 | from the [Geek Feminism wiki](http://geekfeminism.wikia.com/), created by the 161 | Ada Initiative and other volunteers.* 162 | -------------------------------------------------------------------------------- /procedures.md: -------------------------------------------------------------------------------- 1 | # Procedures for reporting and responding to violations of Code of Conduct 2 | 3 | A code of conduct matters as a statement of values. Ultimately, however, it is only as good as its enforcement procedures. This procedure documents actions to be taken by [Code4Lib](https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md) conference staff and volunteers in the event of a violation of the Code of Conduct. These activities will be led by the [Community Support Squad.](csvcharge.md) 4 | 5 | ### How to Report 6 | 7 | If you witness, suspect, or are the target of a violation of the code of conduct, contact a community support volunteer as soon as possible by emailing [c4lcommunitysupport@googlegroups.com](mailto:c4lcommunitysupport@googlegroups.com). All complaints will be taken seriously and kept confidential. 8 | 9 | ### Taking reports 10 | 11 | Upon receiving a report of a code of conduct violation, ask the reporter if they would like to make a formal report. Let them know that you can’t make any promises about how it will be handled, but their safety and confidentiality will be a priority. Take a written report, or write down verbal reports as soon as possible. Reports of any length should be taken in a quiet, private space (not a volunteer's hotel room). If the following information is not volunteered in the written or verbal report, ask for it/include it, but do not pressure them. 12 | 13 | * Identifying information (name if possible) of the participant doing the harassing 14 | * Reporter’s name and contact information 15 | * The approximate time and date of the behavior (if different than the time the report was made) 16 | * Place of the incident 17 | * What happened (try to collect as much information as possible to provide a clear understanding of what occured) 18 | * Other people involved in the incident 19 | 20 | Do not question the reporter's truthfulness. It is your job to maintain a supportive environment and ensure that fair procedures are followed, not to conduct an investigation. Do not summon law enforcement unless there is a threat to physical safety, or at the request of the reporter (see Threats to physical safety, below). 21 | 22 | If the reporter is distressed and/or needs additional assistance, offer them a private space to be in, ask how you can help, and make sure they have local emergency contact information. Ask if there is a trusted friend they would like you to get; if so, have someone bring that person. 23 | 24 | If the incident was widely witnessed: Thank them for the report and tell them you will convene the committee (and possibly other relevant conference volunteers). 25 | 26 | If the incident was private: Thank them for the report and say you will convene the relevant conference staff if that is okay with them. Consent is critical. Be explicit as to who will fall into that category to the reporter, including other volunteers. 27 | 28 | Do not: 29 | 30 | * Pressure them to withdraw the complaint 31 | * Ask for their advice on handling the complaint or imposing penalties. This is the committee's responsibility 32 | * Share details of the incident with anyone, _including the committee and/or other conference volunteers, without the specific consent of the reporter._ 33 | 34 | Be aware that people who have experienced harassment and abuse may be re-traumatized if the details become public. In addition, abusers may recognize these details, even if they have been anonymized, become angry at the reporter, and enact further trauma. Again, confidentiality and consent are incredibly important 35 | 36 | ## Threats to physical safety and law enforcement 37 | 38 | If you have any concerns as to anyone's physical safety, contact venue security or local law enforcement immediately. 39 | 40 | Do not involve law enforcement under any other circumstances except by request of the reporter. Remember that some attendees will experience law enforcement as increasing, not diminishing, threats to their safety, so it is very important that they be in control of this choice. 41 | 42 | If escalation leads to a harasser being required to leave the conference, and they refuse to leave, it may be necessary to involve hotel staff or law enforcement as a last resort. 43 | 44 | ### Recusal process 45 | 46 | Conflicts of interest may include relationships of the following nature with either party: 47 | 48 | * Close friendships 49 | * Business partnerships 50 | * Romantic relationships 51 | * Family relationships 52 | * Hierarchical academic or business relationships 53 | * Any other significant power relationship 54 | * Significant personal conflict 55 | * Involvement in the incident 56 | 57 | If you think the nature of your relationship with either party is such that you would be significantly biased for or against them, or if you would be in a position to retaliate against or receive retaliation from either party depending on the outcome, you should recuse yourself. Additionally, if the nature of your relationship is such that outside people might reasonably perceive a conflict of interest, you should recuse yourself. 58 | 59 | It is not necessary to recuse yourself on the basis of having been present at a public violation under discussion, or on the basis of the sort of general friendships and acquaintanceships which many people share in professional spaces. 60 | 61 | Recusing yourself means you should stop influencing the decision in any way. Don’t participate in the discussion, and don’t discuss the decision with others (including other staff), read or write the documentation, etc. If there are email threads, group chats, etc., leave them if possible (and if you haven’t recused yourself, don’t include people who are recused in these group communications). 62 | 63 | ## Responding to Reports 64 | 65 | Send the report immediately to the committee using established private communication channels, and/or convene a meeting (physical or virtual) as soon as possible. Do let the alleged harasser know that a complaint has been lodged (reread the language above about confidentiality and consent first). Volunteer conference staff are not in a position to conduct exhaustive investigations, so don't. It may be necessary and prudent to gather some additional information before reaching a decision, however. 66 | 67 | At the meeting, discuss: 68 | 69 | * What happened? 70 | * Are you doing anything about it? 71 | * If so, who is doing it? 72 | * When will they do it? 73 | 74 | Specific sanctions may include but are not limited to: 75 | 76 | * warning the harasser to cease their behavior and that any further reports will result in other sanctions 77 | * requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event 78 | * early termination of a talk that violates the policy 79 | * not publishing the video or slides of a talk that violated the policy 80 | * not allowing a speaker who violated the policy to give (further) talks at the event 81 | * immediately ending any event volunteer responsibilities and privileges the harasser holds requiring that the harasser not volunteer for future Code4lib events (either indefinitely or for a certain time period) 82 | * requiring that the harasser immediately leave the event and not return 83 | * banning the harasser from future events (either indefinitely or for a certain time period) 84 | * publishing an account of the harassment 85 | 86 | Keep in mind that it is never a good idea to require an apology. If a harasser would like to apologize, this may also be a bad idea. Do not include the reporter, the alleged harasser, or anyone with a conflict of interest at this meeting. 87 | 88 | If there is no consensus in the group on a response, the coordinators will determine and communicate the course of action. 89 | 90 | Violations that have been reported second hand, not by the target of the violation, should be handled on a case by case basis. Keep an eye on those involved in the report and, if need be, approach the affected parties. 91 | 92 | ## Communications 93 | 94 | Coordinators will determine whether private (not widely witnessed) incidents need to be addressed with the community. Widely witnessed incidents should be addressed with the community. 95 | 96 | ### Involved Parties 97 | 98 | As soon as possible after the meeting, communicate your decision and any actions you are taking to involved parties. 99 | 100 | When meeting with someone accused of harassment, follow the Rule of Two - have two volunteers in the room. Any more than two might be viewed as piling on the person, any less than two is a safety concern. 101 | 102 | ### The community at large 103 | 104 | First, reread the language above about confidentiality and consent, and consider this section in that light. 105 | 106 | * Do respond quickly 107 | * Do keep individuals on both sides of an incident anonymous. (Potential exceptions: when a harasser is a conference staffer; when the incident was public and high-profile.) 108 | * Do provide a general sense of the nature of the incident. 109 | * Do say what you have done in response to the incident. 110 | * You may briefly note any steps taken by harassers to remedy the situation (e.g. apology, leaving the conference). Don't give them a cookie for it. 111 | * Do provide avenues for community feedback to conference staff. This feedback should be private. If you provide only one feedback mechanism, make sure it is accessible to everyone (e.g. email good, in-person conversations bad). 112 | * Do reiterate your values. 113 | 114 | Your goal is to be transparent about your process and values while respecting the privacy of individuals involved. Keep it brief and clear. There will probably be upset community members who want to talk. Conference staff should listen to them nonjudgmentally, take notes if needed, thank them for their feedback, and not flip into problem-solving or explaining mode. Apologize as needed; avoid defensiveness. 115 | 116 | ### After the conference 117 | 118 | If someone's conduct was egregious enough that they should be banned or otherwise sanctioned in future years, this needs to be recorded and communicated to future committees. 119 | 120 | * The Local Planning Committee chairs are responsible for obtaining records of incidents from previous years conference organizers. 121 | * Local Planning Committee chairs have the responsibility to store records securely, to disseminate as-needed in the course of organizing the event, and to update as needed. 122 | * Local Planning Committee chairs are responsible for ensuring that anyone to whom the records are disclosed are aware of this document, aware of the privacy policy regarding the records, and are not themselves associated with any records in a way that could create a breach of privacy. 123 | 124 | If your responses to a conference incident need to continue after the conference, the Local Planning committee chairs are responsible for ensuring the continued response. 125 | 126 | ## Credits and further reading 127 | 128 | * “Recusal process” section taken from 2018 Proposed LITA Code of Conduct Manual 129 | * [http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/) 130 | and subpages 131 | * [https://frameshiftconsulting.com/code-of-conduct-book/](https://frameshiftconsulting.com/code-of-conduct-book/) 132 | * [https://www.writethedocs.org/code-of-conduct-reporting/](https://www.writethedocs.org/code-of-conduct-reporting/) 133 | * [http://safetyfirstpdx.org/resources/](http://safetyfirstpdx.org/resources/) 134 | 135 | 136 | --------------------------------------------------------------------------------