1. A short, top-level summary of the bug. In most cases, this should be 1-2

sentences.

2. A short, self-contained code snippet to reproduce the bug, ideally allowing

a simple copy and paste to reproduce. Please do your best to reduce the code

snippet to the minimum required.

3. The actual outcome of the code snippet

4. The expected outcome of the code snippet

5. The Matplotlib version, Python version and platform that you are using. You

can grab the version with the following commands::

1. `Create an account <https://github.com/join>`_ on

GitHub if you do not already have one.

2. Fork the `project repository

<https://github.com/matplotlib/matplotlib>`__: click on the 'Fork' button

near the top of the page. This creates a copy of the code under your

account on the GitHub server.

3. Clone this copy to your local disk::

4. Create a branch to hold your changes::

5. Work on this copy, on your computer, using Git to do the version

control. When you're done editing e.g., ``lib/matplotlib/collections.py``,

do::

to record your changes in Git, then push them to GitHub with::

Finally, go to the web page of your fork of the Matplotlib repo,

and click 'Pull request' to send your changes to the maintainers for review.

You may want to consider sending an email to the mailing list for more

visibility.

* If your pull request addresses an issue, please use the title to describe

the issue and mention the issue number in the pull request description

to ensure a link is created to the original issue.

* All public methods should have informative docstrings with sample

usage when appropriate. Use the

`numpy docstring standard <https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt>`_

* Formatting should follow `PEP8 recommendation

<https://www.python.org/dev/peps/pep-0008/>`_. You should consider

installing/enabling automatic PEP8 checking in your editor. Part of the

test suite is checking PEP8 compliance, things go smoother if the code is

mostly PEP8 compliant to begin with.

* Each high-level plotting function should have a simple example in

the ``Example`` section of the docstring. This should be as simple as

possible to demonstrate the method. More complex examples should go

in the ``examples`` tree.

* Changes (both new features and bugfixes) should be tested. See

:ref:`testing` for more details.

* Import the following modules using the standard scipy conventions::

* If your change is a major new feature, add an entry to the ``What's new``

section by adding a new file in ``doc/users/whats_new`` (see

:file:`doc/users/whats_new/README` for more information).

* If you change the API in a backward-incompatible way, please

document it in `doc/api/api_changes`, by adding a new file describing your

changes (see :file:`doc/api/api_changes/README` for more information)

* See below for additional points about

:ref:`keyword-argument-processing`, if code in your pull request

does that.

* Code with a good unittest coverage (at least 70%, better 100%), check

with::

* No pyflakes warnings, check with::