From: | Matthew Ahrens <matt(at)mahrens(dot)org> |
---|---|
To: | Peter Cock <p(dot)j(dot)a(dot)cock(at)googlemail(dot)com> |
Cc: | spi-general(at)lists(dot)spi-inc(dot)org, OBF Board <board(at)open-bio(dot)org> |
Subject: | Re: SPI member projects adopting a Code of Conduct |
Date: | 2020-10-13 03:02:33 |
Message-ID: | CAKUb7ivNMu5mt3Z8L33dxXkNX6XHbtwuYiD4HS81uMpA8j75Gw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
Hi Peter. OpenZFS adopted a CoC <https://openzfs.org/wiki/Code_of_Conduct>
a few years ago. I'm not sure I have any specific advice, but I'd be happy
to (privately) share our experience if you'd like.
--matt
On Mon, Oct 12, 2020 at 10:58 AM Peter Cock <p(dot)j(dot)a(dot)cock(at)googlemail(dot)com>
wrote:
> Dear SPI projects,
>
> The OBF is an SPI member project, and is currently in the process of
> adopting a Code of Conduct (CoC) to cover both our online activities
> (including software development) and in person events (like our annual
> conference, assuming that resumes as a physical event).
>
> If legal assistance were required (e.g. in handling a specific CoC
> incident), I presume as per https://www.spi-inc.org/projects/services/
> the OBF would at the SPI board's discretion have access to the SPI's
> legal counsel? Is that correct?
>
> If any other SPI projects have themselves adopted a CoC, do you have
> any advice to share? Our concerns include scope and procedures, and
> providing training for those handling reports.
>
> Thank you,
>
> Peter
> Peter Cock, current OBF president.
> _______________________________________________
> Spi-general mailing list
> Spi-general(at)lists(dot)spi-inc(dot)org
> http://lists.spi-inc.org/listinfo/spi-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Anivar Aravind | 2020-10-13 09:37:11 | Re: SPI member projects adopting a Code of Conduct |
Previous Message | Joshua Drake | 2020-10-12 19:33:06 | Re: SPI member projects adopting a Code of Conduct |