-
Notifications
You must be signed in to change notification settings - Fork 29
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
GUI & In Web Browsers Weekly Sync 2018-10-29 #125
Comments
A little birdie has told me this would be a great call for me to attend, but it's currently scheduled at 5:30am my time (East Coast US), or will be once our daylight savings time realigns across continents. Any chance there's flexibility to move it to a time that's more friendly to non-Europeans without making you all work late? |
Some options are
Monday was chosen previously as it sets us up for the week. I could live with friday being demo and planning day. If we go for monday 4pm, it sets us up for up to 2hrs of calls back to back, which is either terrible or a good way to batch it all up. What are your thoughts @lidel @alanshaw @fsdiogo @hacdias |
I'm cool with either. Mildly in favour of Monday to get all of my meetings out the way for the week! |
I'd be happy with either and am happy to defer to the rest of you, who
probably have far more crowded calendars than I do at the moment.
…On Mon, Oct 29, 2018 at 12:13 PM Alan Shaw ***@***.***> wrote:
I'm cool with either. Mildly in favour of Monday to get all of my meetings
out the way for the week!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASSIiRXj5Q24Umv_4waJuX0wWNsuAoA3ks5upyk5gaJpZM4X5JMf>
.
--
*Teri Chadbourne, CMP*
Community Manager
Protocol Labs <https://protocol.ai/>
Twitter <https://twitter.com/eventteri> | GitHub
<https://github.com/terichadbourne>
|
My vote would go for Monday! |
In past doodle worked quite well in effort to maximize everyone's happiness :) Please fill your picks for next week's time: We will make it work! |
I can't go to either of those times. Everything I'll say is in GMT+0. I just can in the mornings or Wednesdays all day. |
One option is Wednesday at 4pm to 5pm UTC, a mid week check in! Another is we leave the meeting where it is and get better at sharing the output, and ensure people know where to find the video of the most recent meeting. |
4-5 UTC on Wednesdays would be fine for me. My vote of course is for a time
when I can feel like I'm contributing instead of just catching up after the
fact. :)
…On Tue, Oct 30, 2018 at 8:20 AM Oli Evans ***@***.***> wrote:
- To work for US/EU cross over, it's gotta be after 3pm UTC or later
(8am in SF, 11am NYC).
- To work with @hacdias <https://github.com/hacdias>'s studies it's
gotta be 10am or wednesday
- We all kinda like mondays, but it's not a hard requirement
- The design team call is wednesday at 3pm UTC
One option is Wednesday at 4pm to 5pm UTC, a mid week check in! Another is
we leave the meeting where it is and get better at sharing the output, and
ensure people know where to find the video of the most recent meeting.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASSIifsuLXWoxAzoTIHjcA63LsBzk2Vyks5uqEP2gaJpZM4X5JMf>
.
--
*Teri Chadbourne, CMP*
Community Manager
Protocol Labs <https://protocol.ai/>
Twitter <https://twitter.com/eventteri> | GitHub
<https://github.com/terichadbourne>
|
Sounds like Wednesdays @ 4 UTC work for everyone so I changed the Community calendar to reflect that. |
Cool 😄 |
Let's do a quick call today to kick it off! @lidel @fsdiogo @hacdias @terichadbourne @alanshaw |
I am afraid today is too short notice. Let's test new time next week, on 2018-11-07 (#127) |
Agenda for next week's sync in editable hackpad at https://hackmd.io/IA2zEXsRSHC9iSYQGhufaw#
The text was updated successfully, but these errors were encountered: