Functionality for common use cases

To accelerate adoption, we want to place priority on functionality that addresses common use cases.  This could include:

• Expanding the ecosystem of connectors: for example, delivering new integration connectors for common components like databases (target: four per year).
• Delivering entirely new functionality that addresses a commonly-requested scenario: for example, building a repository connector that supports history (target: one per year).

Below you can see our current suggested priorities, but we are keen to receive any additional suggestions from the community. Please feel free to comment directly against any of these pages with your thoughts or ideas on other areas we should consider a priority.

Currently under consideration...