From a4e3ad6382320b26b49d25ffb3c284eb3c406f84 Mon Sep 17 00:00:00 2001 From: Thomas A Caswell Date: Mon, 23 Dec 2024 13:14:04 -0500 Subject: [PATCH 1/2] DOC: change wording on new contributor path --- doc/devel/contribute.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/devel/contribute.rst b/doc/devel/contribute.rst index 8360468235c0..f57d2b1486e6 100644 --- a/doc/devel/contribute.rst +++ b/doc/devel/contribute.rst @@ -203,10 +203,11 @@ why they are the correct approach and an improvement to the current state. New contributors ================ -There is no pre-defined pathway for new contributors - we recommend looking at -existing issue and pull request discussions, and following the conversations -during pull request reviews to get context. Or you can deep-dive into a subset -of the code-base to understand what is going on. +Everyone comes to the project from a different place -- in terms of experience +and interest -- so there is no one-size-fits-all path to getting involved. We +recommend looking at existing issue or pull request discussions, and following +the conversations during pull request reviews to get context. Or you can +deep-dive into a subset of the code-base to understand what is going on. .. _new_contributors_meeting: From a0e476fb878f51ed683aba6344dfb4e5f96f4ced Mon Sep 17 00:00:00 2001 From: Thomas A Caswell Date: Mon, 23 Dec 2024 14:54:33 -0500 Subject: [PATCH 2/2] DOC: use emdash rather than relying on sphinx to translate --- doc/devel/contribute.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/devel/contribute.rst b/doc/devel/contribute.rst index f57d2b1486e6..558e19790d82 100644 --- a/doc/devel/contribute.rst +++ b/doc/devel/contribute.rst @@ -40,7 +40,7 @@ Ways to contribute visualization, 3D plotting, design, technical writing, statistics, or some other field where Matplotlib could be improved.** - Awesome -- you have a focus on a specific application and domain and can + Awesome — you have a focus on a specific application and domain and can start there. In this case, maintainers can help you figure out the best implementation; open an issue or pull request with a starting point, and we'll be happy to discuss technical approaches. @@ -203,8 +203,8 @@ why they are the correct approach and an improvement to the current state. New contributors ================ -Everyone comes to the project from a different place -- in terms of experience -and interest -- so there is no one-size-fits-all path to getting involved. We +Everyone comes to the project from a different place — in terms of experience +and interest — so there is no one-size-fits-all path to getting involved. We recommend looking at existing issue or pull request discussions, and following the conversations during pull request reviews to get context. Or you can deep-dive into a subset of the code-base to understand what is going on.