Code4lib Anti-Harassment Policy
This is a repository to provide a space to draft and allow for dialog in the creation of an anti-harassment policy for the Code4lib annual conference.
Resources for policies/starting points:
- The Ada Initiative: Anti-harassment work
- Geek Feminism Wiki: example anti-harassment policy for conferences
- howto hack code4lib: don't be sexist/racist/*ist
- CAUT Anti-harassment and Non-Discrimination Statement
- AAI 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.
- How do we cover not only the conference/IRL interactions, but IRC, etc. too?
- Do we require a duty officer explicitly? Is it fair/reasonable/workable to have conference staff be in that role?
Discussion is welcome either on the Code4lib listserv or by creating a new issue: https://github.com/code4lib/antiharassment-policy/issues/new
Using Github (doesn't require knowing Git)
- Fork the codebase e.g. to https://github.com/your-username/antiharassment-policy (click the "Fork" button in the upright corner of the page)
- Click the link for one of the files (e.g.
- Click the Edit button
- Add a commit summary and (optionally) an extended description
- Click the Commit Changes button
- Create a pull request by clicking the Pull Request button at the top of the page
- Fork the codebase e.g. to https://github.com/your-username/antiharassment-policy
- Clone your fork locally (
git clone firstname.lastname@example.org:your-username/antiharassment-policy.git my-antiharassment-policy)
- Create a branch to hold your changes (
git checkout -b my-changes)
- Commit the changes you've made (
git commit -am "Some descriptive text around what you've added")
- Push your branch to github (
git push origin my-changes)
- Create a pull request e.g. at https://github.com/your-username/antiharassment-policy/pull/new/master