Sprint: Aug 8 → Aug 14

[RichardLitt]

Sprint August 8th--August 14th

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	pad-all-hands
pubsub	@diasdavid	10:00 PDT 17:00Z 19:00CEST	pad-pubsub
IPLD	@nicola	10:30PDT 17:30Z 19:30CEST	pad-IPLD
js-ipfs	@diasdavid	11:00PDT 18:00Z 20:00CEST	pad-js-ipfs
libp2p	@diasdavid	11:30PDT 18:30Z 20:30CEST	pad-libp2p

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

[RichardLitt]

Proposal for a breakout call: mfs and ipfs files. See this issue.

[flyingzumwalt]

Proposal for discussion: Renaming libp2p-swarm to net-machine. See this issue.

[RichardLitt]

Proposal for discussion: pubsub. See this comment.

Proposal for discussion: IPLD. See this issue.

[daviddias]

Can we get an update on the community calendar as well?

[RichardLitt]

@diasdavid Do you still see those? Did you just take that screenshot? It should only show the All Hands Call today.

[daviddias]

yeah, the screenshot was from just now, I still see them.

[flyingzumwalt]

FYI I've updated the agenda etherpad for the all hands call with all the proposals from this thread.

[daviddias]

All solved, my calendar looks good. Seems that it was a sync problem.

[jbenet]

thanks @flyingzumwalt for running the all-hands! it was great! ❤️

[daviddias]

PubSub notes and repo for further discussions -> libp2p/research-pubsub#1 (comment)

[RichardLitt]

To Do this week

Multiformats

• Standardize all of the READMEs
• Assign owners to the repos
• Design and deliver a basic

Extra

• Get project-repos working with the commit messages repos('philschatz/octokat.js').commits.fetch() returns an empty string philschatz/octokat.js#107
• First draft of a README at https://github.com/RichardLitt/awesome-opsec
• Review the proposed ipfs/pm changes in (WIP) Project Management Process document #131

Please feel free to bring anything else to my attention.

[RichardLitt]

IPFS All Hands Call 08 August 2016

Moderator: Matt Zumwalt (@flyingzumwalt)

Notetaker: Richard Littauer (@RichardLitt)

Attendees

• @nicola
• @RichardLitt
• @jbenet
• @flyingzumwalt
• @haadcode
• @em-ly
• @dignifiedquire
• @diasdavid
• @betaphors
• @Kubuxu
• @haadcode
• @gavinmcdermott
• @ReidWilliams

Agenda

1. Roll call by alphabetical order (moderator)
2. New call/sprint format and Community Calendar - issue 134 and this comment
3. Call for additional agenda items (moderator)
4. Checking in on the GitHub issue. (@diasdavid)
5. PM Process Discussions PR 131 (@flyingzumwalt)
6. Proposal for a breakout call: mfs and ipfs files. See [this issue]
7. Proposal for discussion: pubsub. See this comment. (@diasdavid)
   (Unite the Files API 🗂 specs#98 (comment)). (@diasdavid)
8. Proposal for discussion: IPLD. See this issue. (@nicola)
9. Schedule for the day
10. Renaming libp2p-swarm to net-machine. See this issue. (@diasdavid)
11. RFI about Q2 Update (jbenet)
12. Moderator/notetaker for next time:
    • Moderator: @flyingzumwalt
    • Notetaker: @dignifiedquire

Notes

• Raise questions by raising hands.

New format for quick round

• type of discussion:
  • Cross-cutting
  • Need discussion
• delegate conversations for later
• moderator
  • can rotate
  • keeps things on track
  • keeping things rolling
  • keepin' it smooth

Agenda items

• write them on github
• announce them at the beginning of the call
• writing them in the PAD

Checking in for Github

• We should continue to check in on the Sprint issue
• But this isn't happening
• We should also have a section about things which we said we could do, but don't
• @jbenet: I don't know if we're going with Kanban or Agile, or so on, and this will make sense later. Super important to track though.
• @dignifiedquire: Writing the tasks is a waste of time if we have Boards. We need to be able to check things at places in time, though, and take a screenshot (or some other way of capturing time-sensitive information), once a week or so.
• @jbenet: We can discuss this, and what models we want, on GitHub
• TODO: @diasdavid Open a GitHub issue about this topic so we can discuss it async

PM Process Discussions

• Note for new people: We are working on our process right now; in particular, we're trying to get our model down.
• After Lisbon, the goal is to put together a process for managing our projects in the IPFS community.
• We need to find a general-enough process that we can use, but that people can choose to opt into (or not).
• Some IPFS projects may need this now, however.
• So far, a lot of discussion about how we do PM. First, we've been figuring out the model - as @jbenet says, "figuring our the description for the process so that you can implement it with post-it notes if needed."
• There's a document in a PR ((WIP) Project Management Process document #131) that is good, and we're working on feedback for that
• We need some tool which can be automated, though: roadmaps, milestones, tags, and so on. Ideally, something does this all for you (CI hook, or something similar).
• @jbenet: What should people do this week while we hash this out?
• TODO: @ipfs/devs: Add your sprint todos this Monday for the following work, using the old method, while we figure out how we want this to look. Explicit decision: Use what we used to do that worked (aka huge markdown lists in the sprint issue).
• This pertains to: @richardlit, @jbenet, @flyingzumwalt, @haadoce, @dignifiedquire, @diasdavid, @Kubuxu, @whyrusleeping, @nicola
• Anyone want to get involved, but havent yet?
• @RichardLitt: Waiting becuase there are a lot of cooks, would like to get involved when you feel it is a good time.
• @dignifiedquire: I'd also like to know, but when there is a draft.
• @haadcode: Review it this week; next week is tooling.

MFS

@jbenet: All the bike sheds! Can we do this over GitHub?
@diasdavid: If we commit to that, but over a couple of days, not two months, if possible?
@jbenet will do.

PubSub

@diasdavid: Breakout Discussion!!

• What do we do with our time, research, prototype, and so on.

When: Immediately after this call

IPLD

Scheduled.

Renaming

@diasdavid: Should be part of the libp2p discussion
@jbenet: I can't make that call, and this should be on github.
TODO: Can we prioritize that issue? (Yes)

RFI about Q2 Update

@jbenet: I'm preparing an update on Q2 for the whole IPFS project. Highlighting a lot of important things, too.
I will post a skeleton or a draft and tag relevant people about this (also needs pictures!).
@RichardLitt: Let me haaaalpp

Done. Retrospective

Done in under 45 minutes. We'll tighten this up.

[daviddias]

David Dias TODO

• interface-ipfs-core endeavour
  • write spec for:
    • name name API ipfs-inactive/interface-js-ipfs-core#37
    • dht DHT API ipfs-inactive/interface-js-ipfs-core#36
    • swarm swarm API ipfs-inactive/interface-js-ipfs-core#35
    • pinning pinning API ipfs-inactive/interface-js-ipfs-core#34
  • review, fix and merge ipfs.get PR on js-ipfs-api and interface-ipfs-core
    • feat/ipfs.files.get ipfs-inactive/js-ipfs-http-client#337
    • feat/ipfs.files.get ipfs-inactive/js-ipfs-http-client#337
  • revisit the files API proposal: Files API - dot return DAGNodes on Add ipfs-inactive/interface-js-ipfs-core#29
  • ipfsFactory - ipfsFactory - Tests that require more than one IPFS node ipfs-inactive/interface-js-ipfs-core#53
  • tests for:
    • name name API ipfs-inactive/interface-js-ipfs-core#37
    • dht DHT API ipfs-inactive/interface-js-ipfs-core#36
    • swarm swarm API ipfs-inactive/interface-js-ipfs-core#35
    • pinning pinning API ipfs-inactive/interface-js-ipfs-core#34
• pubsub
  • curate and organize the info on pubsub and move it to the pubsub repo
• interop tests between js-ipfs and go-ipfs
• 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
• review pm doc

[dignifiedquire]

dignifiedquires Todo

• Validate pull-streams are a viable alternative to our streams issues 🎉 ✅
• pull libp2p (ref refactor: ⎆ Migration to pull-streams (from Node.js Streams)  js-ipfs#403)
• pull js-ipfs (ref refactor: ⎆ Migration to pull-streams (from Node.js Streams)  js-ipfs#403)

[nicola]

Nicola's todos

• write down pub-sub skeleton issue (see Sprint call notes from 08 August 2016 libp2p/research-pubsub#1)
• clean up the results from the first IPLD call (see IPLD spec refining call - round 1 #124)
• close all the issues we have agreed about IPLD
• write first draft of new IPLD spec
• sync with @jbenet about the IPLD papers