Skip to content

DOC: change wording on new contributor path #29377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 23, 2024
Merged

DOC: change wording on new contributor path #29377

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a4e3ad6
DOC: change wording on new contributor path
tacaswell Dec 23, 2024
a0e476f
DOC: use emdash rather than relying on sphinx to translate
tacaswell Dec 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions doc/devel/contribute.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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:

Expand Down
Loading