Skip to content

Roadmap 2020 #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jan 16, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 24 additions & 21 deletions ROADMAP.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,23 @@
# Roadmap
The Cloud Native Buildpacks project is rallying around the theme of _THEME_GOES_HERE_ for our upcoming work in 2020. Below are outcomes and features we intend to explore in the coming months. This roadmap will continue to be updated as our priorities evolve.

The Cloud Native Buildpacks project is rallying around the theme *Coming of Age* in 2020. Our roadmap will emphasize features and fixes that bring Cloud Native Buildpacks toward a 1.0 release, signaling that the project is mature enough for anyone to use it in production.

The roadmap is subdivided into three categories that represent the different goals we want to achieve. They are *Maturation*, *Beyond Pack*, and *Path to Production*. Below are outcomes and features we we will be working on for each of these categories. This roadmap will continue to be updated as our priorities evolve.

## Maturation

This part of our roadmap will ensure we’re delivering the best tools we can to our users. We want to finish work we've already started, increase the quality of the things we release, and improve our documentation.

### Buildpackages
- Outcomes: A container-native distribution mechanism (using registries) and developer friendly ergonomics for complex buildpack configurations.
- Status: Close to done.
- RFC: https://github.com/buildpacks/rfcs/blob/master/text/0007-spec-distribution.md
- Spec: https://github.com/buildpacks/spec/blob/master/distribution.md#buildpackage
- Issue(s: https://git.io/JvJGt
- Issue(s): https://git.io/JvJGt

### Reproducibility
- Outcomes: Builds are easier to understand
- Outcomes: Builds are verifiable. Build output can be replicated.
- Status: In progress
- Issue(s): https://git.io/JvJsN

### Codifications to our release process
Expand All @@ -18,6 +26,7 @@ The Cloud Native Buildpacks project is rallying around the theme of _THEME_GOES_

### Project descriptor
- Outcomes: Improvements to the UX for buildpack consumers (application developers)
- Status: In progress
- RFCs:
- https://github.com/buildpacks/rfcs/blob/master/text/0019-project-descriptor.md
- https://github.com/buildpacks/rfcs/pull/32
Expand All @@ -32,6 +41,10 @@ The Cloud Native Buildpacks project is rallying around the theme of _THEME_GOES_
- Outcomes: Getting started with the project is simple and documented
- Issue(s): https://git.io/JvJcH

## Beyond Pack

The goal of this category is to bring the experience delivered by the `pack` CLI to more platforms. This will allow our community to use buildpacks in different kinds of environments and in new ways. We'll achieve this by adding support for new build pipelines, enabling the distribution of buildpacks, and extending constructs like the [stack](https://buildpacks.io/docs/concepts/components/stack/) so that they work in more scenarios.

### CI/CD Adapters
- Outcomes: Developers can move beyond workstation builds to production
- RFCs:
Expand All @@ -47,24 +60,14 @@ The Cloud Native Buildpacks project is rallying around the theme of _THEME_GOES_
- RFC: https://github.com/buildpacks/rfcs/pull/35
- Issue(s):

### Contributor onboarding
- Outcomes: Grow our community of contributors to continue to innovate and
- RFC: https://github.com/buildpacks/rfcs/pull/42
- Issue(s): https://git.io/JvJcP
## Path to Production

### Content Signing
- Outcomes: The integrity of builds is first class citizen
- RFC:
- Issue(s):
-
The last part of our roadmap brings Cloud Native Buildpacks to state where they are ready for anyone to use in production. This requires a level of stability in the API and interfaces that ensure breaking changes are uncommon in the future. It also requires us to be as transparent as possible with our community. Above all it is dependent on delivering the outcomes described in *Maturation* and *Beyond Pack*.

### Windows ecosystem
- Outcomes: Developers and platform creators targetting Windows have a place in the CNB ecosystem
- RFC: https://github.com/buildpacks/rfcs/blob/master/text/0015-windows-lifecycle.md
- Issue(s):
-
### Version 1.0
- Outcomes: Buildpacks are ready for production
- RFC: TBD

### Fully credential-isolated builds (unsafe builders)
- Outcomes: Buildpacks can't steal your creds! Makes multitenant builds safe.
- RFC:
- Issue(s):
### Governance
- Outcomes: Our community knows how we make decisions and how to contribute
- Docs: https://github.com/buildpacks/community/blob/master/GOVERNANCE.md