paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
af092b088409c45171b1408c147d1aed9345f27d
backstage/docs/overview/roadmap.md
T
Francesco Corti 1b994b4b6e Roadmap review for breaking links. 
Signed-off-by: Francesco Corti <francescoc@spotify.com>
2021-07-20 18:07:13 +02:00

10 KiB
Raw Blame History

id, title, description
id title description
roadmap Roadmap 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. Treat the roadmap as an ever-evolving guide to keep us aligned as a community on:

  • Upcoming enhancements and benefits,
  • Planning contributions and support,
  • Planning the project’s adoption,
  • Understanding what things are coming soon,
  • Avoiding duplication of work

How to influence the roadmap

As we evolve Backstage, we want you to contribute actively in the journey to define the most effective developer experience in the world.

A roadmap is only useful if it captures real needs. If you have success stories, feedback, or ideas, we want to hear from you! If you plan to work (or are already working) on a new or existing feature, please let us know, so that we can update the roadmap accordingly. We are also happy to share knowledge and context that will help your feature land successfully.

You can also head over to the CONTRIBUTING guidelines to get started.

If you have specific questions about the roadmap, please create an issue, ping us on Discord, or book time with the Spotify team.

How to read the roadmap

The Backstage roadmap lays out both “what’s next” and “future work”. With "next" we mean features planned for release within the ongoing quarter starting in July until September 2021 included. With "future" we mean features in the radar, but not yet scheduled.

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 it here as well.

Roadmap evolution

Will this roadmap change? Obviously!

Roadmap are always evolving and ours is no different; you can expect to see this updated roughly every month.

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.

Backstage Core

The following features are planned for release:

  • Composable homepage: We’re seeing lots of interest from the community in reusable components to build a homepage experience where users can easily surface what they might find useful to start their tasks. Check out the milestone for further details.
  • Improved responsiveness: Check out the RFC here for further details on how to improve the responsiveness for Backstage's UI.

Software Templates

The following features are planned for release::

  • Re-creation/resubmission in case of failure: Speed up productivity by allowing developers to relaunch a project after a failure or any unexpected problem. In the current version, this task requires retyping and a full re-creation from scratch.
  • Performance and usability improvements for contributors: Reach a relevant improvement in templating's performance through the replacement of handlebars. Other replacements will be considered as part of this task (possibly cookiecutter) for easier software template creation, allowing more contributors to reach their goals without having to learn new tooling.
  • Improved extensibility through inclusion: Make software templates more maintainable and extensible by adding $include support for parameters.
  • Authenticated job creation: Created jobs will be able to run with an authenticated user with all actions tracked for future consumption and evidence. Track users creating jobs and make “jobs created by me” reporting available.

Software Catalog

The following features are planned for release:

  • Request For Comments (RFC) for composability improvements (routing): Enable plugins to be auto-added and make plugin installation and upgrades easier for all Backstage users. This includes information card layouts, entity pages containing content and hooking the external header, considering the support of a separate deployment, and configuration for plugins.
  • Removing duplicated entities in catalog: As any adopter knows, a software catalog can contain thousands or more entities and it is very important to avoid duplications in naming to prevent failures. With this development task, two entities with the same name won't be allowed as described here.
  • Connecting identity to ownership to prepare for role-based access control (RBAC): This is a first step to supporting RBAC for the software catalog (see the future work section for further details). Provide each entity within the software catalog with a recognized owner.
  • Catalog performance improvements through improved caching: Fix the performance gaps in the catalog processor, which currently doesn’t have a strong caching mechanism. The current version often requires fetching a relevant amount of data, especially at scale.

Search

The following features are planned for release:

  • ElasticSearch integration: Add ElasticSearch to the Search Platform as the underlying search engine. Check out the milestone here for further details.

TechDocs

The following features are planned for release:

  • TechDocs beta release: Fix remaining bugs to get TechDocs to Beta. Check out the milestone here for further details.

Future work

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.

  • Improved UX design: Provide a better Backstage user experience through visual guidelines and templates, especially navigation across plug-ins and portal functionalities.
  • Catalog composability (routing): Follow up development after the RFC planned for the ongoing quarter (see what’s next for further details).
  • Catalog-import improvements: Provide a faster (scalability) and better (more features like move/rename) way to import entities into the Software Catalog. Importing items in the Software Catalog is crucial for creating a Backstage proof-of-concept or testing/planning for broader organizational adoption. This enhancement better supports getting developers to use Backstage with less effort and customization.
  • Catalog improvements: Add pagination and sourcing to Software Catalog.
  • GraphQL support: Introduce the ability to query Backstage backend services with a standard query language for APIs.
  • Software templates performance improvements through decoupling a separate worker: Improve performance through decoupling resource-consuming services and making them asynchronous. In the current version, project auto-creation through the Software Templating system can consume a lot of resources and bottleneck many concurrent projects created simultaneously.
  • API discovery and documentation: Add better support for the gRPC.
  • Adding TechDocs search to the Search Platform: Having this capability in place will provide a better and new major version of the Search Platform (v3.0). You can refer to the milestone here for further details.
  • TechDocs GA release: Work toward enhancements necessary to get TechDocs to general availability. Check out the milestone here for further details.

Completed milestones

Read more about the completed (and released) features for reference.

Reference in New Issue View Git Blame Copy Permalink