IPFS Ignite Roadmap - 2022->2023

[SgtPooki]

eta: 2023-12-31

description:
Roadmap planning for the IPFS Ignite team (ipfs-gui under IP Stewards in the EngRes org)
You can read more about the original roadmap planning discussions at #102

Tasks

Preview Give feedback

1. IPFS Desktop and Webui are decoupled from js-ipfs #107
   3 of 4
   P1 dif/medium effort/days +3
2. IPFS Desktop and webui add WebTransport and DAG CAR support #109
   starmaps +1
3. IPFS Desktop and WebUI can keep pace with Kubo feature development #111
   1 of 2
   starmaps +1
4. IPFS Desktop and Webui can handle display of large CID content #113
   starmaps +1
5. NodeJS Active LTS 18.x updates #99
   P0 dif/medium effort/days kind/maintenance starmaps status/ready +6
6. IPFS GUI & Tools Metrics standardization #117
   starmaps +1
   
7. IPFS Companion UX Overhaul & Revamp #118
   starmaps +1
8. IPFS Companion Manifest V3 update #112
   0 of 1
   P0 mv3 +2
   
9. Starmaps.app roadmapping tool V0 Launch #119
   starmaps +1
10. Starmaps.app roadmapping tool V1 Launch #120
    starmaps +1

[SgtPooki]

2023-02-16

Roadmap adjustments and justifications

Note that below is just a proposal, and the changes have not been reflected in the issue description. I will update the description once we have alignment.

Remove

• chore: Dependency updates ipfs-webui#1965 - I feel like we can make progress on this as we progress on other items. We have already made a huge dent in this with migrating webui to kubo-rpc-client (feat: ipfs-http-client -> kubo-rpc-client ipfs-webui#2098).
• Diagnostic tooling overhaul #115 - This task is tracking some really cool and needed work to ensure devs have a great experience, but this doesn't feel as vital as our already large list of tasks to keep below.
• Support punchr experiment ipfs-desktop#2310 - Not as hard hitting as others, doing it "the right way" requires significant effort
• Public Gateway Checker reskin #110 - public-gateway-checker is our 3rd/4th most used project and I feel like this would be exciting for users, but may not fit with the rest of the work we have to do this year
• IPFS Desktop startup improvements #108 - while improving the startup experience for users is something I think will improve UX significantly, I think we already have enough work and can address this soon after we hit the other important items.
• Peers Map V2 — IPFS Desktop & WebUI #116 - building out peers-map as an isolated component could help with chore: Dependency updates ipfs-webui#1965 by reducing the breadth of conflicting dependencies in webui, but would increase our team's maintenance burden

Keep

• IPFS Desktop and Webui are decoupled from js-ipfs #107 - doing this reduces the scope and complexity of a lot of other issues and allows us to deliver a more consistent experience for our users.
• IPFS Desktop and webui add WebTransport and DAG CAR support #109 - CAR files solve a lot of problems for users, and webui+desktop users are not currently benefiting from CAR files.
• IPFS Desktop and WebUI can keep pace with Kubo feature development #111 - Provide users a stable experience across our ecosystem by facilitating consistent and up-to-date feature support and parity across webui, desktop, and kubo
• IPFS Desktop and Webui can handle display of large CID content #113 - Not displaying any subset of CIDs is a critical bug and reduces the trust of our users.
• NodeJS Active LTS 18.x updates #99 - We have to do this by Sep 2023 to ensure we don't end up in a larger mess of tech-debt.
• IPFS GUI & Tools Metrics standardization #117 - done
• IPFS Companion UX Overhaul & Revamp #118 - As the project with our largest userbase, revamping the UI for ipfs-companion will provide the largest impact.
• IPFS Companion Manifest V3 update #112 - ipfs-companion has our largest userbase across all our projects, by a large margin, and not doing this will make the extension unusable.
• Starmaps.app roadmapping tool V0 Launch #119 - done
• Starmaps.app roadmapping tool V1 Launch #120 - done

---

@whizzzkid, a few questions before we ping Steve.

• do you think the above makes sense for the two of us over 2023?
• Does this allow us time to help with Helia work? What about general maintenance and existing bugs?
• If you had to add any items to "keep" what would you add that you think we need to do this year?
• If you would remove any one/two items from the "keep" list, which ones would you remove?
• You're already project lead on the companion MV3 work, are there any other tasks you want to take?
  • Any you want to hand off, or that you really dont want to take on?