Sprint Process?

I've been steadily diving head first into IPFS docs and am still getting up to speed. Along the way, I noticed that there is a [pre-existing weekly sprint process](https://github.com/ipfs/pm/) defined for a lot of the specific current initiatives (go, node, testing + ci, protocol + specs, etc.).

Would this be something that this team would be interested in adopting?

I think one of the benefits is it could solidify strong initial momentum and team to get things going, but it might not fit into everyone's schedule and might not be everyone's favored process. Since this is an ipfs project, I also think it might be good to stick to their existing defined processes & best practices.

Review the linked weekly sprint process in ipfs/pm/ and compare it with the initiatives named in this issue: go, node, testing + ci, and protocol + specs. The issue is complete only when the team has decided whether to adopt that process and documented the outcome; no implementation files or tests are identified.

Written by the indexing model from the issue text.