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

Sprint: May 16 → May 30th #109

Closed
RichardLitt opened this issue May 16, 2016 · 21 comments
Closed

Sprint: May 16 → May 30th #109

RichardLitt opened this issue May 16, 2016 · 21 comments

Comments

@RichardLitt
Copy link
Member

RichardLitt commented May 16, 2016

Sprint Discussions

Schedule

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

Endeavour Lead Time (PDT - UTC/Z - CEST) Pad
sync @RichardLitt 9:00PDT 16:00Z 18:00CEST IRC: #ipfs on Freenode
apps on ipfs @dignifiedquire 10:30PDT 17:30Z 19:30CEST https://public.etherpad-mozilla.org/p/ipfs-may-16-apps-on-ipfs
infrastructure @lgierth 11:00PDT 18:00Z 20:00CEST https://public.etherpad-mozilla.org/p/ipfs-may-16-infrastructure
js-ipfs task force mega sprint @diasdavid 11:30PDT 18:30Z 20:30CEST https://public.etherpad-mozilla.org/p/ipfs-may-16-js-ipfs-task-force
go-ipfs @whyrusleeping 12:30PDT 19:30Z 21:30CEST https://public.etherpad-mozilla.org/p/ipfs-may-16-go-ipfs

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.
@ghost
Copy link

ghost commented May 16, 2016

Timezones are off, fixed in #110

@RichardLitt
Copy link
Member Author

Thank you.

@dignifiedquire
Copy link
Member

dignifiedquire commented May 16, 2016

Apps on IPFS

Lead: @dignifiedquire

Participants

Notes

Orbit Update

  • write improvements (100 ops/sec)
  • Akasha wants to use orbit-db
  • Added user auto complete
  • Emoji auto complete + preview coming soon
  • Next Level: orbit-db in the browser, orbit in the browser, everything in the browser :)

https://ipfs.io/ipns/bin.ipfs.ovh

  • Kubuxu if the work on orbit-db would help adding write access to his pastebin style project
  • Answer, mostly no but js-ipfs will help by having your own node in the browser connecting to other (potentially browser) nodes and
    sharing the content

ipfs-twitter-resolver

  • Storing "ipns records" in a tweet

Demo of gx from whyrusleeping

  • deps tree
  • pinning site for gx packages

@ghost
Copy link

ghost commented May 16, 2016

Infrastructure

Lead: @lgierth

Participants

Agenda

  • SSL
    • HSTS preloading
    • http=>https redirect
  • metrics stability
    • mtail bug
    • flakey cjdns routing
  • pages deploys
    • it's in progress, but not yet working :)

Notes

  • /version commit needs to be fixed
  • whyrusleeping wants to be able to use provsn
    • provsn needs secrets handling
    • provsn needs host grouping
    • provsn needs parallelism (it's sooooo sloooow)
  • lgierth badly wants to not be a bottleneck for others (pages && provsn)

@ghost
Copy link

ghost commented May 16, 2016

@lgierth todo

@dignifiedquire
Copy link
Member

dignifiedquire commented May 16, 2016

@dignifiedquire Todo

@daviddias
Copy link
Member

daviddias commented May 16, 2016

JS IPFS TASK FORCE MEGA SPRINT

This is a joint hangout to sync in the latest details to get js-ipfs out the door and some really cool examples working on it.

Lead: @diasdavid (David Dias)

Participants

  • David
  • Richard
  • Friedel
  • Kuba
  • Samuli
  • Nathan

Agenda

  • Status Update
  • What is left
  • Assign Tasks and try to come up with ETA
  • Make sure we are not missing anything

Notes

last mile

@Kubuxu
Copy link
Member

Kubuxu commented May 17, 2016

@Kubuxu todo:

go-ipfs:

general:

@RichardLitt
Copy link
Member Author

RichardLitt commented May 17, 2016

go-ipfs

Lead: @whyrusleeping

Participants

  • whyrusleeping
  • kubuxu
  • jbenet
  • RichardLitt
  • daviddias
  • dignifiedquire
  • noffle

Agenda

what we need for the demos

tag these with "dev", "solarnet", and/or "release" based on what we NEED and WANT by May 29

(ordered by priority)

  • yamux bug fixed (NEED: dev + solarnet, WANT: release)
  • websockets in go-ipfs (NEED: dev solarnet, WANT: release)
  • multstream name fixes (NEED: dev + solarnet, WANT: release)
  • relay in go-ipfs (NEED: dev + solarnet, WANT: release)
  • metrics change to monitor peers per transport (NEED: solarnet)
  • CORS issue api

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.

Notes

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

@dignifiedquire
Copy link
Member

dignifiedquire commented May 23, 2016

Mid Sprint hangout will be happening now, at 12:10noon EDT, 9:10am PDT, 6:10pm CEST, 4:10pm UTC.

@Kubuxu
Copy link
Member

Kubuxu commented May 29, 2016

@Kubuxu sprint summary

During this week I worked on resolving some issues, and introducing few QoL changes. I also kept the go-ipfs issues and PRs up to date as @whyrusleeping was on a trip. Most notably the offline mode of go-ipfs (no p2p connections, still provides local content and API) works but might still require few changes. I also moved some go-ipfs dependencies from Godeps to gx, it seems simple at first but is quite a bit of work. I am also thinking about new design of API and API transport that would be focused on low lever applications and high performance.

go-ipfs

General

@dignifiedquire
Copy link
Member

dignifiedquire commented May 30, 2016

@dignifiedquire sprint summary

The past two weeks were fast paced but exciting. I prepared and gave my first talk on IPFS at my local meetup. In addition to that I nearly finished my implementation of secio in JavaScript. There is just one racing condition fix and some integration work to be done there. And all the rest of my time was spent helping @diasdavid and @haadcode to get js-ipfs in the best shape possible, including an important fix to js-bitswap to ensure blocks are actually distributed to everyone.


@daviddias
Copy link
Member

daviddias commented May 30, 2016

David Dias Check In

Summary: This last sprint (2 weeks) has been super intense, having a clear, common goal (shipping orbit on js-ipfs) + getting js-ipfs milestone one ready, has given the team an immense focus on a set of things that were crucial to achieve those goals, making everyone working very closely together and that feeling has been amazing :).


Here is a gist of some of the things I've been doing:

  • Debug and fix things for go & js IPFS interop with @whyrusleeping. There are still some missing parts, but we know what to do (mostly, move js-ipfs Identify to use length-prefixed-messages as well)
  • Made libp2p-webrtc-star, a WebRTC Transport for libp2p, enables Orbit peers to use IPFS just from a browser tab
  • Lot's of fixes on spdy, tcp, websockets, identify, duplex streams that were not being wrapped properly, fix identify that was not working on the browser (cause of the missing keys).
  • libp2p-ipfs got a face wash and now it is less fragmented between the internals of js-ipfs and libp2p itself
  • Lot's of more test coverage
  • Havoc tests (blow up processes so that the others stay intact)
  • Worked with @ngginever and @noffle on interface-ipfs-core
  • Community
    • IPFS talk at require('lx')
    • Prepare talk for WebRebels

@haadcode
Copy link
Member

haadcode commented May 30, 2016

@haadcode sprint end report - 16 May - 29 May

Summary

I've worked on getting Orbit to run in the browser with js-ipfs (https://github.com/haadcode/orbit/tree/js-ipfs). We've been making very good progress and as of couple of days ago, we got it all (Orbit) working fully, with IPFS, in the browser! \o/ It's still brittle so the next steps are to make it more stable and performant. Nevertheless, a huge kudos to the JS team, you've made awesome work so far! Also helped the Akasha project to integrate orbit-db and they wrote a really nice blog post describing what they achieved with it (http://blog.akasha.world/2016/05/26/update-highlights-and-interesting-developments/).

@hackergrrl
Copy link
Contributor

hackergrrl commented May 30, 2016

noffle check in

I've had my nose down to the grindstone last week, focusing all my efforts on driving the JS IPFS Core API interface effort (interface-ipfs-core), with @nginnever and @diasdavid. No blockers other than merging the rest of my PRs. I'm just about done with 'add', which had a lot of edge cases to get unified across js-ipfs-api and js-ipfs. Richard and I got cracking on the remaining work for releasing standard-readme. Lots of hard work ahead to get everything finished for next sprint!

@RichardLitt
Copy link
Member Author

This week, I've been less productive than I hoped, because I have been travelling intensively. Mainly, I worked on some Standard-Readme stuff, PRs to http-api-spec, and making sure that awesome_bot works well with our newsletters. Today, I've merged some things to the website and to the blog. I also worked on presenting my endangered-languages repo to professional linguists at a conference; I'm hoping to turn it into an IPFS use-case for archiving academic code.

@nginnever
Copy link
Member

nginnever commented May 30, 2016

voxelot

The past week i started off with more interface-core, js-ipfs-api, and js-ipfs work. There are some open PRs that will be revisited over the week, just little improvements / more features to js-ipfs cat, and add. Also vacationing in Seattle at the moment enjoying the lovely green things and water!

@ghost
Copy link

ghost commented May 30, 2016

@lgierth sprint update

Good sprint -- while team JS has been crunching away,
I took care of a couple of smaller things and fixes,
and prepared the infrastructure side of js-ipfs and Orbit.
It's not running yet, but all the steps are layed out.

Also made a bit of progress on the fc00 CryptoAuth and Switch specs.

I didn't finish my personal quest of stopping being a bottleneck to others, yet :)

@whyrusleeping
Copy link
Member

whyrusleeping commented May 30, 2016

@whyrusleeping's checkin

The first week of sprint I spent a lot of time working with @diasdavid on go and js interop, I think we figured out all of the current issues preventing us from talking across implementations, but before i was certain of that i flew to mexico and had no internet for a week. On the plane ride back I gave iptb the ability to use docker to spin up ipfs nodes, opening up the possiblity of setting artificial bandwidth and latency between nodes for tests. Back in the secret laboratory, i've been tinkering with bitswap. Early tests are showing a 20% throughput increase and a 50% reduction in duplicate block sends.

@jbenet
Copy link
Member

jbenet commented May 30, 2016

@jbenet udpate

This last sprint I've been focused mostly on IPFS and Protocol Labs organizational things. Some highlights:

  • Working with a company who is revamping our ipfs.io website. It looks very exciting. Stay tuned!
  • Collab/org discussions with:
    • Akasha http://akasha.world/
    • Stellar
    • BigchainDB
    • Estonian E ID group
    • Mediachain
    • Internet Archive
    • ConsenSys / uPort
    • Blockstack
    • W3C members
  • Participated in http://weboftrust.info last weekend, which is an identity workshop/conf for emerging tech to be used in Identity. Participated there with many of our friends, including @nicolagreco. Spoke with many people about standards relevant, including IPLD, Keychain, multikey, and more.
  • Some small code review here and there.
  • Planning + prep for the Decentralized and Encrypted conference - I'm in Berlin this week for it!
  • Planning + prep for the Decentralized Web Summit - i'm in SF next week for it!

@nicola
Copy link
Member

nicola commented May 30, 2016

@nicola update

Done with the academic year - had a break plus travelling which meant -> reading time and meeting friends (decentralized and not). I had a great sync with @jbenet about summer plans.

  • met with juan, kyle, manu
  • converted to the church of log-based-everything-and-stream-why-not-(replicate-for-free) (thank you @noffle for the initial initiation)
  • participated at http://weboftrust.info with @jbenet @manusporny & friends.
    Got up to speed with what is happening with Decentralized IDentifiers (DIDs), since then I have been constantly thinking on how to move things across chains
  • read interesting papers on verifiable computations (computations on authenticated logs), causal chains (have chains that diverge, but are still mergeable, so one can do faster progress on a chain different than the main one), BFTs (and clever tricks for DHTs), distributed pubsub (mainly reading Cyclon, Vicinity, Sub2Sub) and the different proposal to scale bitcoin (bitcoin-ng, blockDAG, GHOST)
  • worked on js-gossip-cyclon new api
  • preparing for the decentralized web summit (sf next week)
  • dream aims for next week (1) a reading group (2) plan papers to finalize with you all! (3) get cyclon/vicinity/sub2sub implemented (4) playing with js-libp2p webrtc

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants