docs: update Roadmap (#8)

- Make the milestones subbullets
- Add tracking issues
- Add two proposed milestones for 2023Q3

ROADMAP.md

@@ -16,54 +16,80 @@ https://github.com/ipfs/pomegranate/issues/5
 - [🛣️ Milestones](#️-milestones)
   - [2022](#2022)
     - [Mid Q4 (November)](#mid-q4-november)
+      - [Communicate the State of IPFS in JS](#communicate-the-state-of-ipfs-in-js)
     - [Late Q4 (December)](#late-q4-december)
+      - [Double Team Capacity](#double-team-capacity)
   - [2023](#2023)
     - [Early Q1 (January)](#early-q1-january)
+      - [Finalize "Pomegranate" Execution Plan](#finalize-pomegranate-execution-plan)
     - [Late Q1 (March)](#late-q1-march)
+      - ["Pomegranate" "v1" Released](#pomegranate-v1-released)
     - [Q2](#q2)
+      - [Drive Adoption of "Pomegranate"](#drive-adoption-of-pomegranate)
+    - [Q3](#q3)
+      - [Support Fully Speced Delegated Routing Protocols and Endpoints](#support-fully-speced-delegated-routing-protocols-and-endpoints)
+      - [PL Delegate and Preload Nodes Will Be Shutting Down](#pl-delegate-and-preload-nodes-will-be-shutting-down)
 
-## 🛣️ Milestones
-### 2022
+# 🛣️ Milestones
+## 2022
 
-#### Mid Q4 (November)
+### Mid Q4 (November)
 
-Communicate the IPFS-in-JS state.
+#### Communicate the State of IPFS in JS
 
 **Problem to solve:** Currently, very few know the direction for IPFS-in-JS and how they can best help. This affects project resourcing, recruiting, and IPFS adoption in general.
 
 **Done state:**
-- Present and share the IPFS Camp 2022 presentation.
-- Write and publish a blog post.
-- Hold a community vote and communication about a name for the new IPFS-in-JS implementation.
+- Present and share the IPFS Camp 2022 presentation. ([Tracking Issue](https://github.com/ipfs/pomegranate/issues/7))
+- Write and publish a blog post. (Done: [State of IPFS in JS](https://blog.ipfs.tech/state-of-ipfs-in-js/))
+- Hold a community vote and communication about a name for the new IPFS-in-JS implementation. ([Tracking Issue](https://github.com/ipfs/pomegranate/issues/3))
 
-#### Late Q4 (December)
+### Late Q4 (December)
 
-Double team capacity.
+#### Double Team Capacity
 
 **Problem to solve:** Currently, the IPFS-in-JS effort has less than one full-time SWE (Software Engineer) who is also splitting time with js-libp2p.
 
 **Done state:** Accepted offer for 1-2 additional full-time engineers.
 
 **Why:** Extra hands are needed for designing, planning, and executing on IPFS-in-JS. Even if we outsource development, help is needed to review and guide the development work.
 
-### 2023
+Tracking issue: https://github.com/ipfs/pomegranate/issues/6
 
-#### Early Q1 (January)
+## 2023
 
-Finalize "Pomegranate" execution plan. ("Pomegranate" is the temporary codename for the new IPFS-in-JS implementation.)
+### Early Q1 (January)
+
+#### Finalize "Pomegranate" Execution Plan
+
+("Pomegranate" is the temporary codename for the new IPFS-in-JS implementation.)
 
 - Project scope, milestones, success criteria, and communication channels are established.
 - Community can follow along and contribute to "Pomegranate".
 
-#### Late Q1 (March)
+### Late Q1 (March)
 
-"Pomegranate" "v1" released.
+#### "Pomegranate" "v1" Released
 
 - Users can add and get files.
 - Packaging, publishing, testing, CI/CD, etc. are all set up.
 
 Tracking issue: https://github.com/ipfs/pomegranate/issues/2
 
-#### Q2
+### Q2
+
+#### Drive Adoption of "Pomegranate"
 
 After "Pomegranate" is functional and users can adopt it, Protocol Labs EngRes ceases maintaining the legacy js-ipfs project.
+
+### Q3
+
+#### Support Fully Speced Delegated Routing Protocols and Endpoints
+
+While it will be possible from a connectivity perspective to make DHT queries from a browser, we expect various applications will want to still delegate out routing. [Reframe](https://blog.ipfs.tech/2022-09-02-introducing-reframe/) is a protocol for delegated routing that other IPFS implementations like Kubo have implemented. While it currently uses HTTP as a transport, it is speced and not tied to the Kubo RPC API. If/when there is a speced protocol for ambient discovery of “Limited Delegated Routers” provided by libp2p, we will support that as well.
+
+#### PL Delegate and Preload Nodes Will Be Shutting Down
+
+Given new browser-friendly p2p transports, we’ll shut down the complicated “song-and-dance” with the legacy delegate/preload nodes. This yields a simpler setup for one’s application and removes centralized infrastructure.
+
+For delegated routing, one can configure [Reframe](https://blog.ipfs.tech/2022-09-02-introducing-reframe/) endpoints. When it comes to providing content from a browser node, it will be up to developers to account for user behavior like closing tabs or laptop lids. The general recommendation is to either run your own preload node or upload content explicitly to a pinning service for providing.