User:Chris Tyler/draft/CDOT Researchers

This is a draft only!
It is still under construction and content may change. Do not rely on this information.

This is a draft document outlining some general policies and procedures for CDOT Researchers (employees).

Work Environment

Researcher Hours

• Flex hours
  • To foster collaboration, all researchers are expected to be present from 10 am through 3 pm four days per week, including the weekly meeting day
  • Otherwise, researchers schedule their own hours

System Backup

• Researchers are responsible for backing up their own work
• Data files should be replicated from local workstations to the NAS server and/or checked in to the appropriate repository daily
• Files should be burnt to optical media at the end of each weekday

System Administration

• Each researcher is the primary administrator of the system in their cubicle
• Each researcher has access to the other development systems
• Don't blow up other people's work
• Use the Best Practices for the operating system used on your machine (e.g., use OS-provided packages and directory locations wherever possible)

Communication

• Blogging
  • Prepare a short blog post about your work each day. Tag all of these posts for distribution to the internal planet.
  • Post out to the CDOT public planet and to your community's planet a minimum of twice a week
• Wiki
  • Update your project timeline daily
  • Document APIs changes and other development results within the week in which they are made
• IRC
  • Researchers should be on IRC while they are working
  • Join freenode:#seneca, moznet:#seneca (general Seneca open source discussions), freenode:#seneca-cdot (CDOT employee discussions), and the channels most suited to your project(s)

Meetings

• Weekly Meeting
  • Held in the Conference Room (T1012)
  • Each researcher is expected to give a brief status update