diff --git a/_sources/faq/howto_faq.txt b/_sources/faq/howto_faq.txt index 4015dec0f4a..834d04e6ccc 100644 --- a/_sources/faq/howto_faq.txt +++ b/_sources/faq/howto_faq.txt @@ -491,7 +491,7 @@ Request a new feature Is there a feature you wish matplotlib had? Then ask! The best way to get started is to email the developer `mailing -list `_ for discussion. +list `_ for discussion. This is an open source project developed primarily in the contributors free time, so there is no guarantee that your feature will be added. The *best* way to get the feature @@ -514,7 +514,7 @@ demonstrating what the bug is. Including a clear, easy to test example makes it easy for the developers to evaluate the bug. Expect that the bug reports will be a conversation. If you do not want to register with github, please email bug reports to the `mailing list -`_. +`_. The easiest way to submit patches to matplotlib is through pull diff --git a/_sources/faq/troubleshooting_faq.txt b/_sources/faq/troubleshooting_faq.txt index 5c3f6f29958..9a6e3eab353 100644 --- a/_sources/faq/troubleshooting_faq.txt +++ b/_sources/faq/troubleshooting_faq.txt @@ -78,7 +78,7 @@ There is a good chance your question has already been asked: If you are unable to find an answer to your question through search, please provide the following information in your e-mail to the `mailing list -`_: +`_: * your operating system; (Linux/UNIX users: post the output of ``uname -a``) @@ -154,9 +154,9 @@ simple test script in debug mode:: and post :file:`build.out` and :file:`run.out` to the `matplotlib-devel -`_ +`_ mailing list (please do not post git problems to the `users list -`_). +`_). Of course, you will want to clearly describe your problem, what you are expecting and what you are getting, but often a clean build and