roadmap.md

Roadmap

The CloudEvents Roadmap.

Note: The ordered lists for each milestone provide a way to reference each item; they don't imply an order for implementation.

Setup

1. Establish governance, contributing guidelines and initial stakeholders.
2. Define design goals for CloudEvents V.1.
3. Describe the scope of the specification.
4. Draft educational materials that provide context for reading the spec.

0.1

1. Draft specification that WG members agree could provide interoperability.
2. Include an initial set of use-cases for CloudEvents.
3. Define a type system for CloudEvents values.
4. Document at least 3 sample events that conform to the specification.
5. Github repo is organized to be approachable to a engineers who might want to implement the spec.
6. Finalize logo.
7. Create and deploy a website that features a simple overview, email list and directs visitors to Github.
8. Store all website assets in the CloudEvents repository, under the governance of the working group.

0.2

1. Have at least 2 implementations of the specification that can demonstrate interoperability.
2. Include a specification for mapping the CloudEvents specification to HTTP.
3. Include a specification for mapping the CloudEvents specification to JSON.
4. Changes to the spec to facilitate adoption.
5. Draft documentation and developer guide.
6. Publicize at conferences (CloudNativeCon Europe).

0.3

1. Interoperability demo.
   1. At least one open source implementation of sending and receiving events.
   2. Events are sent by code written by Developer1 and recieved by code written by Developer2, where Developer1 has no knowledge of Developer2.
   3. Draft trigger specification (e.g. how events + actions are associated).
2. Draft documentation and user guides.

0.4

1. Incorporate learnings and feedback from interop demo to support wider adoption.
2. Collaborate on libraries and supporting tools to use CloudEvents and integrate it with the ecosystem.