Contributions are more than welcome in the form of pull requests.

You can either pick one of the open issues to work on, or provide enhancements according to your own needs. In any case, we suggest getting in touch beforehand to make sure the contribution will be aligned with the current development status.

To contribute:

  1. Fork the repository and clone the fork to your local development environment
  2. Identify a modular contribution to the code (avoid too large contributions to simplify review)
  3. Create a branch in your repository where you tackle the "modular contributions"
  4. For multiple contributions tackling different functionalities, create different branches
  5. For all the new functionalities provide tests (see and in the root to understand how tests can be run locally)
  6. When done, verify that all tests are passing
  7. If so, create a pull request against our repository (we cannot review pull requests with failing tests)
  8. Wait for the review
  9. Implement required changes
  10. Repeat until approval
  11. Done :) You can delete the branch in your repository.

Ultimately, contributing guides should keep aligned with those suggested by FIWARE (see here).

Development Setup

The development is mostly in python3 for now, and really in the early stages so things will change for sure. For now, you can get started with:

git clone
cd ngsi-timeseries-api
pipenv install

# if you want to set up a dev env to test everything locally, you'll need to...

pytest is used as the testing framework, but since most of QL's functionality is integration of components, you'll find docker-compose.yml files in the test folders to be run as a setup for tests. If you see .travis.yml file you'll see how they are running today, but probably at some point it's worth exploring pytest-docker plugins.

The requirements.txt still needs to be split between testing and production, that's also why the docker image is massive for now.

Repository Structure

In the current project tree structure you can find:

  • ngsi-timeseries-api
    • docs: Holds documentation files.
    • docker: To hold docker-related files for the scope of the project.
    • experiments: Sandbox for quick manual tests to try some stuff and derive new test cases.
    • specification: Contains the OpenAPI definition that QL implements.
    • src: Source code folder.
      • geocoding: Holds the code for interacting with OSM and doing geo-related processing.
      • reporter: Modules acting as the receiver of the notifications and API requests. It "parses/validates" them before handling tasks to the translators.
      • translators: Specific translators for each time-series databases, responsible for interacting with the lower-level database details.
      • utils: Common shared stuff looking for a better place to live in.