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

Sprint: February 16 (Tuesday) #91

Closed
RichardLitt opened this issue Feb 14, 2016 · 22 comments
Closed

Sprint: February 16 (Tuesday) #91

RichardLitt opened this issue Feb 14, 2016 · 22 comments

Comments

@RichardLitt
Copy link
Member

Sprint February 16

Note that this sprint has been moved from the normal Monday February 15th sprint.

The IPFS Weekly for this week is here. Please add anything cool which happens over the course of this week to it.

Sprint Goals

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
sync Rich Littauer 9:00pDT 17:00Z 18:00CET IRC: #ipfs on Freenode
apps on ipfs Friedel Ziegelmayer 10:30PDT 18:30Z 19:30CET https://public.etherpad-mozilla.org/p/ipfs-feb-16-apps-on-ipfs
infrastructure Lars Gierth 11:00PDT 19:00Z 20:00CET https://public.etherpad-mozilla.org/p/ipfs-feb-16-infrastructure
libp2p David Dias 11:30PDT 19:30Z 20:30CET https://public.etherpad-mozilla.org/p/ipfs-feb-16-libp2p
js-ipfs David Dias 12:00PDT 20:00Z 21:00CET https://public.etherpad-mozilla.org/p/ipfs-feb-16-js-ipfs

Wednesday

Endeavour Lead Time (PDT - UTC/Z - CET) Pad
go-ipfs Jeromy Johnson 10:30PDT 18:30Z 19:30CET https://public.etherpad-mozilla.org/p/ipfs-feb-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.
@RichardLitt RichardLitt changed the title Spring: February 16 Sprint: February 16 (Tuesday) Feb 14, 2016
This was referenced Feb 14, 2016
Closed
Closed
@RichardLitt
Copy link
Member Author

Added note about the Weekly for this week, which can be found here: ipfs/newsletter#21. Add stuff as it happens!

@ghost
Copy link

ghost commented Feb 16, 2016

Infrastructure

Lead: @lgierth

Participants

Agenda

  • 0.4.0
    • multireq and gateway issues
    • utp port 4001 vs 4002
  • metrics
    • no metrics for v03x yet
    • http response metrics are from go-ipfs's point of view, not nginx's
    • alerts

Notes

  • multireq/gateway issues should be resolved now, why says it looks better now
  • utp, let's pick the official-ish port 4737
  • let's also update the tcp port
    • come up with a list of stuff that needs to be updated, beforehand, so that we don't overlook anything important
    • what if more transports? 4737 is multistream in general, both tcp and udp
  • pinbot
  • metrics
    • nginx response status metrics
      • commercial module
      • parse logs?
    • adding metrics
      • add scraping target to prometheus.yml
      • experiment with queries at metrics.i.ipfs.io/prometheus
      • add to dashboard
  • alerts
    • gateway availability
    • swarm availability
    • sms alerts
    • no on-call schedules for the foreseeable future

@daviddias
Copy link
Member

Libp2p

Lead: David Dias

Agenda

  • webrtc-explorer
  • piri-piri & karma-peer

Notes

  • NEXT
  • finish webrtc-explorer reboot
  • impl js-ipfs swarm connect
  • karma-peer spawn browser on demand
  • karma-peer electron-spawn
  • go-libp2p connect request

@daviddias
Copy link
Member

js-ipfs

Lead: David Dias

Participants

Agenda

  • Update
  • UnixFS
    • should we have a thing to import directories?

Notes

NEXT

  • fix nested dir importing on data-importing
  • data-importing bufferImporter
  • data-importing streamImporter
  • data-importing export (for ipfs files cat)
  • bitswap
  • core-api specs

@dignifiedquire
Copy link
Member

Apps on IPFS

Lead: Friedel (@dignifiedquire)

Participants

Agenda

Notes

Webui

ipget

@dignifiedquire
Copy link
Member

@dignifiedquires TODOs

Content Work

Update install instructions on the website

  • Binary Installations: Link to dist.ipfs.io
  • Update the version in descriptions
  • No more go get

Check Needs Review

https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+org%3Aipfs+label%3A%22needs+review%22

Review Blog Posts

Post weekly details

  • Add IPFS Apps notes
  • Add weekly todos

Webui

Distributions

  • Code Signing [0/2]
    • Review PR comments
    • Investigate The Update Framework

IPFS GeoIP

  • Add all the data to the 0.3 and 0.4 network

@nginnever
Copy link
Member

@nginnever TODO

