You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally, I think there would be a meeting on the odd weeks ~11-13UTC, preceding one of the two US/EU time slots. An EU/AF dev would become the "bridge" by attending at their lunch time and in the evening, to keep both regions informed. Unfortunately, that means extra responsibility and duties piled upon a small number of devs in Europe/Africa, who are available at both times.
@Kunde21 I think we decided that a single, rotating meeting time each week is less bad than a separate meeting for other time zones each week (see #852 (comment)).
What do you think of an every three week rotation, with one of the weeks being ~11-13UTC?
unfortunately, we are not doing dev meetings regularly anymore, partially because we can't find a good time for enough people to come. we have folks in GMT/CET time zones, North/South America time zones, and Asia/Pacific time zones! on the plus side, I'm proud that there are Athens users and developers all over the world. So, I am going to close this.
Sidenote: I do office hours and screencasts every once in a while, and I'm going to find some other ways for us to talk outside of GitHub.
We now have a rotation of times that are beginning to accommodate EU and North America time zones in #954 (comment).
As @Kunde21 mentioned in #954 (comment), we don't yet have a time in the rotation that is friendly to Asia/Pacific time zones.
This issue is for adding a time into the rotation that is friendly to those timezones.
The text was updated successfully, but these errors were encountered: