Re: SPI member projects adopting a Code of Conduct

Hi Peter,
SMC adopted a CoC a few years ago, based on Contributor Covenant

https://smc.org.in/code-of-conduct

Enforcement side, All free and open source communities have limitations as
Joshua pointed before.

Anivar

On Tue, Oct 13, 2020 at 8:33 AM Matthew Ahrens <matt(at)mahrens(dot)org> wrote:

> 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
>>
> _______________________________________________
> Spi-general mailing list
> Spi-general(at)lists(dot)spi-inc(dot)org
> http://lists.spi-inc.org/listinfo/spi-general
>