Add Roadmap to README
This commit is contained in:
@@ -13,6 +13,18 @@ The philosophy behind Backstage is simple: Don't expose your engineers to the fu
|
||||
|
||||
At Spotify we [strongly believe](https://backstage.io/the-spotify-story) that a better developer experience leads to happier and more productive engineers.
|
||||
|
||||
## Project roadmap
|
||||
|
||||
Backstage has been in production for over 2 years inside Spotify. But the Open Source version is still in an early stage. We are envisioning three phases of the project and we are commited to deliver on all of them:
|
||||
|
||||
* **Phase 1: Extensible front-end platform** (today) - Backstage helps you get started building a single consistent UI layer for your internal infrastructure. Creating a Plugin is super simple.
|
||||
|
||||
* **Phase 2: Software inventory** (next 2-3 months) - A central _software inventory_ with clear ownership and the ability to easily create and manage software at scale. Regardless if your developers want to create a new library, see their service' deployment status in Kubernetes or the test coverage for a website -- Backstage offers all the tools in one place.
|
||||
|
||||
* **Phase 3: Ecosystem** (later) - Everyone's infrastructure stack is different. By fostering a vibrant community of contributors we hope to provide an ecosystem of Open Source plugins/integrations that allows you to pick the tools that matches your stack.
|
||||
|
||||
The ultimate goal of Backstage is to become the de-facto standard UI layer for the infrastructure landscape.
|
||||
|
||||
## Overview
|
||||
|
||||
The Backstage platform consists of a number of different components:
|
||||
|
||||
Reference in New Issue
Block a user