Contributing to the opsdroid ecosystem is strongly encouraged and every little bit counts! We even send sticker packs to our contributors to say thank you! There are so many ways to contribute to opsdroid:

Check out the following guides for specific contribution suggestions.

If you need help or if you are unsure about something join our matrix channel and ask away! We are more than happy to help you.


All contributors to the project, including maintainers, contribute using the following process:

  • Fork the main project to your own account

  • Work on your changes on a feature branch

  • Create a pull request back to the main project

  • Tests and test coverage will be checked automatically

  • A project maintainer will review and merge the pull request


# clone the repo
git clone
cd opsdroid

# install the project in "editable" mode
pip install -e .

# run opsdroid
opsdroid start

Running the tests

# install pre-commit hooks
pip install -U pre-commit

# set up pre-commit hooks (only needs to be done once)
pre-commit install

# install test runner
pip install -U tox

# run tests

Developing in containers

Developing in containers can be a great way to ensure that opsdroid will run in a clean python environment and that all dependencies are captured.

# build the container
docker build -t opsdroid/opsdroid:myfeature .

# run opsdroid
docker run --rm -ti -v $(pwd):/usr/src/app opsdroid/opsdroid:myfeature

Running the tests

# run tests
docker run --rm -ti -v $(pwd):/usr/src/app opsdroid/opsdroid:myfeature tox

Automatic Linting with Black

Opsdroid is running Black to deal with linting issues and it will be triggered when Travis runs our tests automatically. You can install Black on your machine and have it correct any linting issues that you might have.

Install Black

Run the following command to install Black on your machine.

pip install black

Note: You need to be running Python 3.6.0+ to have Black running.

You also need to have pre-commit installed and set up in order to have Black check your code and work on each git commit. If you followed the instructions on running the tests earlier on Developing, you should have pre-commit set up already, and if not, please do it now.

Using Black

Black will be triggered when you commit changes with the command git commit. You can then check your terminal for what sort of message you get from Black - either all is good or some files would be formatted.

Example of issues with linting

Let’s imagine that you have added your files to stating and did git commit -m 'my awesome feature, then black will run on your terminal and show you something like this:

lint run-test-pre: PYTHONHASHSEED='4023478313'
lint run-test: commands[0] | flake8 --builtins=_ opsdroid
lint run-test: commands[1] | pydocstyle opsdroid tests
lint run-test: commands[2] | black --check opsdroid tests scripts
would reformat /home/travis/build/opsdroid/opsdroid/tests/
All done! 💥 💔 💥
1 file would be reformatted, 87 files would be left unchanged.
ERROR: InvocationError for command /home/travis/build/opsdroid/opsdroid/.tox/lint/bin/black --check opsdroid tests scripts (exited with code 1)

As you can see black tells you that it found some issues with linting on 1 file and since it reformats your code to fix the linting issues, it tells you that the file would be reformatted.

Black will change your file and if you go to git status you will see that your file was modified. You just need to add the files to starting again and commit them with the previous commit message. Afterwards, you can push the changes to your repository/PR.

Example of good linting

If your linting is good when you commit your changes you will see the following message:

lint run-test-pre: PYTHONHASHSEED='3517441289'
lint run-test: commands[0] | flake8 --builtins=_ opsdroid
lint run-test: commands[1] | pydocstyle opsdroid tests
lint run-test: commands[2] | black --check opsdroid tests scripts
All done! ✨ 🍰 ✨
88 files would be left unchanged.
___________________________________ summary ____________________________________
lint: commands succeeded
congratulations :)

This tells you that your linting is good and you can push these changes to Github.


More documentation is always appreciated and it’s something that you can contribute to from the GitHub web interface. This might be a great start point if you are new to Open Source and GitHub!

Things that we need help with:

  • More documentation. Something that you think is unclear?

  • More examples of how to use opsdroid

  • More Tutorials

  • Typos/Grammar check

  • Blog posts, articles, etc

  • Any issue marked with the documentation tag

