8000 [MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section. by mohamed-ali · Pull Request #10917 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

[MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section. #10917

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

Merged
merged 4 commits into from
Apr 10, 2018
Merged

[MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section. #10917

merged 4 commits into from
Apr 10, 2018

Conversation

mohamed-ali
Copy link
Contributor

Reference Issues/PRs

--

What does this implement/fix? Explain your changes.

It makes more sense to put Filing bugs subsection under section Submitting bug report instead of section Contributing code

Any other comments?

This will help to resolve issue #10892.

@mohamed-ali mohamed-ali changed the title [MRG] [DOC] Put "filing bugs" under "submitting bug report" [MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section in Apr 4, 2018
@mohamed-ali mohamed-ali changed the title [MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section in [MRG] [DOC] Put "Filing bugs" subsection under "Submitting bug report" section. Apr 4, 2018
Copy link
Member
@lesteve lesteve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small comment

@@ -42,6 +42,46 @@ ticket to the
`Bug Tracker <https://github.com/scikit-learn/scikit-learn/issues>`_. You are
also welcome to post feature requests or pull requests.

.. _filing_bugs:

Filing Bugs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels like there is no real-need for a subsection here. The few lines above can be merged in the same section.

Maybe "Submitting a bug report" is a bit better as a title, but not very important. Do keep the same reference name otherwise, some links somewhere in the world will break (OK not really break but not find any anchor to go to in the page).

@mohamed-ali
Copy link
Contributor Author

@lesteve I was afraid of breaking references, that's why I kept both section and subsection titles. However, having had a second look, I think changing Filing bugs to a question, like How to report bugs can make both section and subsection relevant, where the small paragraph before the subsection would serve as an introduction.

@lesteve
Copy link
Member
lesteve commented Apr 5, 2018

Fair point, so maybe this section should be something along these lines (mostly reusing the existing content):

Submitting a bug report of feature request

  • make sure there is not an issue or PR for this already
  • feature request look at the FAQ for algorithm inclusion
  • bug report, explain that in order to get the best feed-back you are strongly encourage to read and follow the guidelines

How to make a good bug report (title can be improved)

  • ideally a reproducible snippet with full stack-trace if there is an exception. If not possible, put the relevant code with shape of the data etc ...
  • rest of the existing content.

@mohamed-ali
Copy link
Contributor Author

@lesteve Let me know what you think about the last edit. I tried to incorporate what you suggested.

Sorry, something went wrong.

@qinhanmin2014
Copy link
Member

Maybe Ways to contribute should be on the top instead of guideness of submitting issues?

* Move up "Ways to contribute"
* Reorder and add bold in "How to make a good bug report"
@lesteve
Copy link
Member
lesteve commented Apr 10, 2018

I pushed some tweaks, mostly reorganising the content slightly add adding bold to emphasize the important bits. @mohamed-ali and @qinhanmin2014 can you have a quick look?

@lesteve
Copy link
Member
lesteve commented Apr 10, 2018

In general I think the contributing doc could be reorganised further but I would be in favour of merging this PR as is (and possibly continue the work in other PRs). This PR is already a good improvement as I feel we can refer people to this when we want additional information (snippet, versions, formatting improvements, etc ...).

Copy link
Member
@qinhanmin2014 qinhanmin2014 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @mohamed-ali

@qinhanmin2014 qinhanmin2014 merged commit 6233150 into scikit-learn:master Apr 10, 2018
@qinhanmin2014
Copy link
Member

Just as @lesteve points out, I think contributing.html can be further reorganised into several parts: Ways to contribute at the beginning, following with guidance to submit issue, submit PR, review PR, etc.
We might consider moving things like APIs of scikit-learn objects and Rolling your own estimator to a separate page since I suppose it won't be useful for most contributors.

@mohamed-ali mohamed-ali deleted the change-section-of-filing-bugs branch April 10, 2018 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0