Spring 1999 CS190 Conduct and Cummunications Document
Author: Project Lead, Christine Waggoner


Statement of Purpose
This document is intended to serve as a guidelines on how to communicate
and behave throughout the course of the Spring 1999 CS190 group programming
project.  It is not intended to be read as a set of stringent codes, but as
a simple clarifying statement on how the project lead expects group members
to behave and communicate.  Hopefully, most of this will all seem like
common sense.

Guidelines
1. If you have a gripe about anything related to do with project, even the
project lead herself,  feel free to contact the project lead at any time.  

2. When possible, communicate face to face.  Email and newsgroup posts are
extremely useful, but can often be confusing and be misinterpreted.  Avoid
flame wars.

3.  Use the newsgroup and email as a forum to share ideas and to educate
the rest of the group.  

4. When you accomplish something or complete a task, e.g., a revision,
inform the rest of the group by sending out a short email.

5. Ask questions.  If you are even slightly confused, always ask for more
information and try to clarify the issue at hand.  

6. At group meetings, if you are assigned a task, you may wish to write
down what you have been assigned.  Complete your tasks well and on time.  

7. Attack the idea, not the person.  In group meetings, avoid insulting
each other during disputes.
  
8. Attend all the meetings and be on time.  

9. Keep track of the schedule for the rest of the semester and inform
other group members of necessary absences in advance.  

10. Mail ideas for additions to this document to the project lead.