Sprint January 5th

[RichardLitt]

Sprint January 5th

Sprint Goals

TBD

Sprint Discussions

Schedule

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

Endeavour	Lead	Time (PDT - UTC/Z - CET)	Pad
Apps on IPFS	Juan Benet	10:30PDT 18:30Z 19:30CET	https://public.etherpad-mozilla.org/p/ipfs-jan-5-apps-on-ipfs
api	Richard Littauer	11:00PDT 19:00Z 20:00CET	https://public.etherpad-mozilla.org/p/ipfs-jan-5-api
libp2p	David Dias	11:30PDT 19:30Z 20:30CET	https://public.etherpad-mozilla.org/p/ipfs-jan-5-libp2p
js-ipfs	David Dias	12:00PDT 20:00Z 21:00CET	https://public.etherpad-mozilla.org/p/ipfs-jan-5-js-ipfs
go-ipfs	Jeromy Johnson	12:30PDT 20:30Z 21:30CET	https://public.etherpad-mozilla.org/p/ipfs-jan-5-go-ipfs

January 6th, Wednesday

Infrastructure has been moved to Wednesday due to @lgierth not being able to make Tuesday.

Endeavour	Lead	Time (PDT - UTC/Z - CET)	Pad
infrastructure	Lars Gierth	11:00PDT 19:00Z 20:00CET	https://public.etherpad-mozilla.org/p/ipfs-jan-6-infrastructure

Please add the Agenda to the Pad before the endeavour sprint starts.

Sprint Deliverables

• Add your tasks below in a comment, 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.

---

Before edit: Is it ok if we switch the sprint to Tuesday this week, so that @jbenet can make it? Please let us know here.

[dignifiedquire]

Fine with me

[kyledrake]

That works better for me too, I'm heading back on Monday.

I'll be visiting my grandma all of tuesday (she's turning 80) -- we can do infrastructure on wednesday?

[daviddias]

SGTM :)

[RichardLitt]

@lgierth Infrastructure on Wednesday sounds fine to me. Same time?

[RichardLitt]

Alright. Sprint officially moved to January 5th.

[daviddias]

Apps on IPFS

Lead: @jbenet, @dignifiedquire

Agenda

• registry-mirror
• waiting on 0.4.0 rc-1
• python-ipfs-api
  • needs to get updated to know how to use the Files-API
  • unblock Tahoe-LAFS IPFS Storage Driver notes#93
• webui
• Release Process Discussion notes on WebUI release process from Dec 21 ipfs-webui#167
• station
• plan for 1.0.0
• bundle IPFS daemon + js-ipfs-api to avoid avoc of version incompatibility (also use $HOME/.ipfs-station as default repo)

You have 30 minutes for this agenda, 5 minutes before the meeting ends, consider moving the remaining items to a github discussion thread so that all the other sprint meetings can start in time.

Participants

• @jbenet
• @whyrusleeping
• @RichardLitt
• @diasdavid

Notes

• registry-mirror plans
• post install script
• Tahoe-LAFS using IPFS as a Storage Backend
• Tahoe-LAFS IPFS Storage Driver notes#93
• webui
• release channels
• Discussion notes on WebUI release process from Dec 21 ipfs-webui#167
• match webui to API versions
• station
• bundle and ship 🚢

TODOs:

• ask py-ipfs team to help get python-ipfs-api updated
• outline pros of tahoe/ipfs integrations
• pick up tor+ipfs work (cc david415)
• latest vs stable webui comments (@jbenet) in Discussion notes on WebUI release process from Dec 21 ipfs-webui#167

[daviddias]

IPFS API

Lead: Richard Littauer

Agenda

• API spec and API functionality disparity API spec and API functionality disparity ipfs-inactive/http-api-spec#14
  "It's hard, because I'm not always sure whether something is either not fully specified in the CLI, not available as an easy curl request and I can't make it work, not available at all in go-ipfs (but it should be), or simply something that shouldn't be in the API (why would you want a daemon to run, for instance?). I'm still not sure how to adequately answer this question for these cases."
• Moving to Specs Repo Move the API specs into the Specs repo ipfs-inactive/http-api-spec#11
• Adding curl to descriptions Added more documentation ipfs-inactive/http-api-spec#13 (comment)
• Code Review in general Added more documentation ipfs-inactive/http-api-spec#13 (comment)

You have 30 minutes for this agenda, 5 minutes before the meeting ends, consider moving the remaining items to a github discussion thread so that all the other sprint meetings can start in time.

Participants

• @jbenet
• @whyrusleeping
• @RichardLitt
• @diasdavid

Notes

• CR the API PR Added more documentation ipfs-inactive/http-api-spec#13 (priority)
• move to specs repo
• add curl to descriptions
• Add possibility to have mult langauges (multilang or multisource) for each test case
• add tests
• Move into another branch for spec, current will be in main branch
• @chriscool: see if we can get sharness test for curl
• Go through and standardise formatting for go-ipfs helps
• Make sure headers and everything is cool

[daviddias]

libp2p

Lead: David Dias

Agenda

• go-libp2p
• has been factored and vendoring works nicely now! :D
• swarm example
• interface bikeshedding
• https://github.com/diasdavid/js-libp2p-swarm#usage
• https://github.com/diasdavid/interface-transport
• https://github.com/diasdavid/interface-connection
• https://github.com/diasdavid/interface-stream-muxer
• https://github.com/diasdavid/interface-record-store (less urgent)
• https://github.com/diasdavid/interface-peer-routing (less urgent)
• transports
• utp
• https://github.com/diasdavid/utp
• https://github.com/anacrolix/utp
• transport: µTP libp2p/js-libp2p#7
• curveCP crypto channel: curveCP libp2p/js-libp2p#10
• webrtc
• wrtc is broken (still)
• new endeavour to make a full JS impl (awesome!) https://github.com/nickdesaulniers/node-rtc-peer-connection
• connection upgrades
• tls
• secio
• Tahoe-LAFS and libp2p
• Tahoe-LAFS Networking Layer (named 'foolscap') and libp2p  notes#94
• extra
• does anyone have any input on CurveCP? crypto channel: curveCP libp2p/js-libp2p#10

You have 30 minutes for this agenda, 5 minutes before the meeting ends, consider moving the remaining items to a github discussion thread so that all the other sprint meetings can start in time.

Participants

• @jbenet
• @whyrusleeping
• @RichardLitt
• @diasdavid

Notes

• vendor go-libp2p for 0.4.0
• protobuf is huge, but we can have a -lite version just for JS (check Mathias version)
• roadmap now is to get swarm to interop, then Peer Routing interop
• secio is going to be deprecated, no need to implement in JS
• the first CurveCP implementation, incorporated into the Networking and Cryptography library (NaCl), entered public alpha testing on 21 February 2011
• write captain.log

[daviddias]

js-ipfs

Lead: David Dias

Agenda

• data-importing
• spec DEX specs#57
• js-ipfs-data-importing https://github.com/ipfs/js-ipfs-data-importing
• bitswap
• how to support IPLD and protobufs? (specifically, on the wire?)
• discussion track: bitswap js-ipfs#17
• repo https://github.com/ipfs/js-ipfs-bitswap
• init init js-ipfs#42 (spec it out)
• Itemsize things on the levelDB repo Document on the IPFS Repo Spec, the things we store on Datastore js-ipfs-repo#21

You have 30 minutes for this agenda, 5 minutes before the meeting ends, consider moving the remaining items to a github discussion thread so that all the other sprint meetings can start in time.

Participants

• @jbenet
• @whyrusleeping
• @RichardLitt
• @diasdavid

Notes

• data-importing
• tar importer and not chunker
• we should be able to do perf benchmarks
• dedup tests
• linux kernel
• npm modules
• .app example
• bitswap
  IPLD spec WIP: IPLD spec specs#37
• WIP: IPLD spec specs#37 (comment)
  implement in JS the same thing that bitswap does in go currently
  in 0.4.0 add multicodec on the wire on bitswap (@whyrusleeping to check this)
• kv on top of the MerkleDAG (like the files-api) (discuss)
• write captain.log

[daviddias]

David Dias TODO

• js-ipfs
  • js-ipfs (cli + http api)
    • /block
    • /bootstrap WIP - Bootstrap feature js-ipfs#45
    • /config
    • /id ID impl + tests (core+api+cli) js-ipfs#44
    • /version version js-ipfs#43
  • js-ipfs init
  • js-ipfs-data-importing
    • fixed-size-chunker Fixed Size Chunker ipfs-inactive/js-ipfs-unixfs-engine#1
  • js-ipfs-repo
    • fix overloaded function there was an overloaded function added js-ipfs-repo#22
  • bitswap
    • work towards feature parity with go-ipfs first (protobufs style)
  • CR Improving test coverage multiformats/js-multistream-select#6
• api documentation
  • update the readme description ipfs-inactive/http-api-spec#18
• libp2p
  • utp
  • interop go-js swarm (with tests -> libp2p-ci)
• npm on ipfs
  • update install process with 0.4.0 rc-1
• webui
  • CR https://github.com/ipfs/webui/pull/166/files
• specs
  • CR API Spec Add Add Group add ipfs-inactive/http-api-spec#17
• extra
  • Copenhagen IPFS Meetup

Note: Due to traveling to 3 countries during this Sprint and the fact that it is starting one day late, my predictions are probably off off

@lgierth TODO

• 0.4.0
  • v04x.ipfs.io and v03x.ipfs.io
  • more v03x nodes (3 out of 8 now) Migrate more bootstrappers to dev040 ipfs-inactive/ops-requests#3
  • discuss migration plan with users
  • have ipfs.io resolve both v03x and v04x (whichever responds success fast)
• infrastructure
  • hetzner SSH post-mortem ipfs/ops-private#2
  • decomission sirius Deprecating sirius and castor hosts infra#134
  • project-repos.ipfs.io dns Point project-repos.ipfs.io to GH Pages ipfs-inactive/ops-requests#9
• wishlist
  • set up buildbot worker for Tahoe-LAFS (didn't hear back)

[dignifiedquire]

@dignifiedquire Todo

Webui

• More tests
• CR contributions
• Initiate new distribution setup
• Work on the new design

Distributions

• Add build step for the new site
• Finish missing design implementations
• Ship it

[RichardLitt]

go-ipfs

Lead: @whyrusleeping

Agenda

• release process
• create a concrete plan for what has to happen during a release, things like:
• notify users with new features, bug fixes, etc)
• always make a release candidate so that all the client libraries can be upgraded accordingly
• write this process on the go-ipfs API
• sharding discussion
• Sharding - unixfs support for large directories specs#32

You have 30 minutes for this agenda, 5 minutes before the meeting ends, consider moving the remaining items to a github discussion thread so that all the other sprint meetings can start in time.

Participants

Notes

fix deadlock
more speed!

0.3.11 RC-1

0.4.0 release

After sprint meeting is finished, create the respective action items on the Github sprint issue