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

Sprint: Sept 12 → Sept 18 #174

Closed
RichardLitt opened this issue Sep 5, 2016 · 14 comments
Closed

Sprint: Sept 12 → Sept 18 #174

RichardLitt opened this issue Sep 5, 2016 · 14 comments

Comments

@RichardLitt
Copy link
Member

RichardLitt commented Sep 5, 2016

Sprint for September 12th

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

Calendar

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

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

@RichardLitt
Copy link
Member Author

Times will be locked down on Friday. Please discuss before then.

@whyrusleeping
Copy link
Member

Agenda items for libp2p:

milestone 2:

  • move connection closing to later milestone. Its not feasible currently.
  • Actually discuss moving away from dht.
  • Discuss progress on relay
  • Outline action items for improvements to NAT traversal

@RichardLitt
Copy link
Member Author

RichardLitt commented Sep 8, 2016

Process question

@flyingzumwalt @dignifiedquire pinged you and me on that issue; in the future, we should encourage that they just add it to the agenda, and then they don't need to rely on us to bring it here, right?

@daviddias
Copy link
Member

@RichardLitt it is a way to inform the PMs that something needs discussed and act upon, hopefully we get into a state something can be resolved even before waiting the sprint call.

@RichardLitt
Copy link
Member Author

@diasdavid Sure, it is a way to inform the PMs. But I am not the PM, there, so I'm not really sure what to do with the information. Wouldn't it be better to post any agenda stuff in here, as opposed to pinging me? :)

@RichardLitt
Copy link
Member Author

Hmm. I noticed I used the template in the repo, which doesn't match how we've done video calls for the past two weeks.

Proposals:

  • We move to go-ipfs, js-ipfs, and libp2p, in that order.
  • We start go-ipfs at 17:00UTC instead of 17:30UTC, because we haven't needed the extra thirty minutes in the past few weeks, and this keeps the calls shorter.

I am going to make both of these two changes by 2100UTC today, if no one comments, and then lock down the schedule for Monday.

How does this sound? @diasdavid @whyrusleeping @dignifiedquire @lgierth @flyingzumwalt

@RichardLitt
Copy link
Member Author

🔒 time is now closed. This is what will be happening on Monday.

@flyingzumwalt
Copy link
Contributor

Added agenda item for the all-hands: Second Draft of PM Process Document (View the Draft or the Pull Request)

@parkan
Copy link

parkan commented Sep 12, 2016

can we get a quick mediachain sync call in for the week? probably only need ~15 mins

@whyrusleeping
Copy link
Member

@parkan Yeah, we can do that. @diasdavid and I are also about two blocks from your office right now, so if you want to meet in person again that works too.

@parkan
Copy link

parkan commented Sep 12, 2016

@whyrusleeping would be down to meet for lunch, trying to msg you on freenode but the web ui is being finicky

@whyrusleeping
Copy link
Member

@parkan No worries, meeting for lunch works for me, @diasdavid thoughts?

@jbenet
Copy link
Member

jbenet commented Sep 12, 2016

@flyingzumwalt how did we want to gather feedback/retrospective for sprints? (i remember an issue about fantastic, but i'm not finding it)

@flyingzumwalt
Copy link
Contributor

@jbenet I outlined the idea here: #170

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants