Exec Manual

President

This section covers various useful notes for the CSC president, ranging from who to call for room bookings to when the term should end. I'll rant some more later.

What to do

The President is the person responsible. As ungrammatical as that may seem, it is exactly accurate. He or she is responsible to make certain that everything the CSC is involved in gets proper attention. Specifically, the President's duties are:

• to call and preside at all general, special, and executive meetings of the Club;

• to appoint all committees of the Club and the committee chair of such committees, except the chair of the Programme Committee;

• to audit, or to appoint a representative to audit, the financial records of the club at the end of each academic term.

Wherever possible, the President should delegate tasks to others. Not doing this can overburden the President.

Explanation

As listed above the president is responsible for appointing committee chair's and other positions. So, it is basically up to the president to decide whether or not there is an explicit office staff. How do people become office staff? Must the office close every day? What do the members expect to get out of the club in this term?

MathSoc

The CSC is a MathSoc club as such you should know the MathSoc club policies and know that the president is a non-voting member of MathSoc council, like MathSoc directors.

Planning events

Planning events is a useful thing to know, so go read the Vice-President's section.

Vice President

This section covers various useful notes for the CSC vice president, ranging from who to call for room bookings to how to promote your events.

Planning events

So, you're the CSC Vice President and you want to (hopefully) have the CSC host some really cool events this term. This chapter should help you get started with that. For starters, the most important thing to remember is this: plan your events early!. I recommend about 2 to 3 weeks in advance. This rough timeline should help:

• 2-3 weeks in advance: Get a title and abstract for the event from the speaker as well as a date and time.

• 2 weeks in advance: Book the room and any necessary equipment (projectors etc). Make posters for the event. Make initial announcements on Usenet and possibly by e-mail.

• 2 Days in advance: E-mail Chris Redmond (credmond@uwaterloo.ca) to get the event into the Daily Bulletin. Include a short (one-paragraph) description.

• Day of the event: Try to be at the event, or find someone who will be to make sure things go smoothly. Remember to get the projector if necessary. If there are people in the room you booked, ask them to leave politely. Mention that you have the room booked. Get refreshments to the room as necessary. Introduce the speaker.

• After the event: Thank the speaker in front of the audience and applaud. Offer to take the speaker out for dinner. Clean up the room and return any loaned equipment. Write him or her a cheque for any expenses if necessary. For out-of-town speakers a small gift might be nice.

The rest of this section will outline various tips that should be useful when running events and suggest some events that you might want to run.

Getting ideas and speakers for events

Obviously you will have to start your planning by coming up with an event. Here are some types of events you might want to hold:

• Talks held by CSC members. Ask around, there are probably a few members who have interesting things to give talks on. In the past CSC members have given talks about programming languages they like, Operating Systems, research projects, etc.

• Talks held by Faculty: Simply ask your CS profs, or get other exec to ask their profs or interesting faculty. Approaching faculty in person might get you better results than e-mailing, but be sure to follow up with an e-mail so that you have something written to remind them.

• Out-of-town speakers. The ACM student chapter website has a section called "Lectureship series" where you can find information on getting an ACM Distinguished Lecturer. You can also simply approach interesting people (in Academia, Industry or the Free Software scene) by e-mail and ask them if they'd like to come and give a talk (or a few talks). Don't be afraid to ask high-profile people, the worst you can get is a "no." Be sure to have the treasurer budget money to pay for the guest speaker's expenses. If you can, try to pay for travel expenses (unless the speaker offers), but at the very least arrange for meals and accommodation as well as transport from the airport or bus/train station if necessary.

• Special events. In the past we've had an event called "Pints with Profs" where we invited the CS faculty (cs-faculty@cs.uwaterloo.ca) and any interested CS students to come out to a pub. The Bomber is a convenient location but we've found their catering to be expensive. Weaver's Arms (in WCRI) might be a good alternative. Be sure to budget this with Mathsoc, so you can pay for free food. Try to get both meat and vegetarian alternatives (e.g. Wings and Veggie Platters). Make sure you publicize this event very well, and don't hesitate to ask the profs to announce it in class (giving them overheads might be a good idea). This is definitely an event you should try to hold. If you can think of any other special events, go right ahead, be creative! Be sure to add them here.

• Tutorials. Usually we hold a few UNIX tutorials at the beginning of the term. These are quite popular and you can get Faculty (especially the first and second-year CS profs) to announce them in class. Be sure to book a lab. If there are more than one or two other people in the lab, politely ask them to leave - in our experience, asking such groups to be quiet doesn't usually work very well. Aside from UNIX you could have tutorials for LaTeX, some programming language, some programming problem (e.g. "Writing a raytracer") or anything you think would be useful for people to learn.

• Contests. Programming contests can be a lot of fun and will certainly raise interest in the club. Try to get nice prizes so that you can attract a large group of contestants. Be sure to have the rules and the environment set up early on. Game solving contests are a good idea (this can range from writing programs to play rock-paper-scissors to having programs compete at playing chess), demo programming contests can also be fun or you might go for something more useful. It's up to you - be creative!

• Anything else you can think of. Be imaginative and ask for suggestions. The ACM website also has some good suggestions for events. Don't limit yourself to computer-related events - a volleyball match against the Pure Math Club might be fun.

Announcing the event: Posters and Posts

Once you have the abstract and the room booked you should get the word out. For starters you should send an announcement to the uw.csc newsgroup and possibly to the members by e-mail (try to reserve the latter for special events, although an update with upcoming events every now and then might be a good idea).

You'll also want to make printed posters. Simon Law made a cscposter.cls file for LaTeX which can be used to generate nice-looking posters in letter format. Try to not have too much text on the posters so that they grab more attention. Getting posters out earlier rather than later is definitely beneficial. To actually distribute posters you should use several methods:

• Put up the posters on the CSC boards. There are 3 boards: a small one right by the door of MC3036, a large one in the 3rd floor hallway of the MC and another large one on the second floor of the MC (directly below the third floor hallway).

• Give 6 posters to Mathsoc. Just drop by 6 posters in the Mathsoc office and they'll put them up around the MC and DC.

• Make use of the FEDS poster run. FEDS offers a (reasonably cheap) poster run where they will distribute many posters around campus. Check the FEDS marketing website for pricing and information on how to use it. While we aren't a FEDS club, we are part of MathSoc, so try to get the "student society" price. Also, make sure you budget for this from Mathsoc, you can probably get funds from them to use this.

There are other ways to get people to know about the event. If the event is relevant to classes, try to convince profs to announce it in class (giving them an overhead with the details is a good idea). Also, have the event announced in the Daily Bulletin (a daily update on the UW website about what's happening on campus). To do so, e-mail Chris Redmond (credmond@uwaterloo.ca).

Word of mouth is another important channel. Tell others in the CSC (both executives and members) to tell their friends about events. Tell your own friends and classmates about events that they might find interesting. Word of mouth is often how events get most of their publicity.

Lastly, you'll want to add the event to the website. Contact the CSC webmaster (or if there is none, the sysadmin) to have him or her do that for you, or find out how to do it yourself. This way others can check for events on the website, and you can also conveniently point people there if they ask, "What events is the CSC offering this term?"

System Administrator

This procedure is for users that were expired at the end of spring 2003.

• Login as root on peri (you probably can't do this, but might have access to someone who can..)

• Unexpire the account in the ldap database:

peri# echo username |/root/dead-accounts/unexpire.pl

• If this worked, it should spit back the username.

• Extract home directory onto peri

• Extract home directory onto peri mount "Expired /u" on sugar (or wherever) copy /$mntpoint/username.tar to somewhere accessible to root@peri

     Note: the home directories are not compressed on the CD, remember this when 'cp' is telling you 'username.tgz: no such file or directory'. tar (below) doesn't need 'z' either. peri# tar xf /path/to/username.tar -C /u
  4.

     Restore mail onto peri

     peri$ grep username /root/dead-accounts/unreadable-accounts if the username is there, the mbox is on "Expired mail 2" otherwise, the mbox is on "Expired mail" mount appropriate CD cd to a temporary directory (*not* /var/mail) extract mbox from archive -- on the "Expired mail", this will take a while -- just hit ^C after you see the username printed and you're happy tar has moved on to other files.

     (I say 'sugar', but really any machine with a CD drive...) sugar$ tar jxvf /$mntpoint/mail_tar.bz2 username (hmm.. I don't remember what the tarball is called on Expired2, maybe the same thing, maybe different, but I'm pretty sure this is the filename for Expired1. Besides, there's only one file on the CD, so just tab-complete the damn thing :) (probably scp username root@peri: or something here) restore mail, appending any mail received since backup was made, and preserving permissions on the file. (Note: this doesn't take into account locks -- i.e., stuff might get screwed if the account receives mail while one of the below cats is running. A message received between the cats simply gets lost.)

     The following commands should also work from another machine if the account was on "Expired mail" (i.e., was not in ``unreadable-accounts). But doing it on peri will always

     peri#cat /var/mail/username >>username

     peri#cat username >/var/mail/username