Skip to content

DOC redirect to GitHub issues & PR instead of mailing list when it comes to contribution #30177

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 4 commits into from
Oct 30, 2024
+5 −3
Merged

DOC redirect to GitHub issues & PR instead of mailing list when it comes to contribution #30177

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f50f260
doc(contributing): update contributing to orient toward gh and discor…
MarieSacksick Oct 30, 2024
cd9c1d0
Update doc/developers/contributing.rst
MarieSacksick Oct 30, 2024
126f21a
Update doc/developers/contributing.rst
MarieSacksick Oct 30, 2024
e8c9207
Update doc/developers/contributing.rst
MarieSacksick Oct 30, 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
8 changes: 5 additions & 3 deletions doc/developers/contributing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ There are many ways to contribute to scikit-learn, with the most common ones
being contribution of code or documentation to the project. Improving the
documentation is no less important than improving the library itself. If you
find a typo in the documentation, or have made improvements, do not hesitate to
send an email to the mailing list or preferably submit a GitHub pull request.
create a GitHub issue or preferably submit a GitHub pull request.
Full documentation can be found under the doc/ directory.

But there are many other ways to help. In particular helping to
Expand Down Expand Up @@ -345,8 +345,10 @@ The next steps now describe the process of modifying code and submitting a PR:
12. Follow `these
<https://help.github.com/articles/creating-a-pull-request-from-a-fork>`_
instructions to create a pull request from your fork. This will send an
email to the committers. You may want to consider sending an email to the
mailing list for more visibility.
notification to potential reviewers. You may want to consider sending an message to
the `discord <https://discord.com/invite/h9qyrK8Jc8>`_ in the development
channel for more visibility if your pull request does not receive attention after
a couple of days (instant replies are not guaranteed though).

It is often helpful to keep your local feature branch synchronized with the
latest changes of the main scikit-learn repository:
Expand Down