Skip to main content
Version: Next



DevLake has joined the Apache Incubator and is aiming to become a top-level project. To achieve this goal, the Apache DevLake (Incubating) community will continue to make efforts in helping development teams to analyze and improve their engineering productivity. In this roadmap, we have summarized three major goals followed by the feature breakdown to invite the broader community to join us and grow together.

  1. As a dev data analysis application, discover and implement 3 (or even more!) usage scenarios:
    • A collection of metrics to track the contribution, quality and growth of open-source projects
    • DORA metrics for DevOps engineers
    • To be decided (let us know if you have any suggestions!)
  2. As dev data infrastructure, provide robust data collection modules, customizable data models, and data extensibility.
  3. Design better user experience for end-users and contributors.

Feature Breakdown

Apache DevLake is currently under rapid development. You are more than welcome to use the following table to explore your intereted features and make contributions. We deeply appreciate the collective effort of our community to make this project possible!

More data sources across different DevOps domains (Goal No.1 & 2). See existing data sourcesIssue Tracking: Source Code Management: Code Review: CI/CD: Code Quality: Incident Management: QA:
  • Selenium (Pending)
  • Junit (Pending)
  • JMeter (Pending)
  • Cucumber Test (Pending)
  • Google Docs (Pending)
  • Lark Docs (Pending)
  • Tencent Docs (Pending)
  • Lark Calendar #261 (Done)
  • Google Calendar (Pending)
  • Zoom Calendar (Pending)
  • Tencent Calendar (Pending)
OSS Community Metrics: Instant Messaging:
  • Slack (Pending)
  • Discord (Pending)
  • Lark messages (Pending)
Improved data collection, data models and data extensibility (Goal No.2)Data Collection:
  • Complete the logging system
  • Implement a good error handling mechanism during data collection
Data Models:
  • Introduce DBT to allow users to create and modify the domain layer schema. #1479 (Done)
  • Design the data models for 6 new domains, please refers to the data models of the tools under each domain (see the cell above):
    • Code Quality (WIP)
    • Testing
    • Calendar
    • Documentation
    • OSS Community Metrics (WIP)
    • Instant messaging
  • Polish the data models for existing domains: Issue/Task Management, Source Code Management, Code Review and CI/CD.
Data Extensibility:
  • Enhance the performance of data application under large-scaled usage scenarios
  • Support OLAP databases for more flexible data storage options
Better user experience (Goal No.3)For new users:
  • Iterate on a clearer step-by-step guide to improve the pre-configuration experience.
  • Provide a new Config UI to reduce frictions for data configuration #1700 (Done)
  • Showcase dashboard live demos to let users explore and learn about the dashboards. #1784 (Done)
For returning users:
  • Provide detailed guides to help users customize Grafana dashboards.
  • Work on the documentation for advanced features in the Config UI, such as the usage of Advanced Mode and replacements of old auth tokens for data connections.
For contributors:
  • Add more guide to set up DevLake in different operating system.
  • Provide clearer docs for contributors to get on board easier.
  • Add Swagger to document API #292 (Done)
  • More docs about raw/tool/domain data models

How to Influence the Roadmap

A roadmap is only useful when it captures real user needs. We are glad to hear from you if you have specific use cases, feedback, or ideas. You can submit an issue to let us know! Also, if you plan to work (or are already working) on a new or existing feature, tell us, so that we can update the roadmap accordingly. We are happy to share knowledge and context to help your feature land successfully.