Building the docs

Opsdroid’s documentation is built using Sphinx with the Recommonmark and Napoleon plugins and is hosted on readthedocs.

You can build the documentation yourself locally and view them using the built in Python web server.

$ tox -e docs  # or `sphinx-build -b html docs/ docs/_build/`
The HTML pages are in docs\_build.

$ cd docs/_build && python -m http.server
Serving HTTP on port 8000 (http://localhost:8000/) ...

Writing documentation

All documentation should be written in Basic English where possible. We should try to keep words, phrases and grammar as simple as possible to make the project as accessible as possible.

Markdown is our preferred markup language, although reStructuredText (rst) is also supported. You may also embed portions of rst within your markdown documentation with the following syntax:

.. warning::
   This is a warning admonition from rst within a markdown document.
   Useful because markdown doesn't have warnings.

Renders as:


This is a warning admonition from rst within a markdown document. Useful because markdown doesn’t have warnings.

You can also use Sphinx autodoc directives to embed docstrings from the opsdroid module within your markdown documentation too.

.. autofunction:: opsdroid.matchers.match_event

Renders as:

opsdroid.matchers.match_event(event_type, **kwargs)

Return event type matcher.

Decorator that calls skill based on passed event_type.

  • event_type (str) – opsdroidstarted, message, typing, reaction, file, image

  • **kwargs (dict) – arbitrary kwargs to be added to the event matcher


Decorated function

It is preferable to keep as much documentation within docstrings in the opsdroid codebase as possible and to include it in the documentation website using autodoc.


Opsdroid runs by default in English, but it can be translated to your local language. In order to achieve it, gettext and babel are used.

To mark a string as translatable, just call the special _ function:

txt = 'hello {}'.format(name)  # this is NOT translatable
txt = _('hello {}').format(name)  # but now it's translatable! 🎉

When some new translatable strings are added, you must extract them to a non-versioned pot file with:

python extract_messages

Then, update all existing language po files from the extracted pot file with the command:

python update_catalog

Now, you can translate editing manually or with Poedit the po files in locale/<lang>/LC_MESSAGES/opsdroid.po. Those files contain the real translations and are versioned.

After you made a change in any po file, in order to view the changes in opsdroid, you should compile them to mo binary files, the format read by python gettext:

python compile_catalog

Starting a new language

If your language is not in the locale folder, you can initialize it. You will need the ISO 639-1 code of the language. For example, in order to start a new Esperanto translation:

python init_catalog -l eo

Then you can translate it in locale/eo/LC_MESSAGES/opsdroid.po, then compile it, etc.

Creating New Modules

Opsdroid is an open source chatbot framework. It is designed to be extendable, scalable and simple. It comes with a few official modules that can be found in the Opsdroid GitHub account.

If you love a particular platform and wish to use opsdroid with it or if you want opsdroid to interact with something in a certain way, you can create your own modules and extend the functionality of opsdroid.

If you don’t know where to start, make sure to check the overview and read the documentation. Remember that you can also ask for help in our matrix channel

Creating Consistent Logging Messages

When creating log messages, we would like to see a consistency around how to structure and utilize them.

  • In general any copyright/legal name should be Capitalized (i.e. Slack, Telegram)

  • All usage of the opsdroid capabilities should be Capitalized (Connector, Skill, Database and Parsers)

  • All sentances should end with a period.

  • When inserting specific text from an error message, end the sentance with a period.


You can help us by reporting new issues or by fixing existing issues.

If you find any part of opsdroid that’s acting odd, it would be great if you take the time to create a new issue. That will help us keep opsdroid devoid of any bugs.

We try to tackle issues as fast as possible, but help would be greatly appreciated. To get started, simply follow the workflow guidelines and developing instructions.



Thank you to all the people who have already contributed to opsdroid!


Thank you to all our backers! [Become a backer]


Thank you to all our sponsors! (please ask your company to also support this open source project by becoming a sponsor)