REVISED Proposal: Reduce friction and time to first successful storage and retrieval deals for new Filecoin storage clients

[terichadbourne]

This proposal suggests a path to carry on with the great work started by @andrew & @jnthnvctr's Filecoin storage attempts, addressing the issues flagged with a combination of engineering and documentation. It would also serve as a test ground for establishing a workflow for communicating and collaborating across teams within W3DT as we tackle fundamental engineering issues and documentation in tandem.

[rvagg]

I think the framing of this project should still be exploratory, even though we've had some exploratory work done (i.e. step 1 being "done" might not be quite right). The scope is potentially huge since solving it might involve touching many parts of the technology stack - i.e. it doesn't seem to be just a "the documentation isn't good enough" task.

I'm suspecting there's overlap here between the skills and interests of the dev onboarding and dev optimisation (sudo) teams . It might be something we could tackle together in some way, or divide up and treat it as educational for us and expect it to yield further TODOs (project proposals) along the way. Unless PMs (@jnthnvctr?) have confidence already that we know what needs to be solved and we can go ahead and spin off more discrete project proposals?

#12 is related in fixing some of the deal flow pain.

[alanshaw]

We have some overlap: https://github.com/protocol/web3-dev-team/pull/28

Maybe this is the super-proposal of mine.

[atopal]

@rvagg Yeah, the potential scope is very large, so it might make sense to either use this as the description of the overall desired outcome or scope more tightly. That said, documentation can cover workarounds where the implementation is not sufficient, eg recommending hosted solutions for the time being, and product changes can be on the level of "more comprehensible output of the CLI" or better default behavior.

[terichadbourne]

My latest commit (at the request of @atopal & @raulk) updates the scope of this proposal to include only documentation of current best practices, not engineering of improved processes or CLI UX. (That engineering work would take place within the scope of #12 instead.) It also adds documentation of retrieval best practices rather than focusing exclusively on the storage deal.