1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
:orphan:
.. this page is referenced from the topbar which comes from the theme
Community
=========
Dask is used and developed by individuals at a variety of institutions. It
sits within the broader Python numeric ecosystem commonly referred to as PyData
or SciPy.
Discussion
----------
Conversation happens in the following places:
#. **Usage questions, requests for help, and general discussions** happen in the
`Dask Discourse forum`_. If your discussion topic is not a bug report
or a feature request, this is the best place to start. It's also a good
place to show off cool things you have built using Dask and to get to know other
community members.
#. **Usage questions** may also be directed to `Stack Overflow with the #dask tag`_,
which is monitored by Dask developers. However, the scope of what is considered
a good Stack Overflow question can be narrow, so the Dask Discourse forum may
be a better place to start.
#. **Bug reports and feature requests** are managed on the `GitHub issue
tracker`_
#. **Real-time chat** occurs on
`https://dask.slack.com/ <https://join.slack.com/t/dask/shared_invite/zt-mfmh7quc-nIrXL6ocgiUH2haLYA914g>`_.
Note that Slack chat not easily searchable and indexed by search engines, so
detailed discussion topics around bug reports or usage should go to GitHub issues or
the Dask Discourse forum, respectively.
#. **Monthly developer meeting** happens the first Thursday of the month at
10:00 US Central Time in `this video meeting <https://us06web.zoom.us/j/87619866741?pwd=S2RxMlRKcnVvakt4NHZoS1cwOGZoZz09>`_.
Meeting notes are available in
`this Google doc <https://docs.google.com/document/d/1UqNAP87a56ERH_xkQsS5Q_0PKYybd5Lj2WANy_hRzI0/edit>`_.
#. **Monthly social meeting** happens the third Thursday of the month at 10:00
US Central Time in `this video meeting <https://whereby.com/dask-dev>`_.
.. raw:: html
<iframe id="calendariframe" src="https://calendar.google.com/calendar/embed?ctz=local&src=4l0vts0c1cgdbq5jhcogj55sfs%40group.calendar.google.com" style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
<script>document.getElementById("calendariframe").src = document.getElementById("calendariframe").src.replace("ctz=local", "ctz=" + Intl.DateTimeFormat().resolvedOptions().timeZone)</script>
You can subscribe to this calendar to be notified of changes:
* `Google Calendar <https://calendar.google.com/calendar/u/0?cid=NGwwdnRzMGMxY2dkYnE1amhjb2dqNTVzZnNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>`__
* `iCal <https://calendar.google.com/calendar/ical/4l0vts0c1cgdbq5jhcogj55sfs%40group.calendar.google.com/public/basic.ics>`__
.. _`Dask Discourse forum`: https://dask.discourse.group
.. _`Stack Overflow with the #dask tag`: https://stackoverflow.com/questions/tagged/dask
.. _`GitHub issue tracker`: https://github.com/dask/dask/issues/
Asking for help
---------------
We welcome usage questions and bug reports from all users, even those who are
new to using the project. There are a few things you can do to improve the
likelihood of quickly getting a good answer.
1. **Ask questions in the right place**: We strongly prefer the use
of Discourse or GitHub issues over Slack chat. Discourse and
GitHub are more easily searchable by future users, and therefore can be
useful to many more people than those directly involved.
If you have a general question about how something should work or
want best practices then use Discourse. If you think you have found a
bug then use GitHub
2. **Ask only in one place**: Please restrict yourself to posting your
question in only one place (likely the Dask Discourse or GitHub) and don't post
in both
3. **Create a minimal example**: It is ideal to create `minimal, complete,
verifiable examples <https://stackoverflow.com/help/mcve>`_. This
significantly reduces the time that answerers spend understanding your
situation, resulting in higher quality answers more quickly.
See also `this blogpost
<http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports>`_
about crafting minimal bug reports. These have a much higher likelihood of
being answered
Paid support
------------
In addition to the previous options, paid support is available from the
following organizations (listed in alphabetical order):
- Anaconda: `<https://www.anaconda.com/products/professional-services>`_
- Coiled: `<https://coiled.io>`_
- Quansight: `<https://www.quansight.com/open-source-support>`_
|
