Hello Code4Lib Community, We have two major announcements for you. First of all, we are working on a procedure to manage changes to the Code of Conduct repository <https://github.com/code4lib/code-of-conduct>. There are several pull requests that have sat in the repository for years because there is no clear, community-approved method of managing them. We are proposing a new approval method <https://github.com/code4lib/code-of-conduct/blob/changes-procedure/how_changes_are_made.md> which is attached to this email. We want to follow this document's own community vote guidelines: a discussion on the pull request and then a vote held via web form. Please let us know if you have any questions; you can direct comments to us here, on Slack, or on the pull request <https://github.com/code4lib/code-of-conduct/pull/84>.
Secondly, to review proposed changes to the Code of Conduct, we will need Community Support volunteers that are year-round and not scoped to the annual conference. We are still working on the parameters of these volunteer positions but we anticipate they will: be two-year terms, undergo community vetting, attend an initial training, enforce the Code of Conduct in online spaces, and manage change requests once we have a procedure in place. They will not be required to attend the annual conference or volunteer unless desired. If you are interested in the year-round Community Support Volunteer positions, please fill out this form: https://forms.gle/tHrKL6e7x1Ms8HKJ6 Sincerely, Your Community Support Squad Coordinators Natasha Allen Eric Phetteplace
# How Changes are Made to the Code4Lib Code of Conduct 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. 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. 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. 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. 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. 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. 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. In those instances, the CSS conducts a community vote with an accessible, web-based form with the following elements: - respondent email address, used only to deduplicate responses and not visible outside the CSS - the proposed changes - the discussion on GitHub and any additional, relevant resources - an option to approve or reject the changes 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.
