Sprint Sep 14

[ghost]

Sprint Goals

• ship 0.4.0

Sprint Discussions

See https://github.com/ipfs/pm#sprint-discussion-schedule

Please take notes in a separate pad, if you can, and link it here.

• infrastructure: https://etherpad.mozilla.org/wns7nqRsZa

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.

@yourhandle

@RichardLitt

• Write an issue about how to rework ipfs.io so it is more than a list of videos. If possible, draw or commit an alternative front page on a branch.
• Work with ___ to make sure that set-dns-record tool works as expected. 👍
• Create IFPS/support
• Figure out how to put IPFS repositories on IPFS. Open a discussion in the community repo for this.
• Rebuild the community page, or build a new one listing all of the repos currently in development and make sure that their internal READMEs are streamlined. Write a starlog about this once it is done, the blog needs more <3
• Review https://github.com/diasdavid/node-spdy-stream-muxer
  this one follows abstract-stream-muxer and has one request open that is, to make it return a duplex stream, which won't work till spdy-transport returns also a duplex-stream (just FYI :) ) and TY! (Cool, thanks!)
• Review https://github.com/diasdavid/node-multistream
• Review Removed the base html tag ipfs-inactive/website#14
• Review Links on command list are broken ipfs-inactive/website#2
• Close or review issues on ipfs/community
• Fix textarea scrolling on UI on composing breaks when post is longer than screen space ipfs-inactive/starlog#26
• See if I can codify how I can help manage sprints and project management better.
• Give IPFS install another test run through for ease of use.
• Start document about higher level abstraction education for IPFS to non-cryptos
• Finish job spec.

@diasdavid || @daviddias

• Refactor Swarm
  • abstract-transport
    • libp2p-tls (??)
  • abstract-connection
    • libp2p-tcp
    • libp2p-udp
  • libp2p-spdy
• Fixed bug caused by bad pattern on mDNS discovery libp2p/js-libp2p-mdns@43472a5
• Upgrade IPRS impls (ipfs-record, drs, kad-drs) depending on need for clarification on how a Record is really structured specs#24 (comment)
• abstract-peer-routing
• WebCrypto module (discussions, where to go)
• write a description for each node-ipfs module on node-ipfs repo as separate issues
• write 'what can you do' on node-ipfs-api
• merge Add replaceConf. Update go-ipfs and node-ipfs-api package versions. js-ipfsd-ctl#12

@whyrusleeping

• merge implement unwant command to remove blocks from wantlist kubo#1672
• investigate efficacy of process directory entries asynchronously  kubo#1658
• follow up on vendor commands/files outside of ipfs kubo#1648
• merge dont need blockservice workers anymore kubo#1622
• flatfs put retry PR (allow put to try again if it fails due to too many open files go-datastore#29)
  • integrate into go-ipfs
• finish private-blocks PR (ready for CR again)
• update go-peerstream in go-ipfs after last PR
• finish mfs extraction
• epoll fixes (no need for multiple epoll fds libp2p/go-reuseport#8)
• investigate udp libs, try integration
• add chunking algo to root unixfs file blocks

@jbenet

• put ipld into go-ipfs
• make libp2p go interfaces file
• decide on crypto transport
• node-ipfs repo module listings
• api docs designdoc
• car designdoc
• dkr-shp webpage
• dkr-shp improvements
• infra accounting
• libutp bindings

[jbenet]

Not sure if we can ship 0.4.0 this week but we may be able to at least get everything ready.

[daviddias]

@dignifiedquire let me know if you want to be part of the checkin this week and tell us about your developments for the electron-app stuff :) We have a ipfs-apps sprint meeting at 18:30Z https://github.com/ipfs/pm#sprint-discussion-schedule

[dignifiedquire]

@diasdavid sure, I should be able to make time for the discussion (today?) I'll happily check in, as much as I can get done

[dignifiedquire]

Started work only Friday, so it was more of a mini sprint for me, but I got through some stuff the on electron-app:

• Added hot module reloading
• Using babel and webpack for building
• Improving stability (using safer ipc variant to avoid crashes on reload)
• New design ideas (wip) [WIP] Hot reloading and redesign ipfs-desktop#43 (comment)
• ES201xify code (wip)

Progress can be viewed at: ipfs/ipfs-desktop#43

[whyrusleeping]

• merge implement unwant command to remove blocks from wantlist kubo#1672
• investigate efficacy of process directory entries asynchronously  kubo#1658
• merge dont need blockservice workers anymore kubo#1622
• flatfs put retry PR (allow put to try again if it fails due to too many open files go-datastore#29)
  • integrate into go-ipfs
• finish private-blocks PR
• update go-peerstream in go-ipfs after last PR
• finish mfs extraction (PR in progress)
• lots of work towards UDT, one more PR should do it
  • cleanup code to remove race conditions jbenet/go-udtwrapper#13
• working on a set of patches for ipns to make it work until we get ipld stuff

udt stuff was quite the time suck. But i'm pretty confident in it now

[ghost]

• [~] wip: gateway-dmca-denylist, this time for real
• added storage users for rht, mikolalysenko, davidar
• disabled docker container logging to prevent disks from filling up, as they don't get rotated
• fixed ipfs container's permissions for ipfs log files
• monitoring / prometheus fixing and tuning
  • node_exporter docker container
  • node_exporter should only export cpu, net, ram, fs
  • node_exporter should forget network interfaces that don't exist anymore (i.e. docker's veth)
• alexandria
  • discussed our gateway setup with gendale
  • cjdns peering
• peer discovery using cjdns WIP: discover peers from cjdns kubo#1316
• gateway: caching headers
• fix CORS headers for chrome CORS returning all, instead of just one kubo#1659

[daviddias]

SPRINT UPDATE

• Making progress on the Swarm revisit, right now the current version of Swarm supports multitransport, but once at a time and only if they follow the net module interface, we are changing that to make it even more cool :) - https://github.com/diasdavid/node-ipfs-swarm/issues/8
  • revisit branch https://github.com/diasdavid/node-ipfs-swarm/tree/revisit
  • abstract-transport https://github.com/diasdavid/abstract-transport
  • abstract-connection https://github.com/diasdavid/abstract-connection
  • libp2p-tcp https://github.com/diasdavid/node-libp2p-tcp
  • libp2p-spdy https://github.com/diasdavid/node-libp2p-spdy
• Fixed bug caused by bad pattern on mDNS discovery libp2p/js-libp2p-mdns@43472a5
• IPRS - Reach a conclusion with @jbenet on how to make IPRS more flexible from the validation standpoint
  • need for clarification on how a Record is really structured specs#24 (comment)
  • Key Rotation specs#31
• Made abstract-peer-routing https://github.com/diasdavid/abstract-peer-routing
• Generic Crypto module for libp2p use that is Node.js and Browser compatible
  • still very new https://github.com/diasdavid/webcrypto
  • @tomgco is making a callbacks (not promisses) interface for the browser WebCryptoAPI https://github.com/tomgco/node-webcrypto
  • Been bouncing ideas with Ian "Elliptic curve crypto in IPNS" daviddias/webcrypto#1 and reaching the conclusion that we need an abstract-crypto interface
• Descriptions for the IPFS Node.js modules that people can contribute and understand more (avoiding the ones that are more unstable) https://github.com/ipfs/node-ipfs/issues
• merge Add replaceConf. Update go-ipfs and node-ipfs-api package versions. js-ipfsd-ctl#12
• Collect conferences that we can/should participate till Feb 2016
• Got my head around ipfs-blob-store Reorangized and implementation of a basic dag store ipfs-shipyard/ipfs-blob-store#2 (we need mfs to make everything super sweet! :) )

[RichardLitt]

Update:

Summary:

I was AFK for most of the week, which I did not take into account when I planned this spring on Monday. So, I need to be better at that, and at saying before hand that I will or will not be online much. Also, I need to be careful not to overload on the sprint tasks.

I PRed a few things - go-ipfs Contribute, ipfs/support Readme. I looked at all of the IPFS issues this week and am starting to get a wider feel for the community as a whole and what we're doing, but still don't understand a large amount of the actual talk going on. This made the two reviews I did of diasdavid's modules hard, because I feel I don't have too much to add. I started https://github.com/RichardLitt/ipfs-textbook as a place for me to slowly figure out and make a document aimed at teaching people about IPFS and relevant crypto. This is mostly for me, but hopefully more people will get involved.

I worked on a few other issues, like the baseURL issue for the website. But I didn't have time to do as much as I would like, or to overhaul the community page yet.

• Write an issue about how to rework ipfs.io so it is more than a list of videos. If possible, draw or commit an alternative front page on a branch.
• Create IFPS/support
• Figure out how to put IPFS repositories on IPFS. Open a discussion in the community repo for this.
• Review https://github.com/diasdavid/node-spdy-stream-muxer
• Review https://github.com/diasdavid/node-multistream
• Close or review issues on ipfs/community
• Start document about higher level abstraction education for IPFS to non-cryptos
• Work with ___ to make sure that set-dns-record tool works as expected.
• Rebuild the community page, or build a new one listing all of the repos currently in development and make sure that their internal READMEs are streamlined. Write a starlog about this once it is done, the blog needs more <3
• Review Removed the base html tag ipfs-inactive/website#14
• Review Links on command list are broken ipfs-inactive/website#2
• Fix textarea scrolling on UI on composing breaks when post is longer than screen space ipfs-inactive/starlog#26
• See if I can codify how I can help manage sprints and project management better.
• Give IPFS install another test run through for ease of use.
• Finish job spec.

[jbenet]

Sprint Update

This week I got stuck catching up with an insanely large comm backlog:

• lots of ipfs mail
• issue discussions
• PRs/CR
• discussion calls
• design/impl discussions with @whyrusleeping
• design discussions with @daviddias
• org/logistical todos
• visited consensys (who are using IPFS) - http://cryptogeeks.com/ipfs-consensys-planing-future
  Did not expect how much of a time sink all this would be.

Of the items I listed I only got through one :(

• decide on crypto transport

[amstocker]

Sprint Update

python-ipfs-api:

• pydoc documentation
• make readthedocs.org page
• make it easy to integrate python-ipfs-api into async environment
• make filestreaming chunk large files/multiple files
• python 3 support
• testing framework
• tavisci setup

(otherwise python-ipfs-api is pretty much stable)

other:

• python-multiaddr
  • make testing framework
  • python 3 support
  • feature parity with go-multiaddr/node-multiaddr