Create @ipfs/specs-stewards team

[lidel]

@ipfs/specs-stewards team was created as part of #289

We need to decide who should belong to the team, sharing responsibility of triaging and reviewing improvement proposals (#289).

My initial idea is to add past/recent lead implementation maintainers from existing stewards teams, namely:

• https://github.com/orgs/ipfs/teams/w3dt-stewards/members
• https://github.com/orgs/libp2p/teams/w3dt-stewards/members
• https://github.com/orgs/ipld/teams/w3dt-stewards/members
• https://github.com/orgs/multiformats/teams/w3dt-stewards/members

Starting with a smaller group should be enough to get us started.
Over time, we will add trusted leads from other organizations maintaining IPFS implementations.

TODO

• discuss: add / remove stewards
• figure out how to automate management of the group (JSON under https://github.com/ipfs/github-mgmt/ ?)

[mxinden]

Not a strong opinion. Feel free to ignore.

Appreciate being considered here as a libp2p steward. Though I don't think I should have any special permissions. That is not to say that I am not happy to be involved, but for that involvement, why would I need permissions beyond what any other ipfs user has?

[lidel]

I have a specific rationale for this, but it is also not a strong opinion, feedback welcome!

One of the challenges around ipfs/specs is "legacy go-ipfs monoculture".
Another is "tight coupling and leaky abstractions due to same people wearing multiple hats".

A solution is including maintainers of PL's ipld libp2p implementations (js/go/rust) in the specs group.

This would keep the group diverse in more than one dimension:

1. avoids language-specific shortcuts
2. represents libraries/interfaces (ipld, libp2p, gateway, reframe) and their consumers (ipfs implementations)
3. guards abstraction layers in our stack: avoid leaky abstractions in IPFS specs, ensure data model (ipld) and networking layer (libp2p) should remain decoupled and useful on their own

It also acts as a soft forcing function to follow ecosystem evolution, keeping key stakeholders in sync long-term.

[lidel]

@b5 @dignifiedquire would like to have someone representing Iroh, to be in the loop around specs and IPIPs.
This is mostly a formality, in day-to-day this person will get group-ping for PR reviews (https://github.com/notifications?query=reason%3Ateam-mention) and that is all.

[b5]

Thanks @lidel, I'd be happy to represent Iroh.