From 1ba5c1e0a3585a290751f97728d319b33386f96b Mon Sep 17 00:00:00 2001 From: Francesco Corti Date: Wed, 4 May 2022 17:37:23 +0200 Subject: [PATCH] Updated roadmap to Q3 2022. Signed-off-by: Francesco Corti --- docs/overview/roadmap.md | 88 ++++++++++++++++------------------------ 1 file changed, 35 insertions(+), 53 deletions(-) diff --git a/docs/overview/roadmap.md b/docs/overview/roadmap.md index 8ecd7c4a38..ea81d68ab6 100644 --- a/docs/overview/roadmap.md +++ b/docs/overview/roadmap.md @@ -6,58 +6,57 @@ description: Roadmap of Backstage ## The Backstage Roadmap -Backstage is currently under rapid development. This page details the project’s -public roadmap, the result of ongoing collaboration between the core maintainers -and the broader Backstage community. +Backstage is currently under rapid development. This page details the project’s public roadmap, the result of ongoing collaboration between the core maintainers and the broader Backstage community. -The Backstage roadmap lays out both [“what’s next”](#whats-next) and -[“future work”](#future-work). With "next" we mean features planned for release -within the ongoing quarter from January through March 2022. With "future" we -mean features in the radar, but not yet scheduled. +The Backstage roadmap lays out both [“what’s next”](#whats-next) and [“future work”](#future-work). With "next" we mean features planned for release within the ongoing quarter from January through March 2022. With "future" we mean features in the radar, but not yet scheduled. | [What's next](#whats-next) | [Future work](#future-work) | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Backstage 1.0 (and following versions)](#backstage-10-and-following-versions)
[Backstage Security Audit](#backstage-security-audit)
[Moving to Incubation in CNCF](#moving-to-incubation-in-cncf) | Backend Services
Security Plan (and Strategy)
TechDocs Addon framework
Composable Homepage 1.0
GraphQL
Telemetry
Improved UX design | +| [Ease of onboarding](#ease-of-onboarding)
[Search 1.0](#search-1.0)
[TechDocs Addon framework](#techdocs-addon-framework)
[Backend Services (initial)](#backend-services-(initial))
[Backstage Security Audit](#backstage-security-audit)
[SIGs for contributors](#sigs-for-contributors) | Security Plan (and Strategy)
Composable Homepage 1.0
GraphQL
Telemetry
Improved UX design | The long-term roadmap (12 - 36 months) is not detailed in the public roadmap. -Third-party contributions are also not currently included in the roadmap. Let us -know about any ongoing developments and we’re happy to include them here as well. +Third-party contributions are also not currently included in the roadmap. Let us know about any ongoing developments and we’re happy to include them here as well. ## What’s next The feature set below is planned for the ongoing quarter, and grouped by theme. -The list order doesn’t necessarily reflect priority, and the development/release -cycle will vary based on maintainer schedules. +The list order doesn’t necessarily reflect priority, and the development/release cycle will vary based on maintainer schedules. -### Backstage 1.0 (and following versions) +### Ease of onboarding -During the first quarter of 2022, we plan to finalize and release version 1.0 of -the Backstage platform (which includes Core, -[Catalog](https://backstage.io/docs/features/software-catalog/software-catalog-overview), -[Scaffolder](https://backstage.io/docs/features/software-templates/software-templates-index) -and [TechDocs](https://backstage.io/docs/features/techdocs/techdocs-overview)). -Included as part of this milestone: +A faster (with less development) and easier setup of a POC, as part of the onboarding experience, has been a common and loud suggestion from new adopters as well as analysts looking at Backstage. -- Deciding on the cadence of minor/weekly/daily releases to provide clarity on - the frequency and expectations for future versions of the platform and its - defining modules. -- Establish the support model to set the expectations from the adopters in their - respective use cases. +With this initiative we plan to start facing this important topic with the most commonly used and challenging tasks. More in particular we plan to reduce the effort required to go from zero to production in installing and customising Backstage, as well as reducing the effort required to populate the Software Catalog. + +More iterations will be required in the following quarters, but this will be a good improvement in the onboarding experience, especially for the benefit of new adopters. + +### Search 1.0 + +Fix the few remaining issues to get Backstage Search platform up to 1.0 ([here](https://github.com/backstage/backstage/milestone/27) and [here](https://github.com/backstage/backstage/milestone/28)). + +### TechDocs Addon framework + +Addons are TechDocs features that are added on top of the base docs like code experience. An example would be a feature that showed comments on the page. We plan to add an Addon framework and open source a selection of the Addons that we use internally at Spotify. Further Addons can then be added by the Community. + +### Backend Services (initial) + +To better scale and maintain the Backstage instances, a backend layer of services is planned to be introduced as part of the software architecture. This layer of backend services will help in decoupling the various modules (e.g. Catalog and Scaffolder) from the frontend experience. + +In this quarter we plan to start designing the new architecture, together with the first experimentation and development of the software components. ### Backstage Security Audit +This is the continuation of the initiative started in the previous quarter. This quarter will see the publication of the report describing the outcome of the auditing, together the first fixes and the development of some of the changes required to address the vulnerabilities. + This initiative is the first of a broader Security Strategy for Backstage. The purpose of the Security Audit is to involve third-party companies in auditing -the platform and highlighting potential vulnerabilities. The benefit for the -adopters is clear: We want Backstage to be as secure as possible, and we want to -make it reliable through a specific initiative. This initiative in particular is -done together, and with the support of, the -[Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/). +the platform. The benefit for the adopters is clear: we want Backstage to be as secure as possible, and we want to make it reliable through a specific initiative. -### Moving to Incubation in CNCF +This initiative is done together, and with the support of, the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/). -The progress of the request can be seen -[here](https://github.com/cncf/toc/pull/717). +### SIGs for contributors + +The request to better coordinate the increasing contributions coming from the various developers' adopter is loud and clear. We think that the community is mature enough to start launching the SIGs (Special Interest Groups) following the successful model of Kubernetes. ## Future work @@ -65,30 +64,13 @@ The following feature list doesn’t represent a commitment to develop, and the list order doesn’t reflect any priority or importance, but these features are on the maintainers’ radar, with clear interest expressed by the community. -- **Backend Services:** To better scale and maintain the Backstage instances, a - backend layer of services is planned to be introduced as part of the software - architecture. This layer of backend services will help in decoupling the - various modules (e.g. Catalog and Scaffolder) from the frontend experience. - **Security Plan (and Strategy):** The purpose of the Security Strategy is to move another step along the path to maturing the platform, setting the expectations of any adopters from a security standpoint. -- **Search 1.0:** Fix the few remaining issues to get Backstage Search platform - up to 1.0 ([here](https://github.com/backstage/backstage/milestone/27) and - [here](https://github.com/backstage/backstage/milestone/28)). -- **TechDocs Addon framework and Addons:** Addons are TechDocs features that are - added on top of the base docs like code experience. An example would be a - feature that showed comments on the page. We plan to add an Addon framework - and open source a selection of the Addons that we use internally at Spotify. - Further Addons can then be added by the Community. -- **Composable Homepage 1.0:** Driving this to 1.0 by adding some composable - components. -- **[GraphQL](https://graphql.org/) support:** Introduce the ability to query - Backstage backend services with a standard query language for APIs. -- **Telemetry:** To efficiently generate logging and metrics in such a way that - adopters can get insights so that Backstage can be monitored and improved. -- **Improved UX design:** Provide a better Backstage user experience through - visual guidelines and templates, especially navigation across plug-ins and - portal functionalities. +- **Composable Homepage 1.0:** Driving this to 1.0 by adding some composable components. +- **[GraphQL](https://graphql.org/) support:** Introduce the ability to query Backstage backend services with a standard query language for APIs. +- **Telemetry:** To efficiently generate logging and metrics in such a way that adopters can get insights so that Backstage can be monitored and improved. +- **Improved UX design:** Provide a better Backstage user experience through visual guidelines and templates, especially navigation across plug-ins and portal functionalities. ## How to influence the roadmap