-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Improvements to Docs for new contributors #19344
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're installing the editable
local version, should we also mention something about it?
doc/devel/contributing.rst
Outdated
|
||
4. Create a branch to hold your changes:: | ||
cd matplotlib | ||
pip install -ve . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pip install -ve . | |
pip install -ve . | |
NOTE: `-e` flag would make your installation 'editable', such that your work is always | |
in sync as the installed version. For more details see [ref](https://pip.pypa.io/en/stable/reference/pip_install/#install-editable). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this resolved by entirely deferring this to the standalone dev install page
doc/devel/contributing.rst
Outdated
4. Enter the directory and install the local version of Matplotlib. For more | ||
detailed instructions on doing this see ref`<installing_for_devs>`:: | ||
|
||
4. Create a branch to hold your changes:: | ||
cd matplotlib | ||
pip install -ve . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only half the truth. It's important to set up a dedicated environment (venv or conda) for development and do the editable install there. Otherwise people will corrupt their standard python environment.
I suggest not giving any details here but completely deferring to :ref:`installing_for_devs`
.
Thank you for the reviews - I think I have address all of them. And sorry for the two week wait, it's amazing how a few emails can really make quite a lot of work materialize :P |
I think the doc failures are unrelated:
|
If you rebase, it will fix that docs problem. |
+ Reword contributing opening paragraph Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
also remove the $ as they make it more difficult for readers to copy paste link to more detailed dev install instructions only link to install page in brief set up docs.
it seems to pair well with the contributor incubator part, and it was somewhat hard to notice where it used to be.
Less mental effort to read this, as no time spent thinking about how different your versions are.
It's super easy to click on that link and then get bogged down in details rather than read the short guide that follows that paragraph.
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
Thanks @ianhi! |
PR Summary
At least I think they are improvements. I tried to go through the process as if I didn't know and was starting by clicking the contributing tab. These changes address the areas where I felt I would have gotten stuck or knocked off course.
See also: https://discourse.matplotlib.org/t/contributor-onboarding-retention/21714
I tried to make granular commits and leave explanations in the body of the commit messages.
PR Checklist
flake8
on changed files to check).