From e17f2dd717fd27057b1b2c8336dfd89572713ee8 Mon Sep 17 00:00:00 2001 From: Stefanus Du Toit Date: Thu, 15 May 2003 13:06:11 +0000 Subject: [PATCH] Added execmanual --- docs/Makefile | 4 +- docs/execmanual/Makefile | 36 +++++ docs/execmanual/book.xml | 11 ++ docs/execmanual/vice-president.xml | 236 +++++++++++++++++++++++++++++ 4 files changed, 285 insertions(+), 2 deletions(-) create mode 100755 docs/execmanual/Makefile create mode 100755 docs/execmanual/book.xml create mode 100755 docs/execmanual/vice-president.xml diff --git a/docs/Makefile b/docs/Makefile index 6526c20..4320b46 100755 --- a/docs/Makefile +++ b/docs/Makefile @@ -1,6 +1,6 @@ -SUBDIRS = editing-example1 editing-example2 editing-example3 +SUBDIRS = editing-example1 editing-example2 editing-example3 execmanual INPUTS = index.xml constitution.xml official.xml machine_usage.xml \ machine_usage_summary.xml website.xml editing-howto.xml \ constitution-change-20020920.xml -include ../default.mk \ No newline at end of file +include ../default.mk diff --git a/docs/execmanual/Makefile b/docs/execmanual/Makefile new file mode 100755 index 0000000..0b6e0c7 --- /dev/null +++ b/docs/execmanual/Makefile @@ -0,0 +1,36 @@ +STYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl +FOSTYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/fo/docbook.xsl +XSLTPROC = xsltproc +XMLS = $(wildcard *.xml) +HTMLS = $(XMLS:.xml=.html) + +#all: book.html book.tex book.pdf +all: book.html + +clean-recurse: clean + +clean: + rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.tex + +book.html: $(XMLS) + +%.html: %.xml + $(XSLTPROC) $(STYLESHEET) $< > $@ + +%.fo: %.xml + $(XSLTPROC) $(FOSTYLESHEET) $< > $@ + +#%.pdf: %.fo +# pdfxmltex $< + +%.tex: %.xml + openjade -t tex -d /usr/share/sgml/docbook/stylesheet/dsssl/modular/print/docbook.dsl $< + +%.dvi: %.tex + jadetex $< + +%.pdf: %.tex + pdfjadetex $< + +%.ps: %.dvi + dvips -o $@ $< diff --git a/docs/execmanual/book.xml b/docs/execmanual/book.xml new file mode 100755 index 0000000..2ee7b26 --- /dev/null +++ b/docs/execmanual/book.xml @@ -0,0 +1,11 @@ + + +]> + +Computer Science Club Exec Manual +&veep; + + diff --git a/docs/execmanual/vice-president.xml b/docs/execmanual/vice-president.xml new file mode 100755 index 0000000..98da0e2 --- /dev/null +++ b/docs/execmanual/vice-president.xml @@ -0,0 +1,236 @@ + + + Vice President + + This chapter 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 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 chapter 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 accomodation 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 publicise 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 (especiall 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?" + + + + + Useful contacts + + + + For bookings call Donna Schell at extension 2207 (she can book + rooms in any building) or e-mail her at dschell@uwaterloo.ca. + You might also want to contact ICR about booking the ICR conference + rooms, which include AV facilities. See the ICR homepage. + + + + AV stuff should be handled through AV services at extension + 3033. Keys for AV stuff can be obtained at E2 1309. Note that they + will charge you $80 if you intend to use a projector (and that's + non-refundable - apparently bulbs are expensive and need to be + replaced often). + + + + You can try getting a projector from MFCF/CSCF. You probably + want to talk to Dave Gawley, dlgawley@cs.uwaterloo.ca. + He's been really friendly to the CSC in the past and is a cool guy + in general. + + + + \ No newline at end of file