Sprint: Aug 29 → Sept 4

[RichardLitt]

Sprint August 29th

For information about these calls and how they work, read the ipfs/pm README.

Calendar

Endeavour	Lead	Time (PDT - UTC/Z - CEST)	Pad
All Hands Call	@flyingzumwalt	9:00PDT 16:00Z 18:00CEST	all-hands notes
orbit	@haadcode	9:30PDT 16:30Z 16:30CEST	orbit notes
go-ipfs	@whyrusleeping	10:00PDT 17:00Z 19:00CEST	go-ipfs notes
js-ipfs	@diasdavid	10:30PDT 17:30Z 19:30CEST	js-ipfs notes
libp2p	@diasdavid	11:00PDT 18:00Z 20:00CEST	libp2p notes

Please add any agenda items you have to the pad before the project-specific sprint call starts.

[RichardLitt]

I added a Mediachain call; @parkan let me know if this sounds good to you.

[flyingzumwalt]

Agenda item: A waffle board for ipfs/pm (and maybe add ipfs/community) https://waffle.io/ipfs/pm

[dignifiedquire]

@RichardLitt can you please update the calendar?

[daviddias]

I've added agenda items to js-ipfs and libp2p, please do so too if you have any.

• https://public.etherpad-mozilla.org/p/ipfs-2016-08-29-js-ipfs
• https://public.etherpad-mozilla.org/p/ipfs-2016-08-29-libp2p

[parkan]

@RichardLitt one of our devs (who I would really like to participate) is in EEST (Greece) so this is a bit late for him, is it possible to do it earlier in the day tmw?

[RichardLitt]

@parkan Sorry, I should have gotten to this sooner (still figuring out the new system). Let's schedule a call for Wednesday?

[parkan]

Sounds good to me -- and I should have responded earlier too, but was on a long weekend 😄

[RichardLitt]

No worries! My bad for not catching this. :)

[ghost]

IPFS All Hands Call August 29th

Moderator: @dignifiedquire
Notetaker: @lgierth

Attendees

• @RichardLitt
• @diasdavid
• @victorbjelkholm
• @Kubuxu
• @flyingzumwalt
• @haadcode
• @jbenet
• @em-ly
• @dignifiedquire

Agenda

1. Roll call by alphabetical order (moderator)
2. Call for additional agenda items (moderator)
3. Milestones and (experimentally) a waffle board for ipfs/pm (and maybe include ipfs/community) https://waffle.io/ipfs/pm (@flyingzumwalt)
   • milestone 1: Implement new PM Model https://github.com/ipfs/pm/milestone/1
   • milestone 2: First Org Roadmap https://github.com/ipfs/pm/milestone/2
4. go-ipfs v0.4.3 review + changes
5. Newsletter
6. Identity Providers (Orbit and more) -- call?
7. Community announcement: Code for Philly distributed systems "course" Make sure the online learning materials connect to workshop materials from Code for Philly community#162
8. Moderator/notetaker for next time:
   • Moderator: @lgierth
   • Notetaker: @em-ly

Notes

• !!!we hit the hangouts participants limit!!! (again)
• milestones FYI, em-ly and flyingzumwalt will follow up
• The go-ipfs CR list: Code Review 0.4.2..0.4.3-rc3 kubo#3138 see the MUST part
  • will follow up in the go-ipfs hangout
• newsletter
  • supposed to cover everything since the workshop in lisbon
  • review it and add stuff, everone!
  • @RichardLitt wants to ship it shortly
  • New Newsletter! \o/ newsletter#52
• identity providers
  • @haadcode's integrating orbit and uport
  • there's more possible identity providers
  • e.g. the estonian e-citizenship
• @flyingzumwalt working on distributed systems course
  • walking from "i know how to code a bit" through all the pieces required for a go-ipfs adapter for noms
  • was that "noms"?
• next week
  • notetaker: @em-ly
  • moderator: @lgierth

[RichardLitt]

@lgierth Can you PR the notes to this repo into meeting_notes, too?

[ghost]

ooh yep!

[ghost]

Sorry it committed it right away because I forgot changing the master-vs-PR radio button

[daviddias]

go-ipfs

Lead: @whyrusleeping

Notetaker: @diasdavid

Participants

• @jbenet
• @RichardLitt
• @whyrusleeping
• @Kubuxu
• @lgierth
• @flyingzumwalt
• @victorbjelkholm
• @em-ly
• @diasdavid

Agenda

• 0.4.3 review
• js-ipfs interop milestone update
• ipld milestone update

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

• We've a "last mile" list of action items generated by Juan that need to happen before 0.4.3 release
• Some items will be ported to 0.4.4, which will be merged to master after 0.4.3 release
• js-ipfs interop
  • A new PR using the correct multicodecs is up
  • go-ipfs is going to support protocols with and without semver
  • current version of go-multistream is doing exact matching, however semver support is right there too, not the multivalidation mechanism required for the IPLD
• We have a SECIO that works in js-ipfs, but it hasn't been tested for the go-ipfs platform
  • github issue here: https://github.com/ipfs/js-libp2p-ipfs/issues/15 (@whyrusleeping to create the scripts listed on that issue)
• multibase is implemented
• whyrusleeping has made a go-cid package
  • Create a README (@jbenet)
• go-cid will be integrated this week
  • replace the use of multihash by CIDs (because this is backwards compatible)
• Should peer-id change to use CID as well?
  • Discussion needs to happen
  • Let's piggyback on that discussion the change from /ipfs/ to /p2p/
• We are getting close to have 80% code coverage, this doesn't include the core/commands (the CLI). Next: figure out how to get code coverage from the sharness tests.
• go-ipfs Project Roadmap
• WIP Roadmap - https://docs.google.com/spreadsheets/d/1sQSkjTgft84qGs9bru6Qvegtd3dz3ROgQmLQBFMDstU/edit (not accessible, @em-ly could you check that?)
• @em-ly is working with matt to get the go-ipfs roadmap and pm set up - Test out the PM Process on go-ipfs Project #153
  • current roadmap: Q3 Roadmap: go-ipfs #127
  • @em-ly yo update the github issue with what is in the google drive spreadsheet
  • @whyrusleeping has created milestones https://github.com/ipfs/go-ipfs/milestones in github that describe what needs to be done for each milestone.
• @jbenet Code Review of 0.4.3 - @whyrusleeping is reviewing it

@whyrusleeping wanna review these notes and PR it to the meetings notes folder + create issues (or linking to the ones already existing) for tracking purposes? :) Thank you!

[RichardLitt]

@diasdavid Might be easier to make a PR, and then have @whyrusleeping review the PR.

[jbenet]

PMing thing -- Request for people to write their mechanics down

• Please write whatever "implementations" you plan to use in this issue: Define options for the Mechanics of Tracking Project Milestones #154 -- the goal is to surface them all there so we are all aware of them as we go into the mechanics.
• ATM it's missing "GH Milestones as Milestones" (@haadcode, @whyrusleeping), "GH Labels as Milestones" (@diasdavid).
• There are probably others.

[daviddias]

libp2p Action Items from Sprint discussion

• @ALL Take a look at the new Roadmap and share your thoughts. Update project roadmap libp2p/libp2p#2
• @RichardLitt will stub out the website // design by EOD Tuesday
• @diasdavid and @richard chat tuesday, make a roadmap for libp2p.io
• @lgierth and @RichardLitt work on IPNS tool for launching ipld.io or similar on Monday late day.
• @gavinmcdermott to work on the pubsub-testnet this week, will ping @diasdavid for feedback

Other:

• @diasdavid: surface the PM mechanics as soon as possible.

[parkan]

@RichardLitt can we get an approx call time for tmw so we can plan around it?

[daviddias]

js-ipfs Action Items from Sprint Discussion

• pull-streams endeavour
  • Create halfClosed conn upgrade
  • Fix WebSockets issues found [WIP] Add secio & move to pull-streams libp2p/js-libp2p-switch#67 (comment)
  • Test libp2p against go-libp2p
    • https://github.com/ipfs/js-libp2p-ipfs/issues/15
• interface-ipfs-core endeavour
  • spec out and create tests for bitswap and run them through js-ipfs + js-ipfs-api
  • swarm tests Use interface-ipfs-core tests for files API over http js-ipfs#438 (focus on pull-streams first)
    • needs: Support dialing without knowledge of the peerId (go-ipfs interop) ipfs-inactive/js-libp2p-ipfs-nodejs#16
  • Use interface-ipfs-core tests for the Swarm API js-ipfs#439
    • needs: .add/files.add http-api endpoint js-ipfs#323 (@Voxelot)

[jbenet]

@parkan does 1p work for you guys?

[parkan]

@jbenet yep!