-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recurring Sync Meeting #16
Comments
2018-12-03 libp2p Biweekly Update |
@bigs @mgoelzer Is there an update for 2019-01-28? |
Is it worth posting the next meeting links now? |
Anyway to set up a community calendar reminder for this, it's common practice for the other ipfs/libp2p calls. |
Yes, there's a recurring calendar event (link) on this repo's README.md. The event is from the libp2p Public Events calendar, which people can also add in their calendar software. Other than the bi-weekly call, there are not a lot of libp2p public events currently. But that may change in the future. |
Should the calendar be updated? |
I think we need to specify the time each meeting takes place now that we are time bimodal @bigs |
2019-04-29 libp2p weekly sync (australian friendly edition)Note: I am on vacation this week and nominate @anacrolix to lead! Further note, this event is not recurring on my calendar and I don’t know the exact UTC time. |
[Canceled, Async Updates Only] Monday March 16, libp2p weekly sync
|
[Canceled] Monday March 30, libp2p weekly syncSeveral members of the libp2p team will be unavailable for the sync today so it has been canceled. |
[Cancelled] Monday May 11, libp2p weekly syncA majority of the libp2p core team will not be available for the weekly sync on Monday, May 11th, so the sync has been cancelled. See everyone on the 18th! |
Monday June 22, libp2p weekly sync
|
Todays meeting, June 22, will consist of async updates only. We won't be meeting. |
Monday June 29, libp2p weekly async updatesWe will be doing async updates only again this week. Note: We are currently working on evaluating the future of this meeting to provide better channels for collaborating with the core team., and gaining a better view into the latest/upcoming libp2p efforts. |
We are cancelling this meeting going forward and will be transitioning to an aggregate post on the libp2p forums, https://discuss.libp2p.io. The goal here is to provide a better forum for asynchronously creating and collaborating on what's going on in libp2p, a synchronous meeting that is outside of the normal hours of a lot of community members is not a good forum for this. |
Inspired by the go and js core weekly meetings, we're moving the libp2p biweekly meeting to a format where a fresh notepad is posted on this thread in advance, so libp2p contributors who can't make the call can share their updates.
The text was updated successfully, but these errors were encountered: