view release on metacpan or  search on metacpan

CODE_OF_CONDUCT.md  view on Meta::CPAN

representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
jmaslak@antelope.net.
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series
of actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

CONTRIBUTING  view on Meta::CPAN

  * If you make suggestions/changes, I'll credit you unless you ask
    specifically otherwise.  I'll use your email and PAUSE ID (if
    applicable) if I can find it.  If I get this wrong or you change
    either, just jot me a note or PR to change it.

Some things you can do that would make me smile:

  * Feel free to look at the TODO file - I've pointed out some things I
    want to do with the module.  Feel free to do any of them (but if it
    is a bigger item, you might jot me a note first so that I don't
    accidentally duplicate your effort!)
  * Write tests for things that are known to be broken.  Mark those as
    "todo" tests so that the failures do not cause build failures.
  * Improvements to documentation are always appreciated
  * If the module is missing something you would find useful, or you're
    confused about something, or if it doesn't seem to work the way you
    want, email me or open a Github issue.  The module makes sense to me
    and my way of working, but if it doesn't to you, you probably are
    not the only person who it doesn't make sense to.
  * "Meta" stuff is great too - I'm no expert on Dist::Zilla and all
    that it can/should do.  So please feel free to send me suggestions