Update roadmap.md

Bringing roadmap.md into line with current roadmap and processes .

Signed-off-by: James Magowan <magowan@uk.ibm.com>

roadmap.md

@@ -1,87 +1,27 @@
 # Confidential Containers Roadmap
-When looking at the project's roadmap we distinguish between the short-term roadmap (2-4 months) vs. 
-the mid/long-term roadmap (4-12 months):
-- The **short-term roadmap** is focused on achieving an end-to-end, easy to deploy confidential 
-  containers solution using at least one HW encryption solution and integrated to k8s (with forked
-  versions if needed)
-- The **mid/long-term solutions** focuses on maturing the components of the short-term solution 
-  and adding a number of enhancements both to the solution and the project (such as CI,
-  interoperability with other projects etc.)
 
-# Short-Term Roadmap
+When looking at the project's roadmap we distinguish between the short-term roadmap (2-6 months) vs. the mid/long-term roadmap (6-18 months):
-The short-term roadmap aims to achieve the following:
+- The [short term roadmap](#short-term-roadmap) is focused on achieving an end-to-end, easy to deploy and stable confidential containers solution. We track this work on a number of github boards.
-- MVP stack for running confidential containers
+- The [mid and long term roadmap](#mid-and-long-term-roadmap) focuses on use case driven development.
-- Based on and compatible with Kata Containers 2
-- Based on at least one confidential computing implementation (SEV, TDX, SE, etc)
-- Integration with Kubernetes: kubectl apply -f confidential-pod.yaml
 
-The work is targeted to be completed by end of November 2021 and includes 3 milestones:
+# Short Term Roadmap
-![September 2021](./images/RoadmapSept2021.jpg)
+The short-term roadmap is based on our github boards and delivered through our on-going releases
-- **September 2021**
-  - Unencrypted image pulled inside the guest, kept in tmpfs
-  - Pod/Container runs from pulled image
-  - Agent API is restricted
-  - crictl only
-  
-![October 2021](./images/RoadmapOct2021.jpg)
-- **October 2021**
-  - Encrypted image pulled inside the guest, kept in tmpfs
-  - Image is decrypted with a pre-provisioned key (No attestation)
-  
-![November 2021](./images/RoadmapNov2021.jpg)
-- **November 2021**
-  - Image is optionally stored on an encrypted, ephemeral block device
-  - Image is decrypted with a key obtained from a key brokering service (KBS)
-  - Integration with kubelet
 
-For additional details on each milestone see [Confidential Containers v0](https://docs.google.com/presentation/d/1SIqLogbauLf6lG53cIBPMOFadRT23aXuTGC8q-Ernfw/edit#slide=id.p).
+- [Confidential containers github board](https://github.com/orgs/confidential-containers/projects/6/views/22)
+- [Trustee github board](https://github.com/orgs/confidential-containers/projects/10/views/1)
 
-Tasks are tracked on a weekly basis through a dedicated spreadsheet. 
+# Mid and Long Term Roadmap
-For more information see [Confidential Containers V0 Plan](https://docs.google.com/spreadsheets/d/1M_MijAutym4hMg8KtIye1jIDAUMUWsFCri9nq4dqGvA/edit#gid=0&fvid=1397558749).
 
+In CoCo use case driven development we identify the main functional requirements the community requires by focusing on key use cases.
 
-# Mid-Term Roadmap
+This helps the community deliver releases which address real use cases customers require and focusing on the right priorities. The use case driven development approach also includes developing the relevant CI/CDs to ensure end-to-end use cases the community delivers work over time.
 
-Continue our journey using knowledge and support of Subject Matter Experts (SME's) in other 
+We target the following use cases:
-projects to form stronger opinions on what is needed from components which can be integrated to
-deliver the confidential containers objectives.
 
-- Harden the code used for the demos
+- Confidential Federated Learning
-- Improve CI/CD pipeline
+- Multi-party Computing (data clean room, confidential spaces etc)
-- Clarify the release process
+- Trusted Pipeline (Supply Chain)
-- Establish processes and tools to support planning, prioritisation, and work in progress
+- Confidential RAG LLMs
-- Simple process to get up and running regardless of underlying Trusted Execution Environment
-  technology
-- Develop a small, simple, secure, lightweight and high performance OCI container image 
-  management library [image-rs](https://github.com/confidential-containers/image-rs) for 
-  confidential containers.
-- Develop small, simple shim firmware ([td-shim](https://github.com/confidential-containers/td-shim))
-  in support of trusted execution environment for use with cloud native confidential containers.
-- Document threat model and trust model, what are we protecting, how are we achieving it.
-- Identify technical convergence points with other confidential computing projects both inside 
-  and outside CNCF.
 
-# Longer-Term Roadmap
+A dedicated working group leads this effort. For additional details we recommend reviewing the working group's notes: [Confidential containers use cases driven development](https://docs.google.com/document/d/1LnGNeyUyPM61Iv4kBKFbfgmBr3RmxHYZ7Ev88obN0_E/edit?tab=t.0#heading=h.b0rnn2bw76n)
-
-Focused meetings will be set up to discuss architecture and the priority of longer-term objectives 
-in the process of being set up.
-
-Each meeting will have an agreed focus with people sharing material/thoughts ahead of time.
-
-Topics under consideration:
-- CI/CD + repositories
-- Community structure and expectations
-- 2 on Mid-Term Architecture
-	- Attestation
-	- Images
-	- Runtimes
-
-Proposed Topics to influence long-term direction/architecture:
-- Baremetal / Peer Pod
-- Composability of alternative technologies to deliver confidential containers
-- Performance
-- Identity / Service Mesh
-- Reproducible builds/demos
-- Edge Computing
-- Reduce footprint of image pull