-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
[Doc]: Improve contribute instructions #28005
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
Comments
Generally I've been working on the assumption that contribute.rst is the guide for absolute beginners, and devolpment_workflow.rst is for more experienced folks, so hopefully written slightly differently for both. |
I‘d rather phrase this as: contribute.rst is the first point of contact and a high-level overview directing people to the more detailed instuctions, and development_workflow.rst is one such instruction. |
Yeah, I think both are ways of describing |
Partially adresses matplotlib#28005. The two sections "Report a bug" and "Request a feature" were burried inside of contribute.rst. They were a bit foreign there because all other content is on direct involvement with the project, which needs much more information. To keep things focussed and directly redirect the "simple" bug report and feature request topics to GitHub, I've deleted the sections and instead created two cards at the top of devel/index.rst with essentially the content of the sections. Note that I've the list of things to include in bug reports because that's covered by our issue template on GitHub nowadays and does not need repetition here.
Partially adresses matplotlib#28005. The two sections "Report a bug" and "Request a feature" were burried inside of contribute.rst. They were a bit foreign there because all other content is on direct involvement with the project, which needs much more information. To keep things focussed and directly redirect the "simple" bug report and feature request topics to GitHub, I've deleted the sections and instead created two cards at the top of devel/index.rst with essentially the content of the sections. Note that I've the list of things to include in bug reports because that's covered by our issue template on GitHub nowadays and does not need repetition here.
Partially adresses matplotlib#28005. The two sections "Report a bug" and "Request a feature" were burried inside of contribute.rst. They were a bit foreign there because all other content is on direct involvement with the project, which needs much more information. To keep things focussed and directly redirect the "simple" bug report and feature request topics to GitHub, I've deleted the sections and instead created two cards at the top of devel/index.rst with essentially the content of the sections. Note that I've the list of things to include in bug reports because that's covered by our issue template on GitHub nowadays and does not need repetition here. Co-authored-by: hannah <[email protected]>
Partially adresses matplotlib#28005. The two sections "Report a bug" and "Request a feature" were burried inside of contribute.rst. They were a bit foreign there because all other content is on direct involvement with the project, which needs much more information. To keep things focussed and directly redirect the "simple" bug report and feature request topics to GitHub, I've deleted the sections and instead created two cards at the top of devel/index.rst with essentially the content of the sections. Note that I've the list of things to include in bug reports because that's covered by our issue template on GitHub nowadays and does not need repetition here. Co-authored-by: hannah <[email protected]>
Partially adresses matplotlib#28005. The two sections "Report a bug" and "Request a feature" were burried inside of contribute.rst. They were a bit foreign there because all other content is on direct involvement with the project, which needs much more information. To keep things focussed and directly redirect the "simple" bug report and feature request topics to GitHub, I've deleted the sections and instead created two cards at the top of devel/index.rst with essentially the content of the sections. Note that I've the list of things to include in bug reports because that's covered by our issue template on GitHub nowadays and does not need repetition here. Co-authored-by: hannah <[email protected]>
I can't replicate this, so which browser are you on and which version of the docs? |
Doc version - 3.8.4, 3.8.3 |
Ugh still can't replicate :/ have you cleared/ can you clear your cache? |
Please post this link. |
In iOS Safari, if I "open in background" (equivalent to open in new tab in most browsers) the link always takes me to the top of the page. Are you doing something like that @Impaler343? |
@rcomer What is the link target? If it is correct, IMHO then the browser is acting funny and we cannot do anything about it. |
Yes, I always assumed this was a browser issue. If I just tap the link, I get to the right place. |
|
I don't have Safari but when I try to open in a new tab, I the problem still persists |
Just tried this, didn't work 🥲 |
Just checked and works well on safari, must be a browser issue on all the other ones. |
Documentation Link
https://matplotlib.org/devdocs/devel/index.html
Problem / Suggested improvement
Check section order and hierarchy. E.g.
https://matplotlib.org/devdocs/devel/contribute.html#good-first-issues And
https://matplotlib.org/devdocs/devel/contribute.html#work-on-an-issue
Are subsections in „get connected“
https://matplotlib.org/devdocs/devel/contribute.html#work-on-an-issue should be written more with absolute newcomers in mind.
The text was updated successfully, but these errors were encountered: