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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
.. _contributing:
************
Contributing
************
If you want to contribute to Mopidy, here are some tips to get you started.
.. _asking-questions:
Asking questions
================
Please get in touch with us in one of these ways when requesting help with
Mopidy and its extensions:
- Our Discourse forum: `discourse.mopidy.com <https://discourse.mopidy.com>`_.
- The ``#mopidy-users`` stream on Zulip chat: `mopidy.zulipchat.com
<https://mopidy.zulipchat.com>`_.
Before asking for help, it might be worth your time to read the
:ref:`troubleshooting` page, both so you might find a solution to your problem
but also to be able to provide useful details when asking for help.
Helping users
=============
If you want to contribute to Mopidy, a great place to start is by helping other
users in the discussion forum and the ``#mopidy-users`` Zulip stream. This is a
contribution we value highly. As more people help with user support, new users
get faster and better help. For your own benefit, you'll quickly learn what
users find confusing, difficult or lacking, giving you some ideas for where you
may contribute improvements, either to code or documentation. Lastly, this may
also free up time for other contributors to spend more time on fixing bugs or
implementing new features.
.. _issue-guidelines:
Issue guidelines
================
#. If you need help, see :ref:`asking-questions` above. The GitHub issue
tracker is not a support forum.
#. If you are not sure if what you're experiencing is a bug or not, post in the
`discussion forum <https://discourse.mopidy.com>`__ first to verify that
it's a bug.
#. If you are sure that you've found a bug or have a feature request, check if
there's already an issue in the `issue tracker
<https://github.com/mopidy/mopidy/issues>`_. If there is, see if there is
anything you can add to help reproduce or fix the issue.
#. If there is no exising issue matching your bug or feature request, create a
`new issue <https://github.com/mopidy/mopidy/issues/new>`_. Please include
as much relevant information as possible. If it's a bug, including how to
reproduce the bug and any relevant logs or error messages.
Pull request guidelines
=======================
#. Before spending any time on making a pull request:
- If it's a bug, :ref:`file an issue <issue-guidelines>`.
- If it's an enhancement, discuss it with other Mopidy developers first,
either in a GitHub issue, on the discussion forum, or on Zulip chat.
Making sure your ideas and solutions are aligned with other contributors
greatly increases the odds of your pull request being quickly accepted.
#. Create a new branch, based on the ``develop`` branch, for every feature or
bug fix. Keep branches small and on topic, as that makes them far easier to
review. We often use the following naming convention for branches:
- Features get the prefix ``feature/``, e.g.
``feature/track-last-modified-as-ms``.
- Bug fixes get the prefix ``fix/``, e.g. ``fix/902-consume-track-on-next``.
- Improvements to the documentation get the prefix ``docs/``, e.g.
``docs/add-ext-mopidy-spotify-tunigo``.
#. Follow the :ref:`code style <codestyle>`, especially make sure the
``flake8`` linter does not complain about anything. Our CI setup will
check that your pull request is "flake8 clean". See :ref:`code-linting`.
#. Include tests for any new feature or substantial bug fix. See
:ref:`running-tests`.
#. Include documentation for any new feature. See :ref:`writing-docs`.
#. Feel free to include a changelog entry in your pull request. The changelog
is in :file:`docs/changelog.rst`.
#. Write good commit messages.
- Follow the template "topic: description" for the first line of the commit
message, e.g. "mpd: Switch list command to using list_distinct". See the
commit history for inspiration.
- Use the rest of the commit message to explain anything you feel isn't
obvious. It's better to have the details here than in the pull request
description, since the commit message will live forever.
- Write in the imperative, present tense: "add" not "added".
For more inspiration, feel free to read these blog posts:
- `Writing Git commit messages
<https://365git.tumblr.com/post/3308646748/writing-git-commit-messages>`_
- `A Note About Git Commit Messages
<https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html>`_
- `On commit messages
<https://who-t.blogspot.com/2009/12/on-commit-messages.html>`_
#. Send a pull request to the ``develop`` branch. See the `GitHub pull request
docs <https://help.github.com/en/articles/about-pull-requests>`_ for help.
.. note::
If you are contributing a bug fix for a specific minor version of Mopidy
you should create the branch based on ``release-x.y`` instead of
``develop``. When the release is done the changes will be merged back into
``develop`` automatically as part of the normal release process. See
:ref:`creating-releases`.
|
