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

IPLD bi-weekly sync #720

Closed
vmx opened this issue Oct 17, 2018 · 19 comments
Closed

IPLD bi-weekly sync #720

vmx opened this issue Oct 17, 2018 · 19 comments
Assignees

Comments

@vmx
Copy link
Member

vmx commented Oct 17, 2018

As the IPLD Working Groups grew a bit (with temporary and permanent members), we could make a bi-weekly call to sync up. AFAIK the current members are based in CET and PST. So what I guess PST morning would be most convenient for most.

I'm probably the least busy person meeting wise, so everyone please speak up when you've time.

/cc @mikeal @Stebalien @warpfork

@mikeal
Copy link
Contributor

mikeal commented Oct 17, 2018

I am 100% on-board with this, but I'm also out the rest of this week and next week so I will probably miss the first one :)

@daviddias
Copy link
Member

💯 👍🏽

Also, ping folks from #484, namely @wanderer, @hermanjunge, @jonchoi, @dryajov, @magik6k and @b5

@vmx a good way to find a time for the call is just to set up a doodle and let people vote. Definitely give more weight for the folks that are actively working on the project (i.e. that have OKRs), but also try to maximize attendance.

@daviddias
Copy link
Member

daviddias commented Oct 21, 2018

Potentially, you could just alternate with the libp2p biweekly that happens every other monday
image

@Stebalien
Copy link
Member

Alternating works best for me.

@vmx
Copy link
Member Author

vmx commented Oct 22, 2018

Alternating with another meeting sounds great. So the current proposal is meeting every other Monday at 17:30 UTC.

@dryajov
Copy link
Member

dryajov commented Oct 22, 2018

@vmx that works for me

@vmx
Copy link
Member Author

vmx commented Oct 31, 2018

OK, so the first call will be Monday 2018-11-12 at 18:30 UTC.

Should this be a public call? Please vote:

  • Thumbs up: public
  • Thumbs down: private

If you don't want to vote publicly, just drop me a message through other channels.

@Stebalien
Copy link
Member

It should definitely be public. However, it doesn't necessarily need to be recorded or streamed.

@mikeal
Copy link
Contributor

mikeal commented Oct 31, 2018

I'm a +1 for public and recorded. I've found the recordings quite useful in other WG calls.

@daviddias
Copy link
Member

+1 to public and recorded as well, specially in such a time of refreshing the org, there is a lot of resync'ing to do within the team and the community that follows IPLD for a while :)

@lanzafame
Copy link

Australians appreciate working groups that record meetings between 2-9pm UTC ;)

@vmx
Copy link
Member Author

vmx commented Nov 2, 2018

May someone either add this new bi-weekly call the community calendar or give me permission to do so?

@daviddias
Copy link
Member

@vmx invited you and @mikeal to be able to change and create events on that calendar.

@vmx
Copy link
Member Author

vmx commented Nov 2, 2018

I've added it to the community calendar. Though I didn't know which Zoom to use (I really don't have a clue how we use Zoom for community meetings :)

@daviddias
Copy link
Member

@vmx There is this sweet tutorial at https://github.com/ipfs/pm/blob/master/HOST_A_CALL.md

@daviddias
Copy link
Member

@vmx where will be the notes be taken?

@vmx vmx self-assigned this Nov 5, 2018
@vmx
Copy link
Member Author

vmx commented Nov 5, 2018

Just for everyone's information. I'm taking care of that the call actually happens and has all the infrastructure setup to actually have this public recorded talk.

@vmx
Copy link
Member Author

vmx commented Nov 8, 2018

We now have:

@daviddias
Copy link
Member

And all of this is tracked on the fresh ipld/team-mgmt repo https://github.com/ipld/team-mgmt#bi-weekly-call

Closing this issue here :)

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

6 participants