Sprint: Aug 1 → Aug 8

[RichardLitt]

Sprint August 1st

Sprint Goals

This sprint, we are going to be solidifying our roadmap for the months ahead, and also catching up on some backlog after the event last week. During the sync today, we will go over the Q3 goals listed as new issues in this repo: namely, go-ipfs in #127, js-ipfs in #128, and IPLD in #129. This will lead to having the main project owners having their todos clarified for the coming week; put those below as soon as possible. For other people (including community members!), please put whatever you're working on below.

Sprint Discussions

Calendar

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

Endeavour	Lead	Time (PDT - UTC/Z - CET)	Pad
js-ipfs	@diasdavid	11:30PDT 18:30Z 19:30CET	Etherpad, issue #128
go-ipfs	@whyrusleeping	12:00PDT 19:00Z 20:00CET	Etherpad, issue #127
IPLD	@jbenet	12:30PDT 19:30Z 20:30CET	Etherpad, issue #129

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.

[daviddias]

js-ipfs

Lead: @diasdavid

Participants

@diasdavid
@dignifiedquire
@Voxelot
@RichardLitt
@em-ly

Agenda

• roadmap update
  • waffle board
• priorities and where we need help
• the eternal streams discussion
• changelog
• other things?

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

• roadmap https://github.com/ipfs/js-ipfs/blob/a8c5db3152f8131f22573fe204a70411bc5ac4f2/ROADMAP.md
• streams Node.js Streams vs pull-streams vs ReactiveJS js-ipfs#362
• changelog Improve commit messages for better project tracking and changelogs community#145
• waffle https://waffle.io/ipfs/js-ipfs
• IPLD transition Experimental Proposal: CIDv1 -- IPLD, Multicodec-packed, and more specs#130

[RichardLitt]

go-ipfs

Lead: @whyrusleeping

Participants

@whyrusleeping
@Kubuxu
@em-ly
@jbenet
@RichardLitt

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

See #127. They have been edited into the main issue, as the call consisted of filling this out.

[RichardLitt]

IPLD

Lead: @jbenet

Participants

@diasdavid
@whyrusleeping
@Kubuxu
@em-ly
@dignifiedquire
@jbenet
@RichardLitt

Agenda

• Go through the IPFS issue Q3 Roadmap: IPLD #129

Notes

See #129. They have been edited into the main issue, as the call consisted of filling this out.

[haadcode]

@haadcode's sprint goals - Sprint August 1st

• "Fix Orbit" milestone goals, https://github.com/haadcode/orbit/milestone/2
• Help to define and implement a project management process

[daviddias]

David Dias TODO

• Conquer my backlog
• Follow up on the discussion about Control Flow in js libs Node.js Streams vs pull-streams vs ReactiveJS js-ipfs#362
• Make the case for 'optimised' js-ipfs
• Streams
• Make the case for Ion vs Cbor
• Reduce js-ipfs-api complexity Reduce de complexity of the js-ipfs-api module ipfs-inactive/js-ipfs-http-client#313
• get as much done as possible on the js-ipfs-api next generation endeavour next generation ipfs-inactive/js-ipfs-http-client#305
• Write the PubSub system (Self Certified Streams) notes from all the discussions (PubSub notes from the IPFS Workshop - recursion and corecursion, PubSub API and Self Certified Streams notes#154)
• Fix duplexify thing to make it work again in Node 6 Fix for Node.js 6.3.3 js-ipfs#373

[daviddias]

It would be great to have a pubsub dedicated discussion for next week hangout. @em-ly @RichardLitt could you make sure that it is included on the schedule? Thank you.

[RichardLitt]

Also add an IPLD session. See #124

[daviddias]

David Dias Sprint Check In

Getting back to my schedule, this was week was good but still packed with a lot of non planned work (discussions, logistics and others). Excited to get back on track

Done

• Conquer my long email backlog 🏅
• Get back to all the issues I was notified
• CR what was there for CR in JS land
• js-ipfs
  • Investigate, discuss and move on with the Control Flow issue (Streams) on js-ipfs Node.js Streams vs pull-streams vs ReactiveJS js-ipfs#362
  • Make the case for 'optimised' js-ipfs [technical exploration] js-ipfs bundle optimized js-ipfs#398
  • Fix duplexify thing to make it work again in Node 6 Fix for Node.js 6.3.3 js-ipfs#373
  • 2xCR+T Adds API for ipfs.files.get. ipfs-inactive/interface-js-ipfs-core#28 and related PRs (ipfs.files.get)
  • CR block API spec ipfs-inactive/interface-js-ipfs-core#32
• pubsub
  • Revisit pubsub with @jbenet and @whyrusleeping, post IPFS workshop
  • Write the PubSub system (Self Certified Streams) notes from all the discussions (PubSub notes from the IPFS Workshop - recursion and corecursion, PubSub API and Self Certified Streams notes#154)

Didn't manage to complete

• [~] Remaining interface-ipfs-core spec definitions (DHT, mfs, swarm, name and pinning)
• Make the case for Ion vs Cbor
• [~] Reduce js-ipfs-api complexity Reduce de complexity of the js-ipfs-api module ipfs-inactive/js-ipfs-http-client#313
• Get as much done as possible on the js-ipfs-api next generation endeavour next generation ipfs-inactive/js-ipfs-http-client#305

[dignifiedquire]

Dignifiedquire Sprint Check In

Getting ready to improve js-ipfs in all ways possible

js-ipfs

• Discuss and decide on an action plan for the control flow issues in js-ipfs (Node.js Streams vs pull-streams vs ReactiveJS js-ipfs#362)
• Implement pull-based prototypes for
  • js-libp2p-secio ([WIP] Refactor to use pull streams libp2p/js-libp2p-secio#8)
  • js-libp2p-identify ([WIP] move to pull-streams libp2p/js-libp2p-identify#2)
  • js-libp2p-tcp (Migrate to pull-streams libp2p/js-libp2p-tcp#20)
  • js-libp2p-multistream ([WIP] pull-streams multiformats/js-multistream-select#19)
• Introduce commit convention for js based projects (Draft of js git commit convention community#148)
• Implement changelog generation in aegir for new commit convention (Changelog generation aegir#41)
• Reduce the bundle size of js-ipfs by roughly 50% through fixing build issues in aegir (feat(webpack): enable dedupe plugin aegir#42)
• Enforce reduced code complexity through limiting the amount of nesting allowed (feat(lint): restrict nesting to avoid callback hell aegir#44)
• Refactor js-ipfs cli to fix help issues and improve the user experience (Refactor cli to use yargs js-ipfs#390)
• document the used modules in the readme of js-ipfs (Module list js-ipfs#385)

IPLD

• Discussions about the current issues needed for getting the spec ready.

[haadcode]

haadcode's sprint check in - Sprint August 1st

Spent the last week mainly on defining a project management process for IPFS, great discussion and progress in this thread #125 and as a result, working on this document #131.

Didn't get to spent much quality time with code, but some progress was made on "Fix Orbit" milestone.

Last week's goals:

• "Fix Orbit" milestone goals, https://github.com/haadcode/orbit/milestone/2
• Help to define and implement a project management process

[Kubuxu]

Kubuxu sprint check in - Sprint August 1st - 8th

That week I've travelled back to Poland and was getting set up here.
Before that I've worked on c-multihash, the decoding part is done, although it needs more tests. Next week I will work on encoding in c-multihash and more tests. The plan also includes fuzzy tests of c-multihash.

• - c-multihash
  • - build system
  • - minimal test framework
  • - fuzzy test framework
  • - decoding
    • - decoding tests
    • - decoding fuzzy tests
  • - encoding
    • - encoding tests
    • - encoding fuzzy tests
• - review few go-ipfs PRs