Migrated exec manual to wiki and moved old procedure manual into ~www/misc.

David Bartley 16 years ago
parent fab538456c
commit fbd1f3ca18
  1. 3
  2. 1
  3. 20
  4. 36
  5. 17
  6. 93
  7. 64
  8. 135
  9. 208
  10. 3
  11. 16
  12. 10
  13. 36
  14. 1377
  15. 1379

@ -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
include ../default.mk

@ -4,5 +4,4 @@
<directory title="Documents">
<diritem title="Official documents" href="official.html" />
<diritem title="Executive manual" href="execmanual.html" />

@ -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>

@ -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
rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.tex
book.html: $(XMLS)
%.html: %.xml
%.fo: %.xml
#%.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"
<!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>

@ -1,93 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<title>General Information</title>
<para>Our mailbox is in the MathSoc office. It should be checked on a
regular basis.
<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>
<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>
<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>
<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>
<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>The E-mail I sent to Vic:</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>

@ -1,64 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<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&#39;ll rant some more later.</para>
<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&#39;s duties are:</para>
<para> to call and preside at all general, special, and executive
meetings of the Club;</para>
<para> to appoint all committees of the Club and the committee chair
of such committees, except the chair of the Programme Committee;</para>
<para> to audit, or to appoint a representative to audit, the
financial records of the club at the end of each academic term.</para>
<para>Wherever possible, the President should delegate tasks to others.
Not doing this can overburden the President.</para>
<para>As listed above the president is responsible for appointing
committee chair&#39;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>
<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>
<title>Planning events</title>
<para>Planning events is a useful thing to know, so go read the
Vice-President&#39;s section.</para>

@ -1,135 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<title>System Administrator</title>
<para>The systems administrator position is probably the position
requiring the largest amount of &quot;ad-hoc&quot; 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>
<title>Your responsibilities</title>
<para>According to the constitution, the following are the duties
of the sysadmin:</para>
<para>to operate any and all equipment in the possession of the Club;</para>
<para> to maintain and upgrade the software on equipment that is
operated by the Club;</para>
<para>to facilitate the use of equipment that is operated by the Club.</para>
<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>
<title>Useful contacts</title>
<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&#39;s been really friendly to the CSC in the past and is a cool guy
in general.</para>
<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>
<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>
<title>Expiring Users</title>
<para>This procedure is for users that were expired at the end of spring
<para>login as root on peri (you probably can&#39;t do this, but might
have access to someone who can..)</para>
<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>
<para>Extract home directory onto peri</para>
<para>extract home directory onto peri mount &#34;Expired /u&#34; 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 &#39;cp&#39; is telling you &#39;username.tgz: no
such file or directory&#39;. tar (below) doesn&#39;t need &#39;z&#39;
either. <prompt>peri# </prompt><userinput>tar xf /path/to/username.tar
-C /u</userinput></para>
<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 &#34;Expired mail 2&#34; otherwise, the mbox is
on &#34;Expired mail&#34; mount appropriate CD cd to a temporary
directory (*not* /var/mail) extract mbox from archive -- on the
&#34;Expired mail&#34;, this will take a while -- just hit ^C after
you see the username printed and you&#39;re happy tar has moved on to
other files.</para>
<para>(I say &#39;sugar&#39;, but really any machine with a CD
drive...) <prompt>sugar$ </prompt><userinput>tar jxvf
/$mntpoint/mail_tar.bz2 username </userinput> (hmm.. I don&#39;t
remember what the tarball is called on Expired2, maybe the same thing,
maybe different, but I&#39;m pretty sure this is the filename for
Expired1. Besides, there&#39;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&#39;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 &#34;Expired mail&#34; (i.e., was not in
``unreadable-accounts&#39;&#39;). But doing it on peri will always</para>
<para><prompt>peri#</prompt><userinput>cat /var/mail/username
<para><prompt>peri#</prompt><userinput>cat username

@ -1,208 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<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>
<title>Planning events</title>
<para>So, you&#39;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>
<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>
<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>
<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>
<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>
<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
<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
<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>
<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>
<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>
<para>Out-of-town speakers. The <ulink
url="http://www.acm.org/chapters/stu/">ACM student chapter website</ulink>
has a section called &#34;Lectureship series&#34; 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&#39;d like to
come and give a talk (or a few talks). Don&#39;t be afraid to ask
high-profile people, the worst you can get is a &#34;no.&#34; Be
sure to have the treasurer budget money to pay for the guest
speaker&#39;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>
<para>Special events. In the past we&#39;ve had an event called
&#34;Pints with Profs&#34; 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&#39;ve found their catering to be
expensive. Weaver&#39;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&#39;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>
<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&#39;t usually work
very well. Aside from UNIX you could have tutorials for LaTeX, some
programming language, some programming problem (e.g. &#34;Writing a
raytracer&#34;) or anything you think would be useful for people to
learn. </para>
<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&#39;s up to you - be creative!</para>
<para>Anything else you can think of. Be imaginative and ask for
suggestions. The ACM website also has some good suggestions for
events. Don&#39;t limit yourself to computer-related events - a
volleyball match against the Pure Math Club might be fun.</para>
<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&#39;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>
<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>
<para>Give 6 posters to Mathsoc. Just drop by 6 posters in the
Mathsoc office and they&#39;ll put them up around the MC and DC.</para>
<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
marketing website</ulink> for pricing and information on how to use
it. While we aren&#39;t a FEDS club, we are part of MathSoc, so try
to get the &#34;student society&#34; price. Also, make sure you
budget for this from Mathsoc, you can probably get funds from them
to use this.</para>
<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&#39;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
<para>Lastly, you&#39;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, &#34;What events is the CSC offering this

@ -11,9 +11,6 @@
<li><a href="official.html">Official documents</a></li>
<li><a href="execmanual.html">Manual for new executives</a></li>
<li><a href="procedure.html">Old CSC Procedures manual</a>, to
be integrated into the new exec manual</li>
<li><a href="mathsoc.club.pdf">Mathsoc Clubs manual</a></li>

@ -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>

@ -1,10 +0,0 @@

@ -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
rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.toc
#book.html: $(XMLS)
#%.html: %.xml
#%.fo: %.xml
#%.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