Roadmap

Note: This roadmap is currently considered to be a draft pending feedback and review.

This page serves to track the development of Jasper from a code-level standpoint. If you're looking for more information about Jasper as a whole, head to the main site.

Versioning

In the past, Jasper has not followed a strict semantic versioning system. Going forward, our policy will be to bump the major version number when a disk image-incompatible release is posted. Note that the minor version number will likely be left at 0, but is included for future flexibility.

The current Jasper software is considered to be v1.0. This document outlines the remaining changes we're targeting for v1.x, as well as for v2.0. These changes are broken down into "Additional Features" and "Bugfixes & Cleanup".

Version 1.x

Additional Features

• • Additional TTS speakers (Issue #155)
  • Assigned to: @Holzhaus

Bugfixes & Cleanup

• • Get rid of bash scripts (Issue #161): Use python-only implementations for platform-independence
  • Assigned to: Holzhaus
• • Stop fiddling around with boot folder (Issue #162): Merge all startup scripts into one
  • Assigned to: Holzhaus
• • Use tempfile module for temporary files
  • Assigned to: Everyone
• • Avoid hard-coding paths
  • Assigned to: Everyone
• • Miscellaneous bug fixes: add shebangs, fix any incorrect arguments in codebase, etc.
  • Assigned to: Everyone

Version 2.0

Additional Features

• • Configurable audio engine / doing transcription in a separate thread (Issue #247)
  • Assigned to: @Holzhaus
  • Status: done
• • Plugin architecture (Issue #130)
  • Goal: Break Jasper down into a number of plugin types (e.g., input-handling modules, TTS engines, etc.) and provide an interface for adding new plugins.
  • Assigned to: @Holzhaus
  • Status: done (although we might want to replace it with a better implementation using setuptools entry points)
• • Configuration module (Issue #128)
  • Goal: Create a more mature system for handling configuration, both across jasper-client and for specific modules.
  • Assigned to: @Holzhaus
  • Status: in-review
• • Multi-lingual support (Issue #134)
  • Goal: Make it easy to perform translation in a variety of languages and write modules that are either non-English or language agnostic.
  • Assigned to: @Holzhaus
  • Status: done
• • Better system for sharing modules (Issue #163)
  • Goal: Make it easy to share modules throughout the community, potentially by hosting them in a separate repository.
  • Assigned to: @crm416

Bugfixes & Cleanup

None (for now).