Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Sprint: Aug 22 → Aug 28 #146

Closed
flyingzumwalt opened this issue Aug 20, 2016 · 27 comments
Closed

Sprint: Aug 22 → Aug 28 #146

flyingzumwalt opened this issue Aug 20, 2016 · 27 comments

Comments

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented Aug 20, 2016

Sprint Aug 22

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
js-ipfs @diasdavid 10:30PDT 17:30Z 19:30CEST js-ipfs notes
go-ipfs @whyrusleeping 11:00PDT 18:00Z 20:00CEST go-ipfs notes
libp2p @diasdavid 11:30PDT 18:30Z 20:30CEST libp2p notes
interfaces repr @jbenet 12:00PDT 19:00Z 21:00CEST interfaces-repr notes
mediachain @jbenet 12:30PDT 19:30Z 21:30CEST mediachain notes

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

@flyingzumwalt
Copy link
Contributor Author

@parkan has proposed a Mediachain collaboration call (see #145). Should we add that to the day's agenda? Discuss it in the all-hands?

@flyingzumwalt
Copy link
Contributor Author

Adding coveralls & code coverage to the agenda for all-hands. Just want to check in about where we're at with this.

@jbenet
Copy link
Member

jbenet commented Aug 20, 2016

I propose this discussion:

doesn't need to happen this week, nor on monday, but best for it to.

@flyingzumwalt
Copy link
Contributor Author

Added "Representing Interfaces, in libp2p doc repos and more" to the all-hands agenda, which might just involve identifying when/where to push that process forward.

@flyingzumwalt
Copy link
Contributor Author

Added "IPFS Tutorials in Gitbook form" as an agenda item for the all-hands. I'll be proposing this format for assembling the new Tutorials (and gathering/re-formatting the existing ones) See: https://www.gitbook.com/book/flyingzumwalt/decentralized-web-primer/details

@ghost
Copy link

ghost commented Aug 22, 2016

@whyrusleeping @Kubuxu @jbenet and I should talk about a vulnerability report we got, maybe the 17:00Z slot?

@parkan
Copy link

parkan commented Aug 22, 2016

Hello from team mediachain! Would love to get the following on the agenda:

  • large dataset providing: chatty provide on add, direct improvements, workarounds (add w/o provide, alt. routing schemes)
  • dataset add w/o copy: (re: avoid duplicating files added to ipfs kubo#875)
  • IPLD status/work needed (we want to help out!)

@jbenet
Copy link
Member

jbenet commented Aug 22, 2016

@parkan great! would a call at 3:30p work for you?

@parkan
Copy link

parkan commented Aug 22, 2016

@jbenet sure, works for me

@jbenet
Copy link
Member

jbenet commented Aug 22, 2016

ok great. we'll add that call at 3:30p. I updated the schedule: #146 (comment)

@parkan
Copy link

parkan commented Aug 22, 2016

@jbenet what do I dial into? should I get the url from IRC?

@RichardLitt
Copy link
Member

Yeah, I'll throw it in IRC.

@parkan
Copy link

parkan commented Aug 22, 2016

Good chat, cleared a lot of things up, have a path forward now (short-term). Thanks again!

One small thing: @vyzo is in EEST and having him participate in the future will be very valuable, is it possible to move the call up? We can likely do another day too, if the earlier hours are too packed.

@kevina
Copy link

kevina commented Aug 22, 2016

@parkan @whyrusleeping I was looking over the notes to the mediachain call and I would like to clarify one point concerning ipfs/kubo#875: I have only really broken compatibility once due to the datastore key change and I provided an upgrade path. (In the very early stage I might have changed the format a bit more, but that was well before I created ipfs/kubo#2634.)

@jbenet
Copy link
Member

jbenet commented Aug 22, 2016

@kevina thoughts whether CIDv1 or your PR should land first? if CIDv1 simplifies a lot, worth waiting?

@kevina
Copy link

kevina commented Aug 22, 2016

@jbenet, I would like to see my PR land first, CIDv1 will only simplify a small part that is now well isolated. My PR requires a number of infrastructure changes that I will like to get in ASAP.

@whyrusleeping
Copy link
Member

@kevina can you outline somewhere a revised list of tasks we need to do to get your PR in? things have changed a bit since you last updated your wiki landing page

@ghost
Copy link

ghost commented Aug 23, 2016

@lgierth todo

  • libp2p
    • add packet switching tasks to libp2p roadmap
    • update multigram spec draft
      • move spec to multiformats/multigram repo
    • start go-multigram implementation
  • go-ipfs
    • make docker image work with go1.7
    • fix branch naming of hub.docker.com/r/ipfs/go-ipfs
  • misc
    • work with an external contributor
    • prototype of ipfs-pages
    • review multihash RFC
    • fix ipfs.io/contact
  • org
    • work through email backlog
    • get up-to-date regarding project management, and comms
    • send out new monthly infrastructure report (bling bling)
    • set up waffle board for infrastructure
    • wrap up keythief postmortem
    • take notes about infrastructure role

@kevina
Copy link

kevina commented Aug 23, 2016

@whyrusleeping yes I plan to in the next day or so

@daviddias
Copy link
Member

daviddias commented Aug 23, 2016

js-ipfs goals for sprint

Notes from the Call

@daviddias
Copy link
Member

daviddias commented Aug 23, 2016

libp2p goals for this spring

@RichardLitt
Copy link
Member

What sort of documentation, @diasdavid?

@parkan
Copy link

parkan commented Aug 24, 2016

@diasdavid I think the DHT point is missing "disable providing with ipfs add --local"

@daviddias
Copy link
Member

Thank you @parkan, added :)

@dignifiedquire
Copy link
Member

@flyingzumwalt @RichardLitt can this be closed?

@RichardLitt RichardLitt removed the sprint label Sep 1, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants