Meeting: 07-Feb-2017

[flyingzumwalt]

dat-jawn Call 07-Feb-2017

Participants:

• @flyingzumwalt
• @mels065
• john james
• @munadm

Agenda

Tools Orientation

• hackmd.io - orientation
• Waffle Board https://waffle.io/codeforphilly/ipfs-switchboard

Review Issues

We reviewed the issues in the Waffle Board https://waffle.io/codeforphilly/ipfs-switchboard

• If you haven't done the work listed in the Whole Team Prep Tasks issue, please do it for next week
• Matt's still got some work to do on User Stories in Write up Initial User Stories #2
• @munadm had some great observations about publishing patterns. Hw will add info and links to Research Publishing Command Tools #3. @flyingzumwalt encouraged him to also look into IPNS for this.

Plan work & Make Assignments

The Application

We walked through ipfs/station and observed that it's actually a very simple electron app that just does 2 things:

• Provides a menu bar icon with some controls for starting & stopping ipfs
• Links to the webui which is running with ipfs. The code for the webui is actually a separate code base at ipfs/webui.

The webui code base is a reactjs application.

We are going to imitate this pattern, making a reactjs application that provides the UI of ipfs-switchboard. We will then make a modified version of ipfs/station that links to our switchboard app instead of the default ipfs webui.

@mels065 will set up the skeleton of the reactjs application (issue #5)
When he's done with that, he's going to take a stab at creating mockups of the user interface. (#6)

Mockups

If you have time available, feel free to take a stab at #6 also so we can compare mockups next week.

Finding which nodes are holding a hash

ipfs-cluster is already being worked on, so we don't want to go overboard with tooling to coordinate the network of nodes that are holding a dataset. Instead, we will focus on simple tooling that lets you find see which other nodes are holding the dataset. This lets us build the UX around seeing which peers are helping you hold data, and see your role in that network. @munadm is working on a bit of this in #8