Repo and process cleanup (Launchpad cohort v5 edition)

[BigLep]

Background

Some Launchpad v5 members want to do spec cleanup. Below is an attempt to capture some of the current problems they could help solve.

This should likely be broken into multiple discreet issues that can be actioned/completed independently. I'm creating a issue right now to capture problems/ideas, and then we can break this down.

Problems to solve

1. General issue cleanup. We have 80 open issues in the repo. Many are years old. We should go through them and for any that are still relevant we set a priority, size, and next steps.
2. We're missing a summarized view of the specs with extra metadata about them. For example, https://github.com/ipfs/specs/blob/main/README.md gives a list but it would be nice to see in a table form extra metadata like:

• Spec status
• Associated IPIPs
• When last updated
• Which implementations implement which specs (or at least have a way for this to be captured)
• Which issues are open about the spec

3. IPIPs are the way to make changes to a spec. We don't have a clear way to see what IPIPs are in progress, who is committed to looking at them, when they were last updated, whose court the ball is in.
4. No reporting out on what happened in the specs repo the last week/month (new IPIPs, which IPIPs were commented on, which IPIPs landed or which specs got updates).
5. The specs aren't exposed with the rest of our IPFS documentation at docs.ipfs.tech. It would be ideal to have a way to slurp them over and present them there, at least the summary/table view.

[BigLep]

@lidel : I created this issue in preparation for a call with @reidw and @p-shahi about what they may do for launchpad for here and libp2p/specs. Feel free to add additional or correcting comments. I expect @reidw will want to get your input/suggestions as well.

[lidel]

Thank you @BigLep!

@ReidW since this is a bit more work than one could complete before Launchpad end, my initial idea is to do focus on bringing some visibility into IPIPs (improvement proposals) in flight: something we could use during IPFS Implementer Sync calls to see new IPIPs, track progress of existing ones, and time-box decisions when the content of IPIP is finalized.

Feel free to ping me on Slack / schedule sync time call to chat / brainstorm on this.

[p-shahi]

@lidel @reidw Please add me to meeting too