Sprint O

[jbenet]

Sprint Goals

Sprint Discussions

See https://github.com/ipfs/pm#sprint-discussion-schedule

Sprint Deliverables

• Add yourself below, 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.

@jbenet

• iprs, records, record chain
• signed records
• record tests
• merge GC, batching (datastore), batching (go-ipfs)
• https://github.com/jbenet/node-bsdash

@whyrusleeping

• extra logs for bitswap dashboard
• implement basic bitswap dashboard
• land GC
• land batching (go-datastore)
• land batching (go-ipfs)
• field test dev0.4.0
• fix too many open files issue with bitswap/flatfs respect open fd limit kubo#1456
• add lazy negotiation to go-multistream

@lgierth

• cjdns-based auth for prometheus Make use of cjdns for Prometheus/API/Gateway authentication infra#40
• prometheus dashboard Dashboard frontend for Prometheus infra#35
• discover peers from cjdns WIP: discover peers from cjdns kubo#1316
• spec out relevant cjdns internals Integration with cjdns notes#14
• migrate IRC bots to solarnet Migrate IRC bots to solarnet infra#33
• make IPFS config an Ansible step Make IPFS config an Ansible step infra#39
• h.gateway.ipfs.io h.gateway.ipfs.io infra#30

@krl

• ipfs-app-tool
  that can add unixfs directories
• ipfs-app
• webui -> ipfs-app(s):

@diasdavid

• Get node-swarm working
  • Opening sockets between peer
  • Negotiate a spdy-transport session (Connection) through multistream-select
  • Open streams on top of spdy
  • Switch to Protobufs
• Have node-identify working
• Write a good amount of tests for all of the above
  • random-bytes-stream https://github.com/diasdavid/random-bytes-stream
  • abstract stream muxer https://github.com/diasdavid/abstract-stream-muxer
  • node abstract stream muxer compliant spdy implemenetation https://github.com/diasdavid/node-spdy-stream-muxer
  • write remaining tests for abstract-stream-muxer https://github.com/diasdavid/abstract-stream-muxer/tree/master/tests
• Integrate swarm with the routing layer (to make the DHT interesting)
• Other
  • Make the API for abstract-stream-muxer more flexible - Make the API flexible to conform both with Accept interface (like net.connect pattern) and HandlerFunc (like http pattern) libp2p/interface-stream-muxer#1

[jbenet]

@whyrusleeping @Heems @rht @wking @cryptix @chriscool and anyone else, post stuff below and i'll add it to the top.

[rht]

• Fix processLink leak leak jbenet/goprocess#5

Also I have had the confusion of the man-hour/week/month tracker that there is no 1-to-1 mapping between:

1. waffle.io board (planning, in progress, done) labels
2. this pm weekly issue (planning and done) + daily sprint sync (in progress). This is supposedly a strict subset of 1, but not many items are stated in an issue explicitly (although they will eventually turned into PR's). Just wondering if things need to be more semantic.
3. github per-repo milestone (opposite of icebox, or monthly-scale backlog). https://github.com/ipfs/pm/milestones

[chriscool]

Improve ipfs-paste: jbenet/ipfs-paste#2

[whyrusleeping]

next sprint etherpad: https://etherpad.mozilla.org/biFo0CDpCp

[jbenet]

Also I have had the confusion of the man-hour/week/month tracker that there is no 1-to-1 mapping between:

1. waffle.io board (planning, in progress, done) labels
2. this pm weekly issue (planning and done) + daily sprint sync (in progress). This is supposedly a strict subset of 1, but not many items are stated in an issue explicitly (although they will eventually turned into PR's). Just wondering if things need to be more semantic.

yeah, unfortunately we aren't using waffle as much. do we want to really commit to it? (i find it a bit tedious to organize, but if someone helps me with that, i'm down to commit to labeling all the things well). the labels will certainly help people asynchronously know what's going on. i'm no expert in agile/kanban, so if someone with better PM experience wants to take this on, lmk! whatever makes us more effective = really useful.

i still want the etherpad / sprint issue to be the canonical repr of what someone's definitely taking care of that week.

1. github per-repo milestone (opposite of icebox, or monthly-scale backlog). https://github.com/ipfs/pm/milestones

per-repo milestones are usually just groupings of related issues. @whyrusleeping and i hoped to move the milestones to be releases (like 0.4.0 for go-ipfs).

[rht]

This should have been sprint O.

[rht]

I am in for an AI/bot pm overlord.

[rht]

per-repo milestones are usually just groupings of related issues. @whyrusleeping and i hoped to move the milestones to be releases (like 0.4.0 for go-ipfs).

Where labels should have been used for groupings instead.

Yet the waffle labels for issues are clearly still in the use.

If manual checkmarks can be removed https://github.com/blog/1506-closing-issues-via-pull-requests

[whyrusleeping]

@rht the waffle stuff is kinda done automatically. we have wanted to use it, but its a little difficult to get it integrated into (at least my) workflow. Unless you really like it, i wouldnt worry about it