Hi Code4Lib,

A final followup: the proposed "How Changes are Made to the Code4Lib Code
of Conduct
procedure was approved by a (unanimous) community vote. Thank you to
everyone who voted or participated in discussions about it! The Community
Support Squad will begin reviewing outstanding pull requests on the Code of
Conduct repository shortly.


On Thu, Jul 16, 2020 at 12:34 PM Eric Phetteplace <[log in to unmask]>

> Hi Code4Lib,
> It has been more than two weeks since I originally sought comments on the Code
> of Conduct <> changes
> procedure mentioned in my last email. Since there were no alterations to
> the procedure suggested, I opened a community vote on the topic:
> The vote will run two weeks until Thursday, July 30th. There is no
> eligibility for voting and email addresses are recorded only to prevent
> duplication. Data will be erased afterwards. A simple majority can approve
> the procedure, and as always please send your questions to the Community
> Support Squad at [log in to unmask] or by messaging
> myself (@phette23) or Natasha (@natasha) on Slack.
> Sincerely,
> Your Community Support Squad Coordinators
> Natasha Allen
> Eric Phetteplace
> On Wed, Jul 1, 2020 at 7:47 AM Eric Phetteplace <[log in to unmask]>
> wrote:
>> 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
>> <>. 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
>> <>
>> 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
>> <>.
>> 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:
>> Sincerely,
>> Your Community Support Squad Coordinators
>> Natasha Allen
>> Eric Phetteplace