Timezone Coordination - Autobot Strategy
So, here's a simple method of collecting where everyone is and how to track their availability. Please post a comma separated list of your availability in the format below. Those excel friendly people can can import that in (and I or a mod will periodically update this first post).
Format
Name, Timezone, Daylight Savings, Start, Stop, Days
Rules
-- Name must be provided to simplify copy / paste
-- Timezone should be UTC-# format per link in title
-- Daylight savings is just good to know, enter Yes if you observe it locally No if you don't
-- Start / Stop should be hour, half, quarter increments
-- Start / Stop should be in military time (to avoid confusion)
-- Start / Stop is local to your Timezone - do not convert to GMT
-- Days are valid as M, Tu, W, Th, F, Sa, Su
-- Ranges are acceptable for Days (e.g. M - Th)
-- Provide multiple entries for different Day ranges
Example
Wingspan, UTC-5, Yes, 8:00, 16:30, M - F
Wingspan, UTC-5, Yes, 7:00, 10:00, Sa
Closing Thoughts
So, post away. Smart excel people will post templates, I'm sure, on how to get this integrated. However, this data (if you compile it locally) will give you all you need to know who should be on whenever you're playing. Over time you should be able to coordinate builds to be effective (e.g. via the Repair Strategy; I love shameless self-promotion).
Posted Availability to Date
The ninnies have posted!!
(In order by UTC / GMT offest)
Kickyourassacons, UTC-8, Yes, 10:00, 19:00, M - F
Chocolate Thunder, UTC-6, Yes, 8:00, 17:00, M - F
Evolution Prime, UTC-6, Yes, 7:00, 16:30, M - F
ashe5k, UTC-5, Yes, 4:00, 13:00, M - Sa
Firebird, UTC-5, yes, 22:30, 2:00, M - Su
Conjurous, UTC-0, Yes, 16.00, 1.00, M - F
Conjurous, UTC-0, yes, 10.00, 1.00, Sa - Su
neliz, UTC+1, Yes, 9:00, 0:00, M - F, dachterberg@livingston.nl
neliz, UTC+1, Yes, 17:00, 0:00, Su, dachterberg@livingston.nl
MagnusLabel, UTC+8, No, 16:30, 22:30, M - F
Format
Name, Timezone, Daylight Savings, Start, Stop, Days
Rules
-- Name must be provided to simplify copy / paste
-- Timezone should be UTC-# format per link in title
-- Daylight savings is just good to know, enter Yes if you observe it locally No if you don't
-- Start / Stop should be hour, half, quarter increments
-- Start / Stop should be in military time (to avoid confusion)
-- Start / Stop is local to your Timezone - do not convert to GMT
-- Days are valid as M, Tu, W, Th, F, Sa, Su
-- Ranges are acceptable for Days (e.g. M - Th)
-- Provide multiple entries for different Day ranges
Example
Wingspan, UTC-5, Yes, 8:00, 16:30, M - F
Wingspan, UTC-5, Yes, 7:00, 10:00, Sa
Closing Thoughts
So, post away. Smart excel people will post templates, I'm sure, on how to get this integrated. However, this data (if you compile it locally) will give you all you need to know who should be on whenever you're playing. Over time you should be able to coordinate builds to be effective (e.g. via the Repair Strategy; I love shameless self-promotion).
Posted Availability to Date
The ninnies have posted!!
Kickyourassacons, UTC-8, Yes, 10:00, 19:00, M - F
Chocolate Thunder, UTC-6, Yes, 8:00, 17:00, M - F
Evolution Prime, UTC-6, Yes, 7:00, 16:30, M - F
ashe5k, UTC-5, Yes, 4:00, 13:00, M - Sa
Firebird, UTC-5, yes, 22:30, 2:00, M - Su
Conjurous, UTC-0, Yes, 16.00, 1.00, M - F
Conjurous, UTC-0, yes, 10.00, 1.00, Sa - Su
neliz, UTC+1, Yes, 9:00, 0:00, M - F, dachterberg@livingston.nl
neliz, UTC+1, Yes, 17:00, 0:00, Su, dachterberg@livingston.nl
MagnusLabel, UTC+8, No, 16:30, 22:30, M - F