DCC-L is a listserv designed to help Brown's DCCs share information to assist them in their job as DCC. There is a wide range of technical expertise among the DCCs. While those who are most technical often have gaps in a particular area, those who might consider themselves to have less expertise often surprise us with answers to a question about a problem with which they have had recent experience. So please try to remember that we are all learning. Ask questions whether you feel that everyone in the entire world but you knows the answer, or you assume no one knows. Just please follow the guidelines below in all your posts, they have been developed from all the suggestions contributed by those DCCs who said they were interested in having a list.

If after reading this you are unsure of whether something is appropriate for the list email DCC Liaison, I would be happy to advise you. If you feel these list guidelines should be changed send email to DCC Liaison. All changes will be made after approval by the steering committee.

All DCCs who offered suggestions agreed that the list's primary focus is technical support for one another:

  1. Troubleshooting Q&A
  2. Sharing tips for problem-solving strategies
  3. Warnings about bugs or problems with programs that you have discovered, including workarounds if you've found some.
  4. Questions about or tips for getting a particular feature of a program to work (e.g. Does anyone know how to get Eudora to correctly render Japanese e-mail? Is there a way to transfer a VHS video to QuickTime?)
  5. Queries about potential purchases (e.g. Has anyone had any experience with color printers, Gateway computers, etc?)
With all these technical support type posts include as much information as possible about your system, error messages and what you may have already tried. Use descriptive Subject lines so that anyone searching for a post later can find it. Replies to the post should use the reply key so the subject heading remains consistent and people can follow the thread, not needing to repeat suggestions.

There was mixed support for using the list to ask about non-technical aspects of the DCC position. There were however enough DCCs in favor that it was decided the list should support such posts provided you use accurate subject lines (see below), so those who do not wish to spend time with these can just delete them. Any such posts should be directly related to solving issues with the DCC position here at Brown. Commiserating, generalized complaining, naming of individuals supervisors should be discussed only by direct email to an individual - not by posting to the list.

Examples of non-technical DCC related posts:
  • Suggestions/problems re: managing the DCC workload - Subject line might be How to manage DCC workload rather than something like overwhelmed.
  • Getting the DCC portion of one's job accurately reflected in one's PCD - Subject line: question about getting DCC added to PCD
  • Ideas for DCC meetings or training - Subject line: Idea for DCC meeting
  • Questions about computing plans and policies (e.g. what version of Windows, Word etc. will Brown be using next year?) This should be questions and factual information such as what is going to be supported and technical problems or workarounds not general griping (e.g. I really wish we were using program X instead of Y
The following should NOT be on the list:
  • No advertisements, jokes, cartoons or cute items, commentary on events etc., gripes
  • No personal messages and chatting, no matter how brief (e.g. 1. Thanks for that last message Bill. 2. No problem. 3. Do we really have to include thank-you messages on the list? 4. I agree we shouldn't have thank-you messages on the list. 5. Thank you for agreeing :) 6. No problem...)
  • Questions about technology not related to work at Brown (e.g. How can I make "phone calls" over the Internet?)
  • No attachments: Include URLs or have people email you directly for any handouts or attachments. If it is something there is great demand for we can set it up for download off the DCC web page.

After reading the memo, if you'd like to join the DCC list send an email to listserv@listserv.brown.edu.
Leave the subject field blank. In the body of the message just type:

SUBSCRIBE dcc-l

Set your signature to none (if you are using Eudora that's under the JH button next to bin hex) or it will send you an error message.

If this sounds too complicated just send me an email and ask me to sign you up.