matplotlib / governance

The governance process and model for matplotlib

Matplotlib is a comprehensive library for creating static, animated, and interactive visualizations in Python.

Check out our home page for more information.

Matplotlib produces publication-quality figures in a variety of hardcopy formats and interactive environments across platforms. Matplotlib can be used in Python scripts, Python/IPython shells, web application servers, and various graphical user interface toolkits.

Install

See the install documentation, which is generated from /doc/install/index.rst

Contribute

You've discovered a bug or something else you want to change — excellent!

You've worked out a way to fix it — even better!

You want to tell us about it — best of all!

Start at the contributing guide!

Contact

Discourse is the discussion forum for general questions and discussions and our recommended starting point.

Our active mailing lists (which are mirrored on Discourse) are:

• Users mailing list: [email protected]
• Announcement mailing list: [email protected]
• Development mailing list: [email protected]

Gitter is for coordinating development and asking questions directly related to contributing to matplotlib.

Citing Matplotlib

If Matplotlib contributes to a project that leads to publication, please acknowledge this by citing Matplotlib.

A ready-made citation entry is available.

governance's Issues

Inconsistent wording "lead"/"leader"

The text is inconsistent in the usage of the two words. At least at the heading level this should be harmonized (right now there's "Project Lead", "Deputy Project Leaders", "Project Specific Leads". I can do a PR to fix it either way, but I'll let native speakers decide on which word to prefer.

Remove pydata theme pin for 3.6

Update code of conduct

We should probably pick one of the following as a starting point:

• JupyterDay
• Scipy
• PyCon

These are all fairly geared toward in-person interactions (though not exclusively by any means). One more appropriate perhaps for online interactions is:

• Python Community Code of Conduct

Communication Guide: Self Promotion

Update the comms guide with a clear policy about self-promotional posts. This needs to be resolved in terms of the blog - mpl content versus advert. Also include job post guidelines from Jan 2020 meeting notes

Policy for advertising jobs on mailing list/discourse/twitter/etc
- matplotlib jobs are always acceptable
- jobs advertised by core devs on a case by case basis
- jobs advertised by other scipy stack projects are allowed for reciprocity

Move the communication guidelines to the (future) development guide repo

waiting on matplotlib/matplotlib#22866

It is simpler if all of the content in this repo is content that requires sign off from a majority of the steering council to change.

We want to be more agile/have less ceremony on the communication guidelines.