Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Sprint L #13

Closed
24 of 55 tasks
jbenet opened this issue Jun 16, 2015 · 5 comments
Closed
24 of 55 tasks

Sprint L #13

jbenet opened this issue Jun 16, 2015 · 5 comments

Comments

@jbenet
Copy link
Member

jbenet commented Jun 16, 2015

Sprint Goals

  • go-ipfs protocol transition
  • shorten bug-list
  • get electron-app stable enough to release

Sprint Discussions

2015-06-15:

2015-06-16:

  • 19:00Z (12:00 PDT) apps on IPFS - electrum host
  • 19:30Z (12:30 PDT) data structures

Sprint Deliverables

  • Add yourself below, that way we only have people listed who are really in the sprint
  • Add links to issues down here. Only add things you can finish this sprint.

@jbenet

@whyrusleeping

@diasdavid

@krl

  • finish electron app html menu
  • starlog proposal

@lgierth

@chriscool

@rht

@kbala

  • collect metrics from simulation
  • add more control over connections in bitswap testnet

@harlantwood

@dylanPowers

@cryptix

triage - anyone can pick these up

@daviddias
Copy link
Member

I mentioned this in previously meetings, by just realized I never wrote it down. I'm during today and tomorrow on MediterraneaJS, which means I won't be able to do much. Also attending the Sprint meeting will be hard as the Wifi is pretty much broken (currently on 3G Roaming).

Would it be good to sync up Wed/Thu on node-ipfs?

Thank you

@whyrusleeping
Copy link
Member

etherpad for next sprint: https://etherpad.mozilla.org/4LhJKyOF3j

@jbenet
Copy link
Member Author

jbenet commented Jun 22, 2015

Hey @diasdavid -- this was notice enough, thanks! and yeah let's talk node-ipfs tomorrow or later.

@daviddias
Copy link
Member

@jbenet cool, thank you. Meantime I'll be testing spdy-transport against spdystream and making the node-peerstream wrapper, while making the remaining tests that Indunty needs for spdy-transport.

Need to have a convo about the rest of the network elements to make it work. Essentially if you could point what stuff from here: https://github.com/ipfs/specs/tree/master/protocol/network is on go code and where, it would work :)

That and of course, continuing the DHT, spec would be appreciated, but I believe that I'm getting the hang of how it was implemented by continuously reading the code and making questions.

@ghost
Copy link

ghost commented Jun 22, 2015

Essentially if you could point what stuff from here: https://github.com/ipfs/specs/tree/master/protocol/network is on go code and where

👍 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants