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

Sprint Dec 14 #74

Closed
RichardLitt opened this issue Dec 14, 2015 · 20 comments
Closed

Sprint Dec 14 #74

RichardLitt opened this issue Dec 14, 2015 · 20 comments

Comments

@RichardLitt
Copy link
Member

Sprint Dec 14

  • Completed IPFS API Spec (core + transports) by Jan 1

Sprint Goals

Sprint Discussions

Schedule

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

Endeavor 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-dec-14-apps-on-ipfs
infrastructure Lars Gierth 11:00PDT 19:00Z 20:00CET https://public.etherpad-mozilla.org/p/ipfs-dec-14-infrastructure
libp2p David Dias 11:30PDT 19:30Z 20:30CET https://public.etherpad-mozilla.org/p/ipfs-dec-14-libp2p
js-ipfs David Dias 12:00PDT 20:00Z 21:00CET https://public.etherpad-mozilla.org/p/ipfs-dec-14-js-ipfs
go-ipfs Jeromy Johnson 12:30PDT 20:30Z 21:30CET https://public.etherpad-mozilla.org/p/ipfs-dec-14-go-ipfs

Please add the Agenda to the Pad before the endeavor 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.
@ghost
Copy link

ghost commented Dec 14, 2015

infrastructure

Lead: @lgierth

Agenda

  • dev040 deployment
    • update strategy, also for the future
    • v04x.ipfs.io / v03x.ipfs.io
  • storage
    • biham and nihal
    • castor and sirius
  • deploying site updates automatically in a consistent way via IPFS or IPNS (project repos, website, maybe blog?)

Participants

Notes

  • dev040
    • open issue to come up with upgrade plan
    • include certain ipfs users who are embedding ipfs in their software and might have trouble updating
    • one option: have the multistream handshake be backwards-compatible
    • another option: break compat, but do so with a plan of how to do it better on both our end and their end
  • storage
    • nihal for internal use
    • biham "free for all"
    • copying castor's and sirius' data to biham, then shutting them down
    • daviddias can resume NPM on biham once the copying is finished
  • storage at jbenet's place
    • the host formerly known as earth will be resurrected in the coming days
    • will serve as OSX build machine
    • hands-on storage
  • deploying site updates automatically
    • spin up server which receives github hooks, builds sites, publishes to IPNS
    • start with project-repos (aka ci-status)

@daviddias
Copy link
Member

Apps on IPFS

Lead: @dignifiedquire + @jbenet

Agenda

  • registry-mirror
  • have a node with full npm
  • make experience of getting it ready really nice
  • release 0.4.0 on go builder with latest bell and whistles
  • migration Deprecating sirius and castor hosts infra#134
  • ipfs/distributions
  • IPNS + CoreNetwork

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

registry-mirror

  • try the new 0.4.0 with Rabin again in Jeromy Machine (check with Jeromy)
  • use one of the 17TB nodes to be the main one for npm on IPFS
  • try with tar importer
  • improve installation process of 0.4.0 (check with Jeromy)

ipfs/distributions Update

  • design draft approved last week
  • in the middle of implmentation
  • Goal: Get it ready before 0.4.0

IPNS + Core Network

  • Core Network is using IPNS to publish/consume social network style streams
  • IPNS speed concerns
  • PubSub may fix this, either by sending updates directly, or pushing IPNS updates over PubSub

@daviddias
Copy link
Member

libp2p

Lead: @diasdavid

Agenda

  • factoring go-libp2p
  • swarm Interop
    • secio in JavaScript
  • Are we going TLS?
  • python libp2p
  • rust libp2p
  • update roadmap if needed Roadmap for libp2p #72

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

  • crypto channels
    • multistream enables us to have several protocols already
    • implement TLS 1.3 (check if there are implementations that work in JS) as a upgrade transport
    • look into curveCP
    • skip secio in JS land for now
    • list all of the interfaces in libp2p for Juan to bikeshedding

@daviddias
Copy link
Member

js-ipfs

Lead: @diasdavid

Agenda

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

  • js-ipfs-repo
    • datastore
    • dir
      • levelDB -> /datastore
      • flatfs -> /blocks
      • might move to arenaStore in the long term
    • itemzise what is on leveldb-datastore (@jbenet)
      • DHT (provider records)
  • jsipfs
  • IPLD Data Importing
  • Bitswap
    • dag path notation - IPLD Selector notes#12
    • spec interface (upgrade with dag path notation) (ion is working this)
    • right now JS implementation can use the same 'dumb' approach

@jbenet
Copy link
Member

jbenet commented Dec 14, 2015

go-ipfs

Lead: @whyrusleeping (@jbenet subbing)

Agenda

  • ship distributions
  • ipfs-update testing
  • fs-repo-migration testing
  • 0.4.0 things
  • upgrade path and compatibility

Participants

Notes

Questions:

  • what's the 0.4.0 upgrade path? we'll ask users who care.
  • what's in leveldb? DHT Records mostly.
  • we could implement a kv-store (like pin set) on top of ipfs objects
    (basically ipfs-blob-store) and transition everything in one go.
  • DHT Records will be ipfs objects eventually anyway, under iprs.

TODOS:

@harlantwood
Copy link
Contributor

@harlantwood hopes to:

@daviddias
Copy link
Member

David Dias TODO

@jbenet there are some things you can do that will help me a ton if you manage to go through them quickly, these are:

@eminence eminence mentioned this issue Dec 15, 2015
Closed
@RichardLitt
Copy link
Member Author

This Week

  • Sprint Management
  • API
    • Stub out the entire IPFS api at ipfs/api. PR api/pull/13
    • Clean up and get the API working on Apiary.

@dignifiedquire
Copy link
Member

Todo

  • getting IPFS distributions ready for shipping
  • Work on rust-multiaddr
  • CR api doc PR from @RichardLitt
  • Move apiary source to ipfs/api

@whyrusleeping
Copy link
Member

TODO

  • fs-repo-migration shipped
  • dist.ipfs.io 'build things ourselves' shipped
  • new ipfs add make fewer objects
  • discuss directory sharding
  • look at modtimes in mfs

@ghost
Copy link

ghost commented Dec 15, 2015

@lgierth TODO

@chriscool
Copy link
Contributor

@chriscool TODO

@jbenet
Copy link
Member

jbenet commented Dec 16, 2015

@jbenet TODO

if i told anyone i'd do something and it's not here, please let me know.

@daviddias
Copy link
Member

@jbenet what I had for you was:

@rht
Copy link

rht commented Dec 16, 2015

what's the 0.4.0 upgrade path? we'll ask users who care.

  • Is there a way to sample/snapshot the distribution of the versions the nodes are running?
  • What measure should be used for the network consensus? e.g. 1. the node itself, so that if 51% uses 0.3.8 then that's considered the 'majority', everything else are 'forks', 2. the number/size of hashes of each nodes
  • How are hotfixes broadcasted? Perhaps a semver header check + 101 status response can be used here. If a 0.4.0 node talks to a 0.3.5 node it could notify the latter to upgrade due to such and such list of vulnerabilities.

@RichardLitt
Copy link
Member Author

This Week

  • Sprint Management
  • API
    • ⭐ Stub out the entire IPFS api at ipfs/api. PR api/pull/13
    • Clean up and get the API working on Apiary.

Done

  • Helped plan IPFS Weekly. Comment pm/issues/73
  • Added shields to ipfs-specs. PR specs/pull/52
  • Updated project-dir with new data for project-repos. PR /New templates for weekly call agendas/notes #137, PR Improved Check Ins #138
  • Wrote a doc on how to manually downgrade. PR fs-repo-migrations/pull/10
  • Created and filled out ipfs/roundups
  • CR + M awesome-ipfs/pull/20
  • Work on awesome-ipfs. Closed issues, opened PR awesome-ipfs/pull/29, awesome-ipfs/pull/30, awesome-ipfs/pull/31
  • Added Travis to awesome-ipfs. awesome-ipfs/issues/27

@whyrusleeping
Copy link
Member

TODO

  • fs-repo-migration shipped ⭐
  • dist.ipfs.io 'build things ourselves' shipped
    • closer now, builds dist.json file
  • new ipfs add make fewer objects
  • discuss directory sharding
  • look at modtimes in mfs
  • work on mfs locking issues and performance

@dignifiedquire
Copy link
Member

@dignifiedquire sync update

Planned

  • [~] getting IPFS distributions ready for shipping
  • ⭐️ Work on rust-multiaddr
    • enque/dequeue
    • auto generated, published docs to github pages
    • support for IPFS and onion addresses
  • CR api doc PR from @RichardLitt
  • Move apiary source to ipfs/api

Extra

Special

  • Start benchmarking different request modules in node dignifiedquire/request-bench this is part of a more major undertaking that I might talk about if someone is interested as it is only partialy related to IPFS

@daviddias
Copy link
Member

SPRINT CHECKIN

@ghost
Copy link

ghost commented Dec 21, 2015

@lgierth sprint update

This sprint I managed to lose all of Castor's storage -- yay! :S And sorry again @davidar.

Apart from that dev040 is on the plate. We haven't gotten to discuss the migration strategy with users, I'll get to it right away.

Not really any * from me this week :)

@daviddias daviddias mentioned this issue Dec 23, 2015
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@harlantwood @jbenet @chriscool @rht @dignifiedquire @RichardLitt @daviddias @whyrusleeping