Acme-Unicodify

 view release on metacpan or  search on metacpan

AUTHOR_PLEDGE  view on Meta::CPAN

# CPAN Covenant for this distribution

I, Joelle Maslak <jmaslak@antelope.net>, hereby give modules@perl.org
permission to grant co-maintainership to this distribution and it's
associated modules if all the following conditions are met:

   (1) I haven't released the module for a year or more
   (2) There are outstanding issues in the module's public bug tracker
   (3) Email to my CPAN email address hasn't been answered after a month
   (4) The requester wants to make worthwhile changes that will benefit CPAN

In the event of my death, then the time-limits in (1) and (3) do not apply.

CODE_OF_CONDUCT.md  view on Meta::CPAN

or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
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.

CODE_OF_CONDUCT.md  view on Meta::CPAN

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

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior,  harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).

CONTRIBUTING  view on Meta::CPAN

Wow, you want to help?  That's great!

If you want to help:

  * Don't change the public interface.  You can add to it, but don't
    break code that already depends on this interface.
  * I'll take bug reports however you want to send them (RT, Github
    issue, email, etc).  My preference is for Github issues.
  * I'll take code changes however you want to send them, but prefer
    it via Github pull request.
  * 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.