Skip to content

Commit f6ca08d

Browse files
authored
Merge pull request #1322 from PrernaSingh587/PrernaSingh587-How-to
Minor 'How to get help' Modification
2 parents f3db927 + 2d79dfe commit f6ca08d

File tree

1 file changed

+11
-15
lines changed

1 file changed

+11
-15
lines changed

src/user/how_to_get_help.rst

Lines changed: 11 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,29 @@
11
How to get help in conda-forge
22
==============================
33

4-
We have three options for communication,
5-
live `chat on gitter <https://gitter.im/conda-forge/conda-forge.github.io>`__,
6-
GitHub issues,
7-
and a `mailing list <https://groups.google.com/forum/#!forum/conda-forge>`__.
8-
Depending on the kind of problem one or the other may be more adequate.
4+
You could connect with us via **Gitter, GitHub Issues or Mailing List**.
5+
We would be happy to hear from you!
96

10-
Live chat on gitter
7+
Gitter
118
-------------------
129

13-
If you don't know the first thing about conda-forge and/or is completely
14-
lost we recommend to get in touch via the chat and our community members will direct
10+
If you are just starting out with conda-forge and/or are completely lost, we recommend to get in touch through `Gitter <https://gitter.im/conda-forge/conda-forge.github.io>`__ and our community members will direct
1511
you to the proper documentation and/or help you via the chat.
1612

1713
GitHub issues
1814
-------------
15+
1916
You can open issues at `staged-recipes <https://github.com/conda-forge/staged-recipes/issues>`__
2017
to request a new package or to report a problem with staged-recipes itself (our port of entry to conda-forge).
2118

2219
Or you can open an issue about a specific package at the package feedstock via
2320
``https://github.com/conda-forge/<PACKAGE-NAME>-feedstock/issues``
2421

25-
When opening issues be sure to:
22+
When opening issues, be sure to:
2623

27-
1. Try a new environment first following conda-forge `install instructions <https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge>`__.
28-
2. Always open a new one when an issue is closed. In the packaging world symptoms may be similar but the causes are usually very different.
29-
3. Fill in the required information. Without the output of `conda list` and `conda info -a` the team cannot debug the problem.
24+
* Try a new environment first following conda-forge `install instructions <https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge>`__.
25+
* Always open a new one when an issue is closed. In the packaging world symptoms may be similar but the causes are usually very different.
26+
* Fill in the required information. Without the output of `conda list` and `conda info -a` the team cannot debug the problem.
3027

3128

3229
You can open issues at `conda-forge.github.io <https://github.com/conda-forge/conda-forge.github.io/issues>`__
@@ -36,7 +33,6 @@ Please note that some of these discussions will be turned into policy via the `C
3633
Mailing list
3734
------------
3835

39-
The mailing list is a secondary home for long threads about the ecosystem.
36+
You can subscribe to our `Mailing List <https://groups.google.com/forum/#!forum/conda-forge>`__ and post your queries there. The mailing list is a secondary home for long threads about the ecosystem.
37+
4038

41-
TL:DR Don't be shy! Get in touch!
42-
----------------------------------

0 commit comments

Comments
 (0)