parent
fab538456c
commit
fbd1f3ca18
@ -1,6 +1,5 @@ |
||||
SUBDIRS = execmanual procedure
|
||||
INPUTS = index.xml constitution.xml official.xml machine_usage.xml \
|
||||
machine_usage_summary.xml website.xml constitution-change-20020920.xml \
|
||||
constitution-change-20040205.xml execmanual.xml procedure.xml
|
||||
constitution-change-20040205.xml
|
||||
|
||||
include ../default.mk |
||||
|
||||
@ -1,20 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd"> |
||||
|
||||
<cscpage title="Executive manual"> |
||||
<header /> |
||||
<section title="The CSC Executive Manual"> |
||||
<p>The CSC exec manual is intended to provide exec with a wealth of information on |
||||
useful topics provided by past executives. It should be kept up-to-date every term |
||||
by the current executives. One chapter is devoted to each executive position, with |
||||
descriptions of that position's duties and how to carry them out effectively.</p> |
||||
<p>At this point in time the exec manual is nowhere near complete. If you feel the |
||||
manual is a good contribution to the club, please bug the exec to put more work |
||||
into it.</p> |
||||
<p>The executive manual is written using DocBook and is available |
||||
<a href="execmanual/book.html">in HTML format</a>. The |
||||
<a href="execmanual/">DocBook source</a> is also on-line.</p> |
||||
</section> |
||||
<footer/> |
||||
</cscpage> |
||||
@ -1,36 +0,0 @@ |
||||
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 $@ $<
|
||||
@ -1,17 +0,0 @@ |
||||
<?xml version="1.0" standalone="no"?> |
||||
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" |
||||
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd" |
||||
[ |
||||
<!ENTITY prez SYSTEM "president.xml"> |
||||
<!ENTITY veep SYSTEM "vice-president.xml"> |
||||
<!ENTITY sysadmin SYSTEM "sysadmin.xml"> |
||||
<!ENTITY general SYSTEM "general.xml"> |
||||
]> |
||||
|
||||
<book><title>Computer Science Club Exec Manual</title> |
||||
&prez; |
||||
&veep; |
||||
&sysadmin; |
||||
&general; |
||||
</book> |
||||
|
||||
@ -1,93 +0,0 @@ |
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
<chapter> |
||||
<title>General Information</title> |
||||
|
||||
<para>Our mailbox is in the MathSoc office. It should be checked on a |
||||
regular basis. |
||||
</para> |
||||
|
||||
<sect1> |
||||
<title>Useful Contacts</title> |
||||
<para>There are several people that many exec will need contact information |
||||
for. Their contact info follows and <emphasis> should be updated when |
||||
these people change!</emphasis></para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>Donna Schell: We use her to book most rooms in the MC or elsewhere on |
||||
campus. She can generally book any lecture hall. If she can't do it, she |
||||
can tell you who can! She can be reached at |
||||
<email>dschell@uwaterloo.ca</email> or at extension 2207.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Vera Korody: ICR secretary. Should we wish to use the DC fishbowl for |
||||
anything we can contact her. She may require us to get the permission of a |
||||
ICR director to use it. Currently the friendly director is Vic DiCiccio at |
||||
<email>vicd@uwaterloo.ca</email>. I am including the text of an email |
||||
I sent and the response from Vic at the end of this segment. It is easiest |
||||
to talk to her directly at the ICR reception area beside the fishbowl in DC, |
||||
however she can also be e-mailed at <email>vkorody@uwaterloo.ca</email> or |
||||
called at ext. 2042.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>MathSoc: It is often smart to have executive in MathSoc who are |
||||
friendly with the CSC. To that end it is helpful to keep up with the |
||||
MathSoc exec and attend MathSoc events. Their office is directly across the |
||||
always closed door from ours. The president and VPF are particularily |
||||
helpful, in case we go a little over budget for any event they can approve |
||||
funding up to $100 extra by themselves. They can be reached at |
||||
<email>president@mathsoc.uwaterloo.ca</email> and |
||||
<email>VPF@mathsoc.uwaterloo.ca</email>. They also have a projector that |
||||
we can borrow from time to time.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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). |
||||
</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
|
||||
</sect1> |
||||
|
||||
<para>The E-mail I sent to Vic:</para> |
||||
<para>Hi,</para> |
||||
<para>The Computer Science Club is interested in booking DC 1301 (The Fishbowl) |
||||
for a student-prof mixer on the afternoon Monday, October 17. We were |
||||
told that it would require the permission of someone higher up in ICR since |
||||
we're a student club. We considered asking our faculty advisor, Prabhakar |
||||
Ragde, to book it on our behalf, but that would require him to be present |
||||
for the entire event and we don't want to impose on him to that extent |
||||
unless we have to. We are hoping to get your permission to book it since |
||||
our primary purpose is to remove alcohol from the picture, to get it away |
||||
from the "pints" mentallity and focus it more towards the frosh.</para> |
||||
|
||||
<para>Thanks for your consideration.</para> |
||||
|
||||
<para>Tim Loach</para> |
||||
<para>CSC President</para> |
||||
|
||||
<para> And his Response:</para> |
||||
<para>Hi Timothy,</para> |
||||
|
||||
<para>Sure, I would definitely approve this. Have you been turned down by |
||||
others? But you need to email Vera Korody to book the room, because it |
||||
might be booked, and you need to get her rules about moving chairs, |
||||
etc. I'll copy her on this email.</para> |
||||
|
||||
<para>BTW, does the CSC know that Mike Lazaridis is coming to Fed Hall on Oct |
||||
3 to explain why RIM is a cool place to work, and that there are still |
||||
challenges there to interest co-ops and grads. We could use your help |
||||
in getting the word out. You've probably seen the posters.</para> |
||||
|
||||
<para>Best,</para> |
||||
|
||||
<para>Vic</para> |
||||
|
||||
</chapter> |
||||
@ -1,64 +0,0 @@ |
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
<chapter> |
||||
<title>President</title> |
||||
|
||||
<para>This chapter 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.</para> |
||||
|
||||
<sect1> |
||||
<title>What to do</title> |
||||
|
||||
<para>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:</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para> to call and preside at all general, special, and executive |
||||
meetings of the Club;</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> to appoint all committees of the Club and the committee chair |
||||
of such committees, except the chair of the Programme Committee;</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> to audit, or to appoint a representative to audit, the |
||||
financial records of the club at the end of each academic term.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
<para>Wherever possible, the President should delegate tasks to others. |
||||
Not doing this can overburden the President.</para> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>Explanation</title> |
||||
|
||||
<para>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? </para> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>MathSoc</title> |
||||
|
||||
<para>The CSC is a MathSoc club as such you should know the <ulink |
||||
url="http://www.math.uwaterloo.ca/pinkbook.php">MathSoc club policies</ulink> |
||||
and know that the president is a non-voting member of MathSoc council, |
||||
like MathSoc directors.</para> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>Planning events</title> |
||||
|
||||
<para>Planning events is a useful thing to know, so go read the |
||||
Vice-President's section.</para> |
||||
</sect1> |
||||
|
||||
</chapter> |
||||
@ -1,135 +0,0 @@ |
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
<chapter> |
||||
<title>System Administrator</title> |
||||
|
||||
<para>The systems administrator position is probably the position |
||||
requiring the largest amount of "ad-hoc" knowledge. In |
||||
particular, there are many decisions related to how the CSC |
||||
computers are run which may not be so obvious from looking at the |
||||
systems themselves.</para> |
||||
|
||||
<para>For this reason, as sysadmin of the CSC it is of vital |
||||
importance that you not only read this document, but keep it up to |
||||
date as well.</para> |
||||
|
||||
<sect1> |
||||
<title>Your responsibilities</title> |
||||
|
||||
<para>According to the constitution, the following are the duties |
||||
of the sysadmin:</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>to operate any and all equipment in the possession of the Club;</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> to maintain and upgrade the software on equipment that is |
||||
operated by the Club;</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>to facilitate the use of equipment that is operated by the Club.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
<para>It has become quite regular for the CSC to get new equipment each |
||||
term. The sysadmin is responsible for ensuring this gear gets installed |
||||
and works as intended.</para> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>Useful contacts</title> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>You can try getting access to the machine room from MFCF/CSCF. |
||||
You probably want to talk to Dave Gawley, <email>dlgawley@cs.uwaterloo.ca</email>. |
||||
He's been really friendly to the CSC in the past and is a cool guy |
||||
in general.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>Changing Users</title> |
||||
<para>To alter users and groups please use the cpu command. cpu is setup |
||||
to use ldap to change any given user or group.</para> |
||||
<itemizedlist> |
||||
<listitem>To change a users group use cpu usermod -G current,groups,new,groups</listitem> |
||||
<listitem>man cpu-ldap</listitem> |
||||
<listitem>cpu groupadd cvs-ceo</listitem> |
||||
</itemizedlist> |
||||
</sect1> |
||||
<sect1> |
||||
<title>Expiring Users</title> |
||||
|
||||
<para>This procedure is for users that were expired at the end of spring |
||||
2003.</para> |
||||
|
||||
<orderedlist> |
||||
<listitem> |
||||
<para>login as root on peri (you probably can't do this, but might |
||||
have access to someone who can..)</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Unexpire the account in the ldap database</para> |
||||
|
||||
<para><prompt>peri# </prompt><userinput>echo username |
||||
|/root/dead-accounts/unexpire.pl</userinput> If this worked, it should |
||||
spit back the username.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Extract home directory onto peri</para> |
||||
|
||||
<para>extract home directory onto peri mount "Expired /u" on |
||||
sugar (or wherever) copy /$mntpoint/username.tar to somewhere |
||||
accessible to root@peri</para> |
||||
|
||||
<para>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. <prompt>peri# </prompt><userinput>tar xf /path/to/username.tar |
||||
-C /u</userinput></para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Restore mail onto peri </para> |
||||
|
||||
<para><prompt>peri$ </prompt><userinput>grep username |
||||
/root/dead-accounts/unreadable-accounts</userinput> 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.</para> |
||||
|
||||
<para>(I say 'sugar', but really any machine with a CD |
||||
drive...) <prompt>sugar$ </prompt><userinput>tar jxvf |
||||
/$mntpoint/mail_tar.bz2 username </userinput> (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.)</para> |
||||
|
||||
<para> 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</para> |
||||
|
||||
<para><prompt>peri#</prompt><userinput>cat /var/mail/username |
||||
>>username</userinput></para> |
||||
|
||||
<para><prompt>peri#</prompt><userinput>cat username |
||||
>/var/mail/username</userinput></para> |
||||
</listitem> |
||||
</orderedlist> |
||||
</sect1> |
||||
</chapter> |
||||
@ -1,208 +0,0 @@ |
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
<chapter> |
||||
<title>Vice President</title> |
||||
|
||||
<para>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.</para> |
||||
|
||||
<sect1> |
||||
<title>Planning events</title> |
||||
|
||||
<para>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.</para> |
||||
|
||||
<para>For starters, the most important thing to remember is this: |
||||
<emphasis>plan your events early!</emphasis>. I recommend about 2 to 3 |
||||
weeks in advance. This rough timeline should help:</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>2-3 weeks in advance: Get a title and abstract for the event |
||||
from the speaker as well as a date and time.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>2 Days in advance: E-mail <email>credmond@uwaterloo.ca</email> |
||||
to get the event into the Daily Bulletin. Include a short |
||||
(one-paragraph) description.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
<para>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.</para> |
||||
|
||||
<sect2> |
||||
<title>Getting ideas and speakers for events</title> |
||||
|
||||
<para>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:</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Out-of-town speakers. The <ulink |
||||
url="http://www.acm.org/chapters/stu/">ACM student chapter website</ulink> |
||||
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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Special events. In the past we've had an event called |
||||
"Pints with Profs" where we invited the CS faculty (<email>cs-faculty@cs.uwaterloo.ca</email>) |
||||
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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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. </para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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!</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
</sect2> |
||||
|
||||
<sect2> |
||||
<title>Announcing the event: Posters and Posts</title> |
||||
|
||||
<para>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).</para> |
||||
|
||||
<para>You'll also want to make printed posters. Simon Law made a |
||||
<filename>cscposter.cls</filename> 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:</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para>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).</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>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.</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para>Make use of the FEDS poster run. FEDS offers a (reasonably |
||||
cheap) poster run where they will distribute many posters around |
||||
campus. Check the <ulink |
||||
url="http://www.feds.uwaterloo.ca/services/marketing.html">FEDS |
||||
marketing website</ulink> 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.</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
<para>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 (<email>credmond@uwaterloo.ca</email>).</para> |
||||
|
||||
<para>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.</para> |
||||
|
||||
<para>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?"</para> |
||||
</sect2> |
||||
</sect1> |
||||
|
||||
</chapter> |
||||
@ -1,16 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd"> |
||||
|
||||
<cscpage title="Old CSC Procedures manual"> |
||||
<header /> |
||||
<section title="The old CSC Procedures Manual"> |
||||
<p>This is an outdated procedures manual written by previous |
||||
exec. Useful information from this should get moved into the <a |
||||
href="execmanual.html">new exec manual</a>.</p> |
||||
<p>The procedures manual is written using LaTeX and is available |
||||
<a href="procedure/procedure.pdf">in PDF format</a>. The |
||||
<a href="procedure/procedure.tex">LaTeX source</a> is also on-line.</p> |
||||
</section> |
||||
<footer/> |
||||
</cscpage> |
||||
@ -1,10 +0,0 @@ |
||||
*.html |
||||
*.fot |
||||
*.out |
||||
*.fo |
||||
*.pdf |
||||
*.log |
||||
*.aux |
||||
*.ps |
||||
*.dvi |
||||
*.toc |
||||
@ -1,36 +0,0 @@ |
||||
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: procedure.pdf |
||||
|
||||
%.pdf: %.tex |
||||
pdflatex $<
|
||||
|
||||
clean-recurse: clean |
||||
|
||||
clean: |
||||
rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.toc
|
||||
|
||||
#book.html: $(XMLS)
|
||||
|
||||
#%.html: %.xml
|
||||
# $(XSLTPROC) $(STYLESHEET) $< > $@
|
||||
|
||||
#%.fo: %.xml
|
||||
# $(XSLTPROC) $(FOSTYLESHEET) $< > $@
|
||||
|
||||
#%.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 $@ $<
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Loading…
Reference in new issue