Add PL EngRes IPFS Stewards Roadmap (DRAFT)

[guseggert]

No description provided.

[BigLep]

Thanks for doing this @guseggert .

A few things:

1. We need to have a way for folks to leave feedback or ask question. I think the easiest way is to have an accompanying issue. Feel free to create or @reidlw can. See go-libp2p as an example: https://github.com/libp2p/go-libp2p/blob/master/ROADMAP.md
2. Can we get a table of contents (although I guess Github gives you one on the side if you click...) It's maybe just me but I find it useful to see at the top of the doc like go-libp2p, testground, etc. are doing.
3. Concerning naming/path: I think we need to do one of two things:
   1. Rename to pl-engres-ipfs-stewards/roadmap.md OR
   2. Store at the top level and rename to pl-engres-ipfs-stewards-roadmap.md
      (yes agreed it would be ideal to have a more concise way to refer to the team, but that's a separate thing to figure out.)

We can merge when comments are incorporated. I do think we need to fast follow with #94 to tie this up for now.

[BigLep]

@guseggert : I saw there are a couple of more commits. Is the main remaining thing creating the issue? I'd like to have this in its public form before EngRes roadmap presentation during LabWeek if possible please. Thank you.

[lidel]

I think its a good time to stop using "writable gateways" and focus on use case (which is onboarding data into IPFS) – thoughts?

Suggested change

	#### ⚫ Writeable Gateways
	#### ⚫ Data onboarding with HTTP POST

[BigLep]

@ReidW: now that we're back from IPFS Camp, I'd like to get this merged and some of the comments in #93 (review) incorporated.

It would also be great to see #94 be taken on.

[reidlw]

@BigLep@guseggert - I think we need to rationalize a few things:

1. Naming: So long as this roadmap is only for Kubo, we should call it the Kubo roadmap. Next level-up, we could have a roadmap for IPFS-Stewards, but that would need to include js-ipfs/pomegranate and GUI tools. Next level-up, would be a roadmap for IPFS overall.
2. Where to put roadmap: I don't think we should duplicate data, and we definitely need to put the roadmap into Github issues, which I did ahead of engres summit: https://maplight.vercel.app/roadmap/github.com/ipfs/roadmap/issues/102?view=detail. So, I think we should close this PR, and switch to using the issues-based roadmap from now on. Thoughts?

[BigLep]

Hi @wilkyr31d,

Naming

I think we need to create a name for the "Go" PL EngRes IPFS Stewards. I agree if we say its the "PL EngRes IPFS Stewards" it should include all our IPFS work, but I think it's too much if we combine our specs/kubo/js-ipfs/GUI work into a single document.

Where to put roadmap

I don't think the tool is ready yet (e.g., click-throughs don't work, don't have it on a more permanent domain). Until then, I think we can use our roadmap.md file and have each of the milestones there point to the issues you've created.

Side topic: I think most of the issues that were created in this repo (ipfs/roadmap) should ideally live in Kubo since they are Kubo specific.

[2color]

Any update on this?

[TinyTb]

A huge amount of progress has been made on the roadmap tool in the past couple weeks. The tool is now usable, and available at: https://www.starmaps.app/

It's very much in-development -- report issues here :)

[BigLep]

I'm going to close this because:

1. Don't want to set wrong expectations. "no information is better than incorrect information"
2. This needs updating to account for 2022Q4 learnings
3. Changes in the ability to hire
4. Internal huddle on how we we want to present this (e.g., markdown file like this, github issues with starmap). Don't want to be duplicating.