Sprint Sep 28

[ghost]

Sprint Goals

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.

• main pad: https://etherpad.mozilla.org/juEv7EcG5l
• node-ipfs notes: https://etherpad.mozilla.org/lm3txgSGbZ
• go-ipfs notes: https://etherpad.mozilla.org/FQE1OWzp6Q
• ipfs-app notes: [WIP] Hot reloading and redesign ipfs-desktop#43 (comment)

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

@noffle

• ipget (https://github.com/noffle/ipget)
  • tests + travis ci
  • support godep
  • smarter default filename when given a x/y/z path
  • logging with github.com/Sirupsen/logrus
  • plan out work toward 'ipfs get' feature parity

@jbenet

• make issue about ipfs-update
• multiaddr-net modularizing Pluggable design multiformats/go-multiaddr-net#7
• exo-transport design doc
• put ipld into go-ipfs
• figure out dkr-shp next steps
• go-ipfs roadmap
• blockstore intergration / onename profiles
• ascribe catchup
• whittle down open PRs in go-ipfs
• @willglyn's go-ipfs paths PR
• @mildred's go-ipld PR
• start ipfs-api repo for spec, docs, tests.
• define multikey standard
• HK Blockchain Workshop
  • Smart Contracts + IP Working Group doc work
  • IoT Working Group doc work
• re-record computer from DTN
• CR + land mfs/files - implement ipfs files command kubo#1769
• CR + land IPNS patches - Ipns/patches kubo#1739
• CR + land utp patches - Feat/utp kubo#1789
• review growing libp2p spec
  • discuss questions with @diasdavid

@amstocker

python-ipfs-api:

• [~] api method documentation (almost done)
• readthedocs.org page
• easy integration with async environments
• better file streaming
  community:
• start python/ipfs hangout on monday sprints

@mappum

• jbenet/vinyl-fs browser changes
• create PR from jbenet/vinyl-fs to gulpjs/vinyl-fs (maybe)
• inpm alternate install types (dupe, link to local registry)
• ship inpm initial release
• fix cube server expiration calculation
• basic cube-web PoC for designer

@RichardLitt

• Add -contribute.md files to community list. Do Go and Node. go-ipfs#1734
• Resolve issues on ipfs/community as much as possible. Add open issues to next week's sprint.
• Write 300 words~ on how I can codify how I can help manage sprints and project management better.
• Give IPFS install another test run through for ease of use. Minimum: Getting started page.
• Actually finish job spec. Google what these should look like, too.
• Take a crack at node-ipfs-api docs! Minimum: 1 hour.
• Add update-or-create to dnslink-deploy dnslink-deploy#5.
• Mention ipfs/support on the google groups email list.
• Make sure the google groups list is advertised in the appropriate places.
• Work on IPFS-Textbook. Deliverables: A read through and edit; close all PRs and issues; update glossary.
• Help @jbenet with email lists. (logistics)
• Talk to @jbenet about IPFS google apps so that I can create the calendar community#35
• PR the Readme standards and guidelines.
• Build a README parser and standard checker. Test IPFS repositories with it.
• Write a Starlog about Readme standards and all repositories.
• Close gencmdref issue for the website go-ipfs#1735
• Setup keybase.io, and take a look at the BookReader issue as payment of that debt to @davidar
• Add node-ipfs-api node-ipfs question to ipfs/faq.

@lgierth

• make gateway-dmca-denylist accessible at ipfs.io/refs/lists/denylists/dmca
• make sure infrastructure is documented well
• hand off to whyrusleeping jbenet richardlitt cryptix
• chill

@diasdavid

• kick of the tires on libp2p in go
• ipsurge tool

@dignifiedquire

• init screen
  • advanced options tab
  • move path into advanced
  • add key choice into advanced. (make algo a dropdown, with only RSA but say "ECC and more coming soon". it's an important detail)
• menu screen
  • logo in menu title [ ] IPFS (Ref Vectorized & Outlined Versions ipfs-inactive/logo#6)
  • hide settings for now
  • figure out if "console" and "browser" can be more clear (a bit confusing atm)
• file upload
  • re-enable file upload
  • add progress bars for file upload

@rht

• integrate ipget into gx
• more ipfs add test cases (--trickle, --chunker)
• ipfs add benchmark (vs cp vs rsync vs tar vs tar z vs git vs ?) -- sorry, benchmark almost always means apple vs orange, but can still be useful
• ipfs object cache $hash / ipfs object get --cache-only $hash? i.e. store a particular hash into blocks without outputting to $PWD or stdout. Useful for partial backup of parts of a huge node, pre-ipfs-cluster
• git on ipfs

@whyrusleeping

• ipns merged
  • old record fix
• mfs api redux
• chunking/layout algorithm into unixfs roots
• UDT into go-ipfs
  • udt into go-multiaddr-net
  • refactor multiaddr-net
    • waiting on discussion for interfaces
• more stats in repobench
• reduce dialing concurrency
• chat with blame about scaling provides

[jbenet]

• node-ipfs notes: https://etherpad.mozilla.org/lm3txgSGbZ
• go-ipfs notes: https://etherpad.mozilla.org/FQE1OWzp6Q
• ipfs-app notes: [WIP] Hot reloading and redesign ipfs-desktop#43 (comment)

[jbenet]

Reminder to add things to etherpad -- @whyrusleeping @lgierth @mappum @RichardLitt @dignifiedquire @davidar @chriscool @rht @diasdavid

[jbenet]

hey @diasdavid @whyrusleeping -- reminder: your things o/ o/

[daviddias]

sorry, just added :)

[jbenet]

@jbenet's end of sprint update

This week i had a bunch of small things. Lots of CR upkeep, figuring out various issues, lost of discussions with people.

• make issue about ipfs-update -- finishing this up, will post in a bit.
• multiaddr-net modularizing Pluggable design multiformats/go-multiaddr-net#7 -- still some figuring out to do there.
• [~] exo-transport design doc -- working on this
• put ipld into go-ipfs -- not yet
• [~] figure out dkr-shp next steps -- working on this.
• go-ipfs roadmap - not yet. need to do this.
• ascribe.io catchup -- figuring out integration points
• whittle down open PRs in go-ipfs
• @willglyn's go-ipfs paths PR
• @mildred's go-ipld PR
• start ipfs-api repo for spec, docs, tests. -- need to do this still.
• define multikey standard -- need to do this still
• HK Blockchain Workshop prep
  • Smart Contracts + IP Working Group doc work
  • IoT Working Group doc work
• re-record computer from DTN
• CR + land mfs/files - implement ipfs files command kubo#1769
• CR + land IPNS patches - Ipns/patches kubo#1739
• [~] CR + land utp patches - Feat/utp kubo#1789
• review growing libp2p spec
  • discuss questions with @diasdavid
• ship 0.3.8 -- we haven't done this.

[ghost]

• [~] make gateway-dmca-denylist accessible at ipfs.io/refs/lists/denylists/dmca gateway: add /refs/* infra#95
• [~] make sure infrastructure is documented well
• [~] hand off to whyrusleeping jbenet richardlitt cryptix
• chill
• instrument api and gateway HTTP handlers for Prometheus daemon: instrument the gateway and api HTTP handlers kubo#1799
• fix pluto's private key and peerid config: update pluto's peerID kubo#1748
• gc'd the gateways before the techcrunch article hit

[dignifiedquire]

• [~] Welcome Screen (IPFS Electron App)
•  File Upload (IPFS Electron App)

[RichardLitt]

Etherpad for the next sprint, #36: https://etherpad-mozilla.org/sprint-36

[chriscool]

Some very small fixes in sharness tests:

• Fix test cmp args kubo#1792
• Improve t0120 kubo#1786
• t0051: swap test_cmp arguments kubo#1783
• t0081: swap test_cmp arguments kubo#1784
• Improve t0240 kubo#1781

And improved shellquote():

• Shell quote kubo#1772

[daviddias]

SPRINT UPDATE

Apologies for missing today's checkin, I thought I would be able to do it in Newark Airport, but the airport was impressively full today and after waiting in all the queues, had to run to my gate.

My main focus for this past week was working on a interopable go-libp2p and get ipsurge off the ground.

• Work on getting more stuff documented on libp2p libp2p spec specs#19
• Discuss with @jbenet some very important details about libp2p architecture and agree on how transports are architectured
• Got formally invited to lecture a Post Graduation course on "Programming for the Web" (woot:))
• schedule travel plans for &yetConf
• ipsurge https://github.com/diasdavid/ipsurge https://github.com/diasdavid/ipsurge-preview

Usage: ipsurge COMMAND [OPTIONS]

Available commands:

browse    Open your application in a browser
init      Initialize a ipsurge project
preview   Preview your application through a collection of snapshots
publish   Publish your project
versions  Check each version published 

• deploy my website with ipsurge and DNS hack http://ipfs.daviddias.me/
• WebRTC WG mails and review stuff (worked a bit more on the article distilling WebRTC)
• libp2p in Go
• give some feedback on Cube
• submit talks for 32c3
  • Parasitic Computing for building a distributed computing platform with Volunteered Cycle Sharing
  • ipsurge
  • libp2p - A multi protocol approach for an upgradable network stack

[davidar]

@davidar update: https://github.com/ipfs/apps/issues

[hackergrrl]

• ipget (https://github.com/noffle/ipget)
  • tests + travis ci
  • support godep
  • smarter default filename when given a x/y/z path
  • logging with github.com/Sirupsen/logrus
  • plan out work toward 'ipfs get' feature parity

I chatted with @whyrusleeping about logrus and logging for ipget, and decided against it: the logging isn't very human friendly, and CLI tools like this are primarily talking to humans. go-logging looks nice, but I think just writing to stderr is sufficient for this tool.

I didn't get to delve very deeply into testing, but I got a wealth of information about how current ipfs get testing works with sharness, which I'll tackle this week.

[rht]

@noffle If you git blame the code, the one who put logrus into almost all logging was me, sorry.
One reason against logrus that I know of is that logrus doesn't tell line number when an err happens (a much requested feature as in sirupsen/logrus#63).
Though it would be more helpful if you elaborate on "the logging isn't very human friendly", lest the back-and-forth switching between the two libs.
(will fix the composite files PR later)

[sirupsen]

I chatted with @whyrusleeping about logrus and logging for ipget, and decided against it: the logging isn't very human friendly, and CLI tools like this are primarily talking to humans. go-logging looks nice, but I think just writing to stderr is sufficient for this tool.

Curious what you mean here? You may want to write a custom formatter if it's to show users and not the developers.

[whyrusleeping]

@sirupsen its not really that its not 'human friendly' its just information overload to use a full fledged logging library for an app that has functionality similar to 'wget'.

While youre here... any news on the filename/line-number front? logrus is definitely more flexible, but the lack of line numbers makes debugging more difficult for me (prompting the discussion about switching back to go-logging)

[hackergrrl]

Curious what you mean here? You may want to write a custom formatter if it's to show users and not the developers.

Jeromy did a better job of clarifying than I did -- sorry about that. I didn't know about the line number feature-want, but yes, my qualm was with logrus being heavy (creating a custom formatter that outputs essentially just what fmt.Fprintf(os.Stderr, "...") does) in relation to the tininess of this tool. Having line numbers (maybe behind a -d debug switch) would be nice, though.

[sirupsen]

@whyrusleeping I've never needed the functionality myself and noone has ever opened a convincing PR to do it that works in every situation (see this comment). I'm very surprised noone has written a hook for it, it doesn't necessarily have to be in core.

[ghost]

Let's move this to an appropriate issue in another repo