Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC correct some typo in bug_triaging.rst #19032

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 17, 2020
Merged

DOC correct some typo in bug_triaging.rst #19032

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d903cf9
DOC: fix spelling in bug_triage page
tacaswell Dec 17, 2020
f7bfc63
DOC: straighten rst headers
tacaswell Dec 17, 2020
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
12 changes: 6 additions & 6 deletions doc/developers/bug_triaging.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
.. _bug_triaging:

Bug triaging and issue curation
================================
===============================

The `issue tracker <https://github.com/scikit-learn/scikit-learn/issues>`_
is important to the communication in the project: it helps
Expand All @@ -10,7 +10,7 @@ priorities. For this reason, it is important to curate it, adding labels
to issues and closing issues that are not necessary.

Working on issues to improve them
--------------------------------------
---------------------------------

Improving issues increases their chances of being successfully resolved.
Guidelines on submitting good issues can be found :ref:`here
Expand All @@ -36,22 +36,22 @@ The following actions are typically useful:

Online discussions may be harder than it seems at first glance, in
particular given that a person new to open-source may have a very
different understanding of the process than a seasonned maintainer.
different understanding of the process than a seasoned maintainer.

Overall, it is useful to stay positive and assume good will. `The
following article
<http://gael-varoquaux.info/programming/technical-discussions-are-hard-a-few-tips.html>`_
explores how to lead online discussions in the context of open source.

Working on PRs to help review
------------------------------
-----------------------------

Reviewing code is also encouraged. Contributors and users are welcome to
participate to the review process following our :ref:`review guidelines
<code_review>`.

Triaging operations for members of the core and triage teams
-------------------------------------------------------------
------------------------------------------------------------

In addition to the above, members of the core team and the triage team
can do the following important tasks:
Expand Down Expand Up @@ -91,7 +91,7 @@ See the github description for `roles in the organization
should be closed.

A typical workflow for triaging issues
----------------------------------------
--------------------------------------

The following workflow [1]_ is a good way to approach issue triaging:

Expand Down