-
Notifications
You must be signed in to change notification settings - Fork 60
WASM WG Team Meeting #2 #80
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
Comments
I can't seem to ping the WG but if you haven't please fill out the doodle for this week! |
Hey everyone the largest overlap seems to be this Thursday. We'll do the meeting from 2pm to 3pm UTC-4 (check your timezone here which I've input my city to compare to). We'll use Google Hangouts again for now since it worked well last time. I'll leave the link to the hangout both here and on #rust-wasm 15 minutes prior to the meeting! If you have anything to discuss please put it in the agenda. I'll be filling it out with some exciting things that I've done and what I've heard from some others this past week, but it'll be good to hear and catch up on anything that we might need to discuss. If there's not much we can keep the meeting short :) |
Just a reminder that today is the meeting! |
Link for the meeting in 10 minutes: |
Realtively short meeting today:
Overall a short meeting thanks to everyone who attended! |
As we all discussed in the Team Meeting today 3/8/2018 we've decided to run a meeting every two weeks. @fitzgen will be out for the next meeting so I'll be walking us through discussion points.
The agenda is located here if you have items that you want to bring up or talk about please drop them in there!
Please put in what times you're available in this doodle here! If we need more flexibility with the times I can add more, but if we end up with the same as last time we might just want to make 19:00 UTC a default.
We'll post a link as the time approaches in #rust-wasm irc channel. If everyone is fine with it let's continue with Hangouts for now.
The text was updated successfully, but these errors were encountered: