Aloha, thank you for bringing this up again.
there were already quite a few comments on the PR at the time, which interested people should have a look at. I also share the concern that this CoC lacks explicitness which is why I also favor a covenant of code based CoC. this is what we created for Symfony. https://symfony.com/doc/current/contributing/code_of_conduct/code_of_conduct.html Since then version 2.0 was released, which I have not studied in detail but afaik it now contains enforcement guidelines https://www.contributor-covenant.org/version/2/0/code_of_conduct/ for Symfony we have created our own (heavily inspired from Sunshine PHP, who in turn were inspired by others): https://symfony.com/doc/current/contributing/code_of_conduct/reporting_guidelines.html Of course it is important that people receiving reports know what they are doing. For Symfony we got a group of people trained by Sage Sharpe: https://symfony.com/doc/current/contributing/code_of_conduct/care_team.html https://otter.technology/code-of-conduct-training/ Semi related to this there is an initiative to create a tool for CoC reporting. The key benefit I see is: 1) proper handling of records 2) ability for anonymous reporting 3) ability for report handlers to be excluded or to recuse 4) ability to collect statistics that could help identify cross community "grey" behavior Note the tool is not yet "production" available. Mostly because there are 3rd party evaluations missing. But this could be an amazing service for the entire PHP community. So to me the key things I would like to have changed: 1) more explicit 2) reporting guidelines 3) trained team to handle reports However I do think this is a step forward, but I feel quite strongly that without 2)/3) we might just offer a solution that will fail affected people when push comes to shove. regards, Lukas On Mon, Jul 20, 2020 at 2:50 AM Larry Garfield <[email protected]> wrote: > Hi folks. > > Last year I proposed a CoC for FIG, based on the Code Manifesto by Graham > Daniels. It was subsequently edited a bit by former FIG Secretary Margaret > Staples. I left it lie for a bit in the hopes that Margaret's changes > would be merged back into the Code Manifesto proper, but that never > happened and then I got distracted by other things and then the world > turned upside down and... yeah. > > So, I'm finally back with take 2, which is really just continuing where > the previous attempt left off. Specifically, this PR: > > https://github.com/php-fig/fig-standards/pull/1143 > > The only change I am still debating myself is whether to include > "lifestyle choice" as one of the forms of discrimination that we're not on > board with. It is a distinction that is important to me (as many know), > but I know that others fear it is too easy to hide jerkish behavior > behind. That said, I'm certain a dedicated jerk could hide behind > absolutely any label if they put their mind to it. Hence my hesitation. > > Since it's been so long I'll consider this a new discussion period of > minimum 2 weeks, with the intent to bring it to a vote shortly thereafter. > > -- > Larry Garfield > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/a6954973-11df-49cf-ad92-5d9c8fb195d1%40www.fastmail.com > . > -- regards, Lukas -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAEFKHaGofSXVPrMN1djpzLuD4tbaaZCXJAgi5f1VKN8ZEhh6Ag%40mail.gmail.com.
