PC::PerlCoders
Search About Submit a question GitHub

Applies to every channel we operate

Argue with the claim, not with the person.

This applies to GitHub Discussions and Issues, pull requests, comment threads, submissions through the contribute forms, and any correspondence with the editors.

What is expected

  • Be specific. Name the page, the claim and the source. “This is wrong” is not a correction; it is a mood.
  • Assume the other person read the same documentation and reached a different conclusion. Usually they did.
  • Separate the technical disagreement from the person holding it. Language choice is not a moral position, and people who choose differently are not the enemy.
  • Accept a correction the way you would want yours accepted. Including ours — several pages on this site say “unverified” precisely so they can be corrected.

What is not tolerated

  • Personal attacks, harassment, or sustained hostility toward an individual.
  • Demeaning remarks based on someone’s identity, background, experience level or first language.
  • Publishing someone’s private information, or material identifying a person, without their consent.
  • Deliberate derailment: reframing a technical thread as a fight about the language’s worth, on either side.
  • Submitting material you have no right to submit, or misrepresenting its provenance.
On language advocacy specifically Perl attracts both dismissal and defensiveness, and both make threads useless. A comment whose content is that Perl is dead, or that its critics are ignorant, adds nothing either way and will be treated the same in both directions.

Reporting

Report a problem through the contact form, marking it as a conduct report. Reports go to the editors and are not published. If the report concerns an editor, say so in the message and it will be handled by someone else.

Tell us what happened, where, and what outcome you want. You will get an acknowledgement, and a decision as quickly as a small team can reach one.

What happens next

  1. Clarification. Most reports are a misread thread and end here.
  2. Private warning. A description of the behaviour and what must change.
  3. Temporary suspension from the channel where it happened.
  4. Permanent removal from every channel we operate.

We do not publish the details of individual reports. Aggregate policy changes that follow from one are noted in Pulse.

Scope

This covers the spaces we operate. It does not extend to unrelated conduct elsewhere, with one exception: behaviour that makes someone unsafe in our spaces is in scope regardless of where it originated.