File: community.rst

package info (click to toggle)
intake 0.6.6-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 6,552 kB
  • sloc: python: 12,408; makefile: 37; sh: 14
file content (58 lines) | stat: -rw-r--r-- 2,628 bytes parent folder | download
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
Community
=========

Intake is used and developed by individuals at a variety of institutions.  It
is open source (`license <https://github.com/intake/intake/blob/master/LICENSE>`_)
and sits within the broader Python numeric ecosystem commonly referred to as
PyData or SciPy.

Discussion
----------

Conversation happens in the following places:

1.  **Usage questions** are directed to `Stack Overflow with the #intake tag`_.
    Intake developers monitor this tag.
2.  **Bug reports and feature requests** are managed on the `GitHub issue
    tracker`_. Individual intake plugins are managed in separate repositories
    each with its own issue tracker. Please consult the :doc:`plugin-directory`
    for a list of available plugins.
3.  **Chat** occurs on at `gitter.im/ContinuumIO/intake
    <https://gitter.im/ContinuumIO/intake>`_.  Note that
    because gitter chat is not searchable by future users we discourage usage
    questions and bug reports on gitter and instead ask people to use Stack
    Overflow or GitHub.
4.  **Monthly community meeting** happens the first Thursday of the month at
    9:00 US Central Time. See `<https://github.com/intake/intake/issues/596>`_,
    with a reminder sent out on the gitter channel. Strictly informal chatter.


.. _`Stack Overflow with the #intake tag`: https://stackoverflow.com/questions/tagged/intake
.. _`GitHub issue tracker`: https://github.com/intake/intake/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 Stack Overflow or GitHub issues over Gitter chat.  GitHub and
    Stack Overflow are more easily searchable by future users, and therefore is more
    efficient for everyone's time.  Gitter chat is strictly reserved for
    developer and community discussion.

    If you have a general question about how something should work or
    want best practices then use Stack Overflow.  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 Stack Overflow 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.