Sprint Oct 12th

[RichardLitt]

Sprint 37

Date: October 12, 2015

Sprint Goals

• Ship 0.3.8

Sprint Discussions

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

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

• Apps on IPFS notes: https://pad.okfn.org/p/sprint-37-apps-on-ipfs
• node-ipfs notes: https://pad.okfn.org/p/sprint-37-node-ipfs

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.

Participants

At sync time

daviddias, lgierth, kyledrake, krl, RichardLitt, whyrusleeping, dignifiedquire

With deliverables this week

• daviddias
• lgierth
• kyledrake
• krl
• richardlitt
• whyrusleeping
• dignifiedquire
• jbenet
• mappum
• noffle
• ike
• amstocker

@dignifiedquire

electron-app

• Packaging setup
  • Fix issue with inifinite applications started :(
  • Automated release process (build and push to github releases)
• Documentation
  • Components
  • File structure
  • Used libraries-
• Rename to IPFS Station

WebUI

• Start work on mockups for the new design

@krl

• ipfs webcomponents
  • best practices, frameworks
  • tooling, versioning, etc

@kyledrake

Recap from last sprint:

First sprint. Last week I did some initial work on setting up DMCA compliance. I also did some work preparing for the libp2p announcement, including copy for a blog post. Next week is mostly a continuation of that work. New item is copy for the Electron app announcement. I have a talk this Saturday at BSides that will discuss IPFS. I also want to start getting us on a more active blog cycle. We're doing a ton of great work here that isn't getting the attention it deserves because we're not talking about it.

DMCA

• Approval from jbenet on DMCA items, and required info.
• Get access to company virtual mailbox to be able to check for DMCA letters.
• Register a Protocol Labs a fax line (lol)
• Fill out Interim Designation of Agent to Receive Notification of Claimed Infringement form.
• Send form to copyright office with check, will be expensed to Protocol Labs ($105)
• Initial DMCA takedown info page (example: ipfs.io/dmca.html).
• Figure out process for DMCA takedowns (list of hashes?)
• Coordinate with @lgierth on DMCA denylist (see implement access control lists for gateway kubo#1551)

Blog and Outreach

• Finish draft of libp2p announcement
• Work to improve the libp2p web site
• Announcement post for Electron app (see Name bikeshedding ipfs-desktop#46)
• Finish BSides Talk
• Work on getting a process for more frequent blog posts.

@lgierth

_ 🌴 No tasks this week_

@whyrusleeping

• ship 0.3.8
• fix goprocess panic in swarm/dialer
• improve address dial ordering
• PR to gobuilder to fix ipfs builds
• get numbers for ipfs transfers over WAN
  • tool to simulate WAN on a virtual net
  • docker test environment and scripts for benchmarks

@RichardLitt

• Work on IPFS-Textbook. Deliverables: A read through and edit; close all PRs and issues; update glossary.
• Help @jbenet with email lists. (logistics)

README Overhaul

• Add -contribute.md files to community list. Do Go and Node. go-ipfs#1734
• PR the Readme standards and guidelines.
• Build a README parser and standard checker. Test IPFS repositories with it.

API Documentation

• Close gencmdref issue for the website go-ipfs#1735
• Work on the HTTP api for ipfs/go-ipfs

@diasdavid || @daviddias

• ipfs-blob-store
• ipscend+c3 planning/building
• Make a case for blogging on IPFS (what are the tools we can use out there and how can we make it interesting)

@amstocker

Python ipfs api:

• started docs: python-ipfs-api.readthedocs.org
• now support file streaming for large uploads/downloads
• async implementations for gevent, asyncio, etc

  Other:

• pubsub on ipfs research, SSB on ipfs, CRDTs on ipfs
• distributed web forum on ipfs built on CRDTs

@ike

indie-comments:

• consider initial project goals
• work on user stories
• outline initial MVP UX

[jbenet]

we should probably just deploy our own damn etherpad until we make one on ipfs.

[dignifiedquire]

we should probably just deploy our own damn etherpad until we make one on ipfs.

What exactly is the benefit in the current structure of the sessions for an etherpad, as far as I can tell everybody is just pasting his or her goals for the week and then it gets copied over to github. So why not just post it as a comment directly on github?

[jbenet]

benefits

• we sometimes discuss the todos in the hangout
• time to edit it and all edit at once
• people can help reallocate for each other, and so on.

this is more vestigial from when i had more time to PM better.

we could move to:

• everyone post an individual comment on the sprint issue and not have one comment at the very top.
• have a better PM than me

[RichardLitt]

Why don't we try posting individual comments in the sprint issue this week? I want to see if that works, I suspect it will work just as well. Combined with a list of attendants at the top, it'll streamline my efforts, anyway. I haven't seen anyone edit it async in the past few weeks.

I'm just the sprint master, not a PM, so I don't know if I can help completely, but I think that would be a smart thing to do.

[daviddias]

SPRINT UPDATE

• figure out things for SF Meetup (meetup.com madness, etc)
• Get things together to be nominated for Computer Society Distinguished Lecturer Program http://www.computer.org/web/chapters/speaker-nomination
• npm on IPFS
  • ipfs-blob-store with mfs
  • registry-static working with ipfs-blob-store
  • Get all of npm inside IPFS (blocked, need to have good Internet for 24h++, planning on doing that 1st thing when I get back to Lisbon on Sunday)
• Node.js Interactive Logistics (request travel fund, etc)
• collect IPFS meetups all over the world add meetups list and some assets useful for meetup.com community#56
• make a notes for blogging case on IPFS Use IPFS to host a Blog (or similar type of website) notes#66 (get that discussion going), explore how harp can help us achieve that (basePath kennethormandy/hb-casper#3)
• Merkle Tuesday Hangout
  • https://etherpad.wikimedia.org/p/merkle-tuesday
  • Merkle Tuesday dat-ecosystem-archive/datproject-discussions#29

[dignifiedquire]

Sprint Update

Station (was electron-app)

• Merge big refactoring
• Rename electron-app to station
• [~] Setup automatic release process for station
• Fix Fork bomb in electron jbenet/node-subcomandante#2 to avoid fork bombing ourselve in packed versions
• Extract location formatting into ipfs-geoip (Lookup pretty ipfs-shipyard/ipfs-geoip#3)

(Web)Components on IPFS

• [~] Discussions with @krl about possible solutions
• Webpack sample for packaged components served from ipfs (https://github.com/Dignifiedquire/components-on-ipfs)

node-ipfs-api

• [~] Setup browser tests using karma (Start implementing browser tests using karma ipfs-inactive/js-ipfs-http-client#78)

WebUI

• Research on current functionality
• [~] First draft on how the new design should look like: https://ipfs.io/ipfs/QmTr8oTzi1upsHhHoK3ixmsxosD7hFMuMgbEZSakMRbTUT

Misc

• Create https://github.com/ipfs/awesome-ipfs (still empty though)

[whyrusleeping]

• ship 0.3.8
• fix goprocess panic in swarm/dialer
• fix goprocess panic in bitswap
• improve address dial ordering
• add system diagnostics command
• add local flag to ipfs name resolve
• aided in debugging of station
• PR to gobuilder to fix ipfs builds
• get numbers for ipfs transfers over WAN
  • learn more about linux traffic control than i wanted to
  • PR against dockers libnetwork
  • tool to simulate WAN on a virtual net
  • docker test environment and scripts for benchmarks

[jbenet]

@jbenet's update

• blockchain workshop in hong kong -- this took up most of my time last week.
• @epicenterbtc interview released
• catching up on github discussions + CR (a bit behind still)
  • ipfs update
  • ipfs hosting binaries plan
• help @whyrusleeping land go-ipfs 0.3.8
• find space for SF meetup
• merge fixes for node-subcomandante, vinyl-multipart-stream, website
• lots of admin things
• lining up various meetings this week
• prep for talks this week -- http://web.stanford.edu/class/ee380/Abstracts/151021.html

[RichardLitt]

@RichardLitt's update:

• Worked on the calendar
• [~] Worked on IPFS textbook
• PRed go-contribution-guidelines.md
• [~] Worked on README standards and finding a parser; still working on that.
• [~] Looked at starting HTTP api for ipfs/go-ipfs; still preliminary
• Helped juan with Email lists
• Close gemcmdref

[chriscool]

@chriscool's update:

• first version of Sharness coverage script
• tests for ipfs commands in t0010 and related cleanup
• helped implement ipfs commands --flags
• first try at handling no nc in t0060
• added a few issues about the build infrastructure

[ike]

@ike's update:

I got laid off this week, so I made no progress on indie-comments. If anybody has any leads on front-end dev or bizdev gigs, I'd be super appreesh.

indie-comments:

• consider initial project goals
• work on user stories
• outline initial MVP UX

[RichardLitt]

New sprint! #40

[davidar]

@davidar's update:

• still working on TeX.js
  • discussing how to get this applied to the arXiv corpus arXMLiv / CorTeX ipfs-inactive/archives#31
• started discussions about integrating @hypothesis with IPFS
• slowly making progress on BASE ipfs-inactive/archives#3
• spreading the word about CRDTs Aggregation --> CRDTs discussion notes#40 ;)