There are two reasons I use Eastern Daylight/Standard time: * That is where the QA and release engineering teams for Fedora are primarily based. Working off a schedule that is intuitive for them reduces the chances of miscommunication and mistakes. * The same intuitiveness is currently spread throughout the Fedora development community. Should this change, or we want to lead a charge for UTC on all things, feel free to challenge this concept. Meanwhile, if we ever set a deadline, e.g. 24 October, this is what it means: 24 October 23:59 Eastern Time Yes, that means right before Midnight. This way we provide the most time for completing deadlines without having confusion about Midnight meaning the start of the end of which day. Alternately, we can set deadlines as COB (close of business), for an additional cushion of time. That would be: 24 October 17:00 Easter Time Does this make sense? When doing the scheduling for translation, I tried to add in a calendar day as a cushion against any problems caused by a deadline being late afternoon in APAC. http://fedoraproject.org/wiki/DocsProject/Schedule - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