- js-ipfs - [x] PR ID command (keygen part of issue #42) - js-ipfs-data-importing (js-ipfs issue #41) - [x] bufferImorter - [ ] streamImporter - [ ] browser / mocha tests - js-peer-id - [x] create issue / document forge build - Webui - [ ] begin redux saga (issue #227) - [ ] research enzyme tests on components - [ ] document in contibuting.md

@daviddias
Copy link
Member

DAVID DIAS TODO

@RichardLitt
Copy link
Member Author

To Do

@Kubuxu
Copy link
Member

Kubuxu commented Feb 17, 2016

@Kubuxu TODO:

  • gx-lua in go or maybe once more in Lua
  • two stage caching for IPNS
  • [~] investigate CRDT over IPFS/IPLD
  • add cdnjs to my dedicated - available at fs:/ipns/cdnjs.ipfs.ovh/
  • host glowing-bear on IPFS (using cdnjs) and add fs:/ handler to it. - available at fs:/ipns/glowing-bear.ipfs.ovh/

@whyrusleeping
Copy link
Member

Go-IPFS

Lead: Jeromy

Participants

Agenda

  • 0.4.0 testing
    • large long running tests
  • get CI green
    • a few intermediate sharness failures
    • appveyor
  • issue template (yay new github features)

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

Actionables:
- fix gx installs on appveyor (looks like gopath issues?)
- fix sharness tests on appveyor (theres a lot here, every bit helps)
- write up an issue template
- modularize iptb code, for reuse in large testing environments
- ALL: try out a new ipfs command (look in ipfs commands)

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

@hackergrrl
Copy link
Contributor

noffle todo

@ghost
Copy link

ghost commented Feb 19, 2016

@lgierth todo

@dignifiedquire
Copy link
Member

@dignifiedquire SprintUpdate

Content Work

Webui

IPFS GeoIP

Station

dignified hacks

  • [-] Twitch
    • Sign up
    • Configure all the things
  • Find good screen recorder: OBS
  • Test out
  • Plan first episode

Misc

@Kubuxu
Copy link
Member

Kubuxu commented Feb 22, 2016

@Kubuxu sprint update:

  • gx-lua in go or maybe once more in Lua
  • two stage caching for IPNS
  • [~] investigate CRDT over IPFS/IPLD
    • - theory of operation based CRDTs in IPLD
    • - figured out that state based CRDT will be hard to optimally store in IPLD
  • add cdnjs to my dedicated - available at fs:/ipns/cdnjs.ipfs.ovh/
  • host glowing-bear on IPFS (using IPFS cdnjs) and add fs:/ handler to it. - available at fs:/ipns/glowing-bear.ipfs.ovh/

@RichardLitt
Copy link
Member Author

This Week

This week I focused on getting the API out of the door, although I also did a fair amount of other things. I updated a lot of the go-ipfs mans in the process of finishing up the API, but there is still a lot of work to do there, and the work is very difficult due to constant context switching. Hoping to keep banging away at this this week.

Radically transparent thought process ahead: My work suffered this week because I was straight out avoiding the weekly. I am not good at tackling it. Encouragement on the whole thing would be appreciated: right now I feel like it is something everyone needs, but no one wants to help make, and the need for it to be all-inclusive in content and high quality makes me want to do little doc PRs where I feel safe to keep me from engaging with the high mental cost of trying to sort out what is actually interesting for the IPFS project at a whole, something that I am still not sure about all of the time. I'm guessing the same is true for a lot of the other projects here - the cost for being a team comprised of masters is that we are all responsible for our domains: I'll try and encourage other people, too, and I'll struggle to be more responsible here. One thing I can do better is to always build it during the sync and not wait until after. That's what I'll try to do, today.

Extra

@whyrusleeping
Copy link
Member

  • fixed revert bug in fs-repo-migrations (Sprint Q #23)
  • fixed a panic in argument parsing in go-ipfs (#2354)
  • set up CI for go-libp2p (PROPOSAL: Move sprint planning to start at 17:15 UTC (mondays) #16)
  • add observed remote addr on handshake (README.md: Fix 'print' -> 'sprint' typo #15)
  • fix t0065 timing issue (#2346)
  • reduce memory usage of request log (#2344)
  • merged lars changes into multireq
  • fix filepath checking for gx on windows
  • [~] start refactoring iptb into a usable library+cli
  • started PR for changing default ports
  • CR/Merge #2333 #2377 #2372 #2373 #2374 #2366 #2362 #2363 #2364 #2367 #2365 #2369 #2353 #2352 #2351 #2342 #2298 #2299 #2321 #2337
  • file bugs for every CI failure ⭐

@ghost
Copy link

ghost commented Feb 22, 2016

@lgierth update

This week didn't quite go as planned either. Looked after stability problems with docker and the go-ipfs containers which made me decide to switch to runc+runit as a runtime, which is work-in-progress. Also threw a bit of hardware at the problem (resized our vhosts).

@nginnever
Copy link
Member

Update

- js-ipfs - [x] PR ID command (keygen part of issue #42) - js-ipfs-data-importing (js-ipfs issue #41) - [~] bufferImorter - [~] streamImporter (more questions) - js-peer-id - [x] create issue / document forge build - Webui - [x] begin redux saga (issue #227) - [x] research enzyme tests on components

@hackergrrl
Copy link
Contributor

noffle end-of-week

Fixed several go-ipfs test failures, and revisions on other outstanding PRs. I can now manually set up a Go package for ipfs.io retrieval via 'go get' -- now we just need to make the changes to gx-go to do it for us and rewrite urls to use ipfs.io. Some clean-up on ipfs-hyperlog to integrate my work back into the parent hyperlog project rather than being a crude fork.

@daviddias
Copy link
Member

David Dias Check in

js-ipfs

js-ipfs-api

ipfs-geoip

libp2p

npm on ipfs

  • [~] [777509/785588] super close to have the complete clone (overcome the IPFS memory leaks by just monitoring the process and restarting after it gets too 'hot') scratch that, just found out that something weird has happened, investigating.

station

ipscend

js-ipfsd-ctl - Features that I needed for ipscend

specs

@RichardLitt
Copy link
Member Author

Thanks, all. Please add your starred updates to the weekly: ipfs/newsletter#21.

The next sprint is: #93.

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
7 participants
@hackergrrl @dignifiedquire @RichardLitt @daviddias @whyrusleeping @Kubuxu @nginnever