Sprint: Oct 10 → Oct 17

[RichardLitt]

Sprint October 10

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

Calendar

Zoom and Stream links will be updated directly before the calls. Links to them will also be dropped in IRC, at the start of each call.

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

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

[RichardLitt]

We will be discussing the Q4 Roadmaps during this sprint.

From the blog:

Our next weekly call will be focused on roadmaps. We will be planning our roadmaps for the rest of 2016. You're invited to join in! We want to make sure the community is heard and involved as much as possible.

If you're interested in seeing the progress we've made with IPFS over the last few months or if you have something you want to see done in Q4, tune into these calls and chime in on IRC.

You are welcome to dial into these calls as a participant if any of the following are true:

• You maintain software that relies directly on IPFS
• You have done work on js-ipfs, go-ipfs, libp2p, orbit, etc.
• You plan to do work on the these projects in the coming months

To prepare for these calls, take a look at the video calls from last week, where we reviewed the third quarter roadmaps.

This is a diversion from our usual weekly schedule. As you may know, every Monday we have a series of calls to align work on IPFS for the following week. We announce the calls each week in an issue in ipfs/pm and on the #ipfs IRC channel. Next week, instead of following our usual routine, we're going to look at roadmaps. We will cover some of the work we plan to do in the next few months. In mid-October all of the project leads will be meeting in person to lay out our finalized roadmap for the rest of 2016.

If you'd like to weigh in on the process for the next two weeks, check out this issue and let us know! If you have never participated in the calls before and you plan to dial in as a participant on these roadmapping calls, please let us know you're coming by leaving a comment on that github issue.

[parkan]

Hey gang, would love to squeeze in a mini-call again next week if possible. We're moving forward rapidly and hitting lots of new corners 😄

Topics, roughly in order of importance:

• go-datastore: we're looking at both writing to the datastore directly from concat, and possibly implementing an alternate backing store under the interface to support our operating scale (500MM+ objects), based on a bitcask/haystack style design. Have a bunch of questions about Key/Query and minimum required set of behaviors to conform to the interface. Goal here is to share datastore between IPFS, concat, and (potentially) indexer.
• IPLD update?
• js-ipfs ECC keys: very happy to have ECC keys in go, would love to help get them into js too (planning to hack around this currently)

[dignifiedquire]

js-ipfs ECC keys: very happy to have ECC keys in go, would love to help get them into js too (planning to hack around this currently)

Hey @parkan this sounds great but please make sure to check out and base your work on libp2p/js-libp2p-crypto#12 as this will be merged very soon.

[parkan]

@dignifiedquire thanks for the heads up, that's an important set of changes 😄

[flyingzumwalt]

@parkan could you bring these things up on the js-ipfs and go-ipfs calls on Monday? We'll be discussing the Q4 roadmaps, so it's a perfect time to bring up topics like these.

Regarding an IPLD update, FYI we might push the IPLD call to Wednesday or Thursday instead of doing it at the time listed above.

[kevina]

I would very much like to see ipfs/kubo#2634 get merged and also think my multi-blockstore idea/implementation, ipfs/kubo#3257, could be very useful going forward. I am going to try and participate in at least one of these calls (likely go-ipfs, maybe the all hands). I might be able to give a quick demo if others would be interested. @whyrusleeping (and others) please advice.

[parkan]

@flyingzumwalt Monday is a holiday here so I think relevant parties may be afk; most of the discussion can wait until a bit later (weds should be good)

[flyingzumwalt]

@parkan that's right! I forgot about Indigenous People's Day. The Protocol
Labs people will be tied up in meetings all week. We will try to punch a
hole in the schedule for a call but might not have an opening until next
Monday (17-Oct).
On Fri, Oct 7, 2016 at 6:32 PM Arkadiy Kukarkin [email protected]
wrote:

@flyingzumwalt https://github.com/flyingzumwalt Monday is a holiday
here so I think relevant parties may be afk; most of the discussion can
wait until a bit later (weds should be good)

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

[haadcode]

Orbit call is missing from the schedule.

[flyingzumwalt]

@haadcode @RichardLitt I spoke with @nicola about this - please put orbit
in the IPLD slot this week. We will do the IPLD call on Wednesday. In
future weeks, IPLD will be after orbit (like last week) unless we decide to
cap the length of the Monday calls, in which case the IPLD call will
probably move to another day of the week.
On Sat, Oct 8, 2016 at 1:48 AM Haad [email protected] wrote:

Orbit call is missing from the schedule.

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

[nicola]

So no monday call on IPLD?

[RichardLitt]

Added Orbit calls.

[daviddias]

@RichardLitt can we bump Orbit up? Due to my recent travel incident, I'm afraid I might not be able to make it on time to the js-ipfs call as it is scheduled right now.

Hope that doesn't cause a conflict with others people schedules, I've had the misfortune of not making my flight due to a flight delay.

[RichardLitt]

I have no problem with bumping it up. Will you be able to make the js-ipfs call if it is half an hour later, though?

[daviddias]

I believe so, it gives me 70 minutes to go from Airport to the Hotel (http://www.worldtimebuddy.com/?qm=1&lid=100,6167865&h=100&date=2016-10-9&sln=18-19)

I would appreciate some directions for when I get to the Hotel, to rush to the room where the good wifi is :)

[RichardLitt]

Moved orbit up. :)

[flyingzumwalt]

@nicola yes. sorry for the confusion. We're moving the IPLD call to Wednesday so you can lead it after you've arrived here at Protocol Labs.

[RichardLitt]

We cannot stream today, due to a lack of equipment for this. Please join the calls and turn off your video and audio if you would like to follow along live. We will be recording the calls after.

[RichardLitt]

We now have a stream! https://beam.pro/Kubuxu

[flyingzumwalt]

@nicola I'd like to schedule this week's IPLD call at 18:00Z (2pm EST). Thank you for letting us bump it from the normal Monday slot. Does Wednesday at 18:00Z work for you? Does it work for Steven?

Is there anyone else who wants to participate in this week's IPLD call, which will focus on IPLD Q4 Roadmap?

[nicola]

@Stebalien, @mildred tell us when you can make it, any time works for me

[Stebalien]

Sorry, I'm in PDT and busy till 12pm (PDT). Does 19:00Z (3pm EDT) work?

[Stebalien]

I can probably participate asynchronously (over chat) now if you want but I won't be paying much attention.

[ghost]

@RichardLitt sprint issue for next week