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.

[ghost]

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

[ghost]

@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

[RichardLitt]

To Do

Minimal assignment:

• Sprint Management
• Write the weekly roundup; launch it.
• IPFS API
  • Split into current functions master branch and expected spec branch.
    • Add a link to the api from the specs repo
  • Add curl commands to all method descriptions
  • Check all responses have maximal entries
    • Log any errors in go-ipfs
  • Standardize formatting for ipfs --help entries, basing on 0.4
  • Open an issue about sharness testing.
  • Open a feature issue about having multiple language implementations for curl requests
  • Hope Get sharness testing working
• Hope Research PATENTS.md strategies

[RichardLitt]

This Week

Summary: Not a very productive week for me this week, for a variety of reasons, mostly travel related and because it was a short week and I had a lot of admin stuff. I know what I'm doing, just running behind a bit.

• Sprint Management
• [~] Write the weekly roundup; launch it.
• IPFS API
  • Split into current functions master branch and expected spec branch.
    • Add a link to the api from the specs repo
  • Add curl commands to all method descriptions
  • Check all responses have maximal entries
    • Log any errors in go-ipfs
  • Standardize formatting for ipfs --help entries, basing on 0.4
  • Open an issue about sharness testing.
  • Open a feature issue about having multiple language implementations for curl requests
  • Hope Get sharness testing working
• Hope Research PATENTS.md strategies

Extra

• Built module to open ipfs/go-ipfs notifications from the CLI after the great "go-ipfs issue party". https://github.com/RichardLitt/open-github-notifications
• CR
  • fix(object) Ensure keys for all rendered array elements ipfs-webui#166
  • Version 0.1 of a tool to get a list of commit authors for the previous week newsletter#5
  • + M Add HasteIPFS awesome-ipfs#38
• Build GitHub Notification checker
• Overhaul "Modified Sprint and GitHub master roles" PR pm/pull/66
• Lots of go-ipfs issue review following the "great go-ipfs issue party"
• Met up with @jbenet in NY and merged some open PRs together
• Bought tickets to http://arcticjs.club; planned trip to Svalbard to meet @whyrusleeping and @diasdavid
• Closed js-guidelines Added js guidelines community#92

[dignifiedquire]

@dignifiedquire Sprint Update

Webui

• [~] More tests
• [~] CR contributions
• Initiate new distribution setup
• Work on the new design
•  Fix issues due to babel upgrade (ipfs/ipfs-webui@208e5d1)

Distributions

• Add build step for the new site
• Finish missing design implementations
• [~] Ship it, getting close: http://v04x.ipfs.io/ipfs/QmZyvWokPYGg6DrjE6o2V7qhThzZQZ8QCWqdd2U3S75HXC/index.html

Archives

• [~] Stackoverflow archive (Stackexchange Archives ipfs-inactive/archives#50)
• [~] Research into wikipedia dump mirrors (https://meta.wikimedia.org/wiki/Mirroring_Wikimedia_project_XML_dumps)

CR

•  Lots of PRs from @RichardLitt that I don't have the links to anymore

[ghost]

@lgierth sprint update

I've been away for a day visiting my grandma (she turned 80). The ipfs.io v03x/v04x thing is on its way, and I'm very happy to start getting rid of Ansible.

• 0.4.0
  • v04x.ipfs.io and v03x.ipfs.io
  • more v04x 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 faster)
    • dead-simple replacement for ansible (aka Provsn)
    • [~] deploy ipfs using provsn
• 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
• work through email backlog
• wishlist
  • set up buildbot worker for Tahoe-LAFS (didn't hear back)

[whyrusleeping]

• libp2p example for @diasdavid
• fix and test set/append data for ipfs object patch
• cleanup mfs code a bit, refactoring how it pins
• [~] ipfs files flush
• let @mafintosh convince me to go to svalbard for arcticphp
• paris?
• distibutions build script nearly done, just some small cleanup to do

[daviddias]

SPRINT CHECK IN

• js-ipfs
  • /bootstrap WIP - Bootstrap feature js-ipfs#45
    • cli
    • core
    • tests on all
  • /id ID impl + tests (core+api+cli) js-ipfs#44
    • cli
    • api
    • core
    • tests on all
  • /version version js-ipfs#43
    • cli
    • api
    • core
    • tests on all
  • 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
  • CR Improving test coverage multiformats/js-multistream-select#6
• Invest time on API documentation, organize things, CR PR's, issues and so on
• npm on ipfs
  • work and debug with @whyrusleeping files api (which affects npm on IPFS).
• 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 - It was great, more users of IPFS (and following close libp2p and js-ipfs) than I imagined

This week hasn't been super productive for me code wise, missing a flight, losing my bag, having to buy some cloths (not knowing when my bag was going to get back) and travelling to two countries in a sprint that was shortened by one day made me feel that I was leaking time everywhere.

One of the outcomes of all this travelling, that might me useful for others, is that we started a awesome list for hacking spots in cities (It has been really hard to get good internet or internet at all in Paris)

https://github.com/diasdavid/awesome-hacking-spots

[jbenet]

This week I've been working through my large holiday backlog, reconnecting with various people in the IPFS periphery, and handling many start of year organizational things. Lots of email. Haven't made it to github proper yet. Sorry-- if any PRs need my pressing comments, CR, please bring them up to me via IRC or https://github.com/jbenet/todo

• whittled backlog
• lots of IPFS related email
• worked on PRs with @RichardLitt, discussed various community things
• [~] IPLD spec work with @mildred -- i still need to do more here this.
  • finalize IPLD
• latest vs stable webui comments (@jbenet) in Discussion notes on WebUI release process from Dec 21 ipfs-webui#167 -- didnt get to this
• lots of protocol labs org things

[hackergrrl]

I've just been trying to ramp up on everything (reading lots of specs over the holidays!), and figure out what I'm going to be focusing my efforts on for Q1. I expect to be bugging you all a lot over the coming weeks!

[jbenet]

@noffle 👍 :)

[daviddias]

@RichardLitt getting back to you on the star:

🌟Now you can do npm i -g js-ipfs and use jsipfs bootstrap + id + version commands, fully compatible with go-ipfs repo

:)

[RichardLitt]

Thanks @diasdavid. @dignifiedquire @lgierth @whyrusleeping: what's yours?

[whyrusleeping]

no star, i don't do anything that interesting

[dignifiedquire]

⭐ distributions page

[hackergrrl]

@diasdavid that's awesome! Just tried it! +:100:

[ghost]

@lgierth what's yours?

added - the work-in-progress dev040 migration

[jbenet]

• ⭐ (specs) much debate in the IPLD spec about pathing notation.

[chriscool]

• ⭐ IPFS Docker image is now tested automatically on Travis, thanks to @ChristianKniep and @whyrusleeping, see PR Docker image volume fix and Sharness tests  kubo#2064 (Docker image volume fix and Sharness tests)