Closed whyrusleeping closed 6 years ago
Hey Everyone,
I'm sorry for missing the planning call. I should've been there. I've been overwhelmed with other work and failed to wake up-- i'm sorry. That said, I don't think the lack of my presence is the reason for the issues here. Faults like that will happen and we need to be fault-tolerant and proceed through them.
The bigger issue here -- and why the call went the way it went -- is that, collectively, we had dropped this thing, and we don't really know what we're doing. We have not taken the time to craft product, nor synthesize all the available comments into a coherent product. (Product Development).
The PMing role -- which often involves that Product Development or at least surfacing and synthesizing others' work -- fell to @whyrusleeping late in the game, who has also been extremely busy with other things and has not had the time required to do greatly here. The result is that the call ended up with fishing for things vaguely related to do, and the action plan is very far away from the original goals set for this sprint in early January. We also need @whyrusleeping tech-leading here, which is a hard and time-consuming role. I voiced this a few days ago: I doubt that Tech-leading, being one of the lead Implementors, Project Managing, AND Product Developing, is a feasible thing, if we want this sprint to be successful. As amazing as @whyrusleeping is, there's just not enough hours in a day. (thoughts @whyrusleeping?)
As the person who called this sprint into being, I was the de facto product owner. But this was not quite explicit, and I did not have the time to do the product development necessary. Regardless, I should've either found someone else or do it. So I dropped that ball, which I wasn't even aware I was dropping until a couple days ago.
Here are a bunch of threads relevant to this product (thanks to everyone who surfaced these, or contributed thoughts):
And then there is the vision & goals for the "InterPlanetary Lab" (what this sprint is here for), which i've discussed with many people in this sprint, but has not yet been written up. (For those familiar with Planet Lab, imagine: Planet Lab for IPFS, with all sort of hardware around the world.
The goals I had for this sprint were:
So I went ahead and finally did some of the product development required for this sprint. I made a designdoc like thing, and a video discussing it. it's here:
This is not everything we need, of course. We still need tighter connection to user stories. Still, I would like people in this sprint to:
IF we decide to go for it, we can:
Taking stock of our options, two others appear:
I may be ok to do (2) if we decide not to do the proper test lab.
But I think we should go for the test lab. It's incredibly important for the continued success of everything we're doing, and it's going to level up our tech dramatically. If we do it, I can commit to a daily standup (except Thursday) and to guiding the Product Development, if @whyrusleeping can handle big part of the Lablet implementation & Tech Leading (making sure everyone can do what they need to do, and guiding people through the implementation), someone else (@victorbjelkholm maybe, since we had discussed it as a possibility?) could handle the Project Management.
Orchestration of processes
Experiment with testing
Testing Setup -- Job bundle and Results bundle
Documentation
@jbenet I have copied relevant parts of your notes to a sprint objective document here: https://github.com/ipfs/test-lab/blob/master/sprint-objectives-2-27-2017.md.
Tentatively, I think we could create the following issues to be completed during this sprint:
I believe these could happen to some degree in parallel. The actual deliverable seems a bit vague however.
InterPlanetary Test Lab Planning Call
Video recording of the call
Participants
Goal
Jenkins works reliably for standard go-ipfs CI
Infrastructure + code in place for large scale network tests
Kubernetes deployed and able to run tests based on commits
Actionables: