Sprint: Aug 15 → Aug 22

[RichardLitt]

Sprint August 15th

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	@RichardLitt	9:00PDT 16:00Z 18:00CEST	all-hands-call
go-ipfs	@whyrusleeping	10:00PDT 17:00Z 19:00CEST	pad-go-ipfs
js-ipfs	@diasdavid	10:30PDT 17:30Z 19:30CEST	pad-js-ipfs
libp2p	@diasdavid	11:00PDT 18:00Z 20:00CEST	pad-libp2p

We also inserted a discussion about http-api.

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

Please post below if you would like to have any calls after the All Hands Call.

[daviddias]

We need to talk about the HTTP-API -> https://github.com/ipfs/http-api-spec/issues/114

[RichardLitt]

@flyingzumwalt Should I add that as a call, now?

[RichardLitt]

@diasdavid Do you want to put it on the all-hands agenda, schedule a call for it, or cover it on the js-ipfs call?

[daviddias]

@RichardLitt Can you describe what is going to happen tomorrow? It seems that no hangouts are schedule other than a All Hands.

[RichardLitt]

I'm a bit new to this new format; I thought that we arrange the meetings during the call before hand. @flyingzumwalt can you help me here?

[flyingzumwalt]

I think the main sprint calls (in the sprint issue template) - js-IPFS, go-IPFS and libp2p - are always included by default. We just add agenda items to the all-hands and add/remove project-specific sprint calls like IPLD based on requests over the week.

[RichardLitt]

@diasdavid Added them. :)

[daviddias]

We also need to decide if we still want the config replace, by ipfs/kubo#2927 . @whyrusleeping @Kubuxu probably we can have this one in go-ipfs.

[daviddias]

Thank you @RichardLitt <3

I've added an agenda to js-ipfs and libp2p. Please, everyone, also add items to the agendas that you would like to see discussed.

[daviddias]

js-ipfs AI from the call

• CI Thread -> CI Infrastructure infra#100
• Cancelable requests -> https://github.com/ipfs/interface-ipfs-core/issues/58
• Enumerate all the tests for the new ipfsd-ctl Enumerate the tests in order to make sure that execa is as robust as subcommandante js-ipfsd-ctl#95 @jbenet
• @jbenet to follow up on Unite the Files API 🗂 specs#98
• dev go-ipfs builds for testing branch dev builds for js-ipfs testing kubo#3089

http-api AI from the call

• http-api-spec.ng -> https://github.com/ipfs/http-api-spec/issues/116

libp2p AI from the call

• @jbenet to ask @mikolalysenko for his pubsub notes and review of the pubsub repo
• interop scripts for testing https://github.com/ipfs/js-libp2p-ipfs/issues/15 @whyrusleeping
• libp2p harness for pubsub Design and build the harness for pubsub tests libp2p/research-pubsub#10

[RichardLitt]

Is there a need for the ####, or the multiple comments? :P

[daviddias]

@RichardLitt :D

[jbenet]

I like it because it's super attention grabbing :)

[RichardLitt]

I know you like it. :) But it also grabs the attention of everyone else, which can be very distracting.

[flyingzumwalt]

WHY ARE YOU SHOUTING AT ME.

[daviddias]

@flyingzumwalt Can we continue to keep the issue open during the sprint?

[flyingzumwalt]

I don't see why not. Seems like people use it to post little updates and to
find meeting notes.

Maybe we can close the previous week's issue when the following week's call
happens?

On Tuesday, August 16, 2016, David Dias [email protected] wrote:

@flyingzumwalt https://github.com/flyingzumwalt Can we continue to keep
the issue open during the sprint?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#141 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIestJl8o02SLD0KDc_GQlSMBetTqocks5qgWXwgaJpZM4JigX8
.

[daviddias]

@flyingzumwalt that is what we've been doing and I believe it is a good formula (I come back to sprint issue often) :)

[flyingzumwalt]

Oh I closed it! Lol. I didn't mean to close it. I must have hit the wrong button when I added a comment. Sorry.

[RichardLitt]

I was wondering about that!