From 4524fe1744e2ded6e5d544f6e572160f301eb6b8 Mon Sep 17 00:00:00 2001 From: David Bartley Date: Tue, 14 Aug 2007 02:34:30 -0400 Subject: [PATCH 01/51] Downsized the favicon. --- favicon.ico | Bin 26622 -> 2462 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/favicon.ico b/favicon.ico index 52872fd6a2b960ed336899959113bf69d8c4d514..7d1e208fd7424da37003298d309464f381f04833 100644 GIT binary patch literal 2462 zcmeH{JxCl;6h@y>F#ZI)xC+982sQy@XSy_^7K)XMV4;=v3eiBcQ$iqZN^2WIu@f7y z5fQYq5Ecu65VWxnU0u(S8CWDUf?zk_a`w%=_q%sz-<#bKDtP5`f%kk^tO?ID!+{ft6@AHg8>@e)Sc8 zgWe>MpFaaaND-m9v~_-yW=j_n^k$3i=>^7Lz=^k;l~@ zdzG`CX`lD&d5wc=2lH#t0xHe(jk;cY>{ZTkrhV@3GTgutbi+J6!Y&L#n&&?9&a>L< z3}-phKKGyv%opGs{A|DPCJe# z2MHXliIBX(I57(vrZ``Fdo`4*t7@uxECKi0clxi+J-1GGSJ%%vx2JzMZ#wwf#x zxwoBj@5yz_eJ$s_nJHijm;$DNDPRhi0;Yf|U<#N5rhqA63YY?>fGJ=Km;$DNDPRhi z0;Yf|U<#N5|1kxws6L1CWBIr8U*+d=f3fA5^IWGK<$G(v_AzR_Td2GuY=5|9Tern92CI1jhF65LluKy?xu`S0XykSls>BO^<^Ju9+hXqfZ zSbVT4Yr(#$z(2@iynLfmwhb?RomiX0bC=Vu6ib}gvjlIhueA#-{Tup-DJ$ire;eK- z+Md)q+w*RNB_44@E@I@Y1txowFJ&aYHWnH^+KIye(M1 zDIqUo6UKKrOYt5G9LD9H8v4#|a@Amo8*3|wm9tiCtZ&2EIA^fdVl7zuhhy_HUlPWgmsCV$YO%x*If+$ba}}z^-ilzElPR&e3dMMt&k4^Tlmt|n zS}gHHPGXf<3-)~xjLjQs6ByT&SS^_}tU(gu1r0f3z_rHa2fb&Mj@{5VrOk zibj09LhWyrh^I0wytUYQB;VHWer+EPnPS)nTqv*@mcCty)nbVs-fv=+*bug64AJw^ zcMtQSUE9^zrRS~5IW>mp;|^_8*ee2^$wM9P4F%gc&)AVMWQb*~nX?w&8Z7k*^Q7Ly z%2^J(%^XU|6?>PM>tN0!XDz(jU~_XQsXR-trE_>O9_G-V%foxiT;Eu8hcVvLoJ;5M zVjSCGb92bC`2D#%+6ndJn7Lo(fK%4Oo5NE7mo@L5Tf^Wv9x|{)>#mP=E%h$9@}|~o zV)NbH*Ili<+)(UYtiRD7@=duWkJ+wxWADVS*8Tc=v9=l;TlKjx_eo!9E6Ks)rMBXJ5dn$Z_8tRv2&CK(_^W_Tuz;0^SXTuawo?UqukJQ*vG5g z5_c$%UGmoE3oe!Oke<9#Lv2fKF0_%vP1!DZYx4z%2DzMv>O@V&|W#{IQ%qVvW`Ek|+7rZG%f62+W&q3p*pu5 Date: Sat, 18 Aug 2007 01:58:27 -0400 Subject: [PATCH 02/51] Move mailman back to http://csclub.uwaterloo.ca/mailman/ --- clubs/directory.xml | 2 +- clubs/index.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/clubs/directory.xml b/clubs/directory.xml index d5bfe62..3c0931b 100644 --- a/clubs/directory.xml +++ b/clubs/directory.xml @@ -4,5 +4,5 @@ + href="/mailman/" /> diff --git a/clubs/index.xml b/clubs/index.xml index 9edf58e..c269f4d 100644 --- a/clubs/index.xml +++ b/clubs/index.xml @@ -63,7 +63,7 @@

We also host a number of mailing lists + href="/mailman/">mailing lists for various organisations, on-campus or in the community. We provide archives of mailing list postings, as well as a web-based interface for administring lists.

From 24360172b2ede219d82cf542b807b859dcb45372 Mon Sep 17 00:00:00 2001 From: Michael Spang Date: Sat, 18 Aug 2007 02:00:25 -0400 Subject: [PATCH 03/51] Also fix mailman link in the menu (whoops) --- menu.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/menu.xml b/menu.xml index 140623b..a3c6263 100644 --- a/menu.xml +++ b/menu.xml @@ -13,7 +13,7 @@ - + From e9b2063d8da8e8b195e49e342d2614c9e6624a2c Mon Sep 17 00:00:00 2001 From: David Bartley Date: Sat, 18 Aug 2007 02:03:03 -0400 Subject: [PATCH 04/51] Make mailman really absolute. --- menu.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/menu.xml b/menu.xml index a3c6263..36666e5 100644 --- a/menu.xml +++ b/menu.xml @@ -13,7 +13,7 @@ - + From 472ee48340656a4dc9a5247ef0e2accca3a23eea Mon Sep 17 00:00:00 2001 From: David Bartley Date: Mon, 20 Aug 2007 14:26:20 -0400 Subject: [PATCH 05/51] Remove machine list as the wiki contains more up-to-date information. --- office/Makefile | 2 +- office/computers.xml | 105 ------------------------------------------- office/directory.xml | 1 - office/index.xml | 5 +-- 4 files changed, 3 insertions(+), 110 deletions(-) delete mode 100644 office/computers.xml diff --git a/office/Makefile b/office/Makefile index 2eeca8b..3b3c535 100644 --- a/office/Makefile +++ b/office/Makefile @@ -1,5 +1,5 @@ SUBDIRS = books -INPUTS = index.xml staff.xml books.xml operating-systems.xml webcam.xml webcam-streaming.xml computers.xml +INPUTS = index.xml staff.xml books.xml operating-systems.xml webcam.xml webcam-streaming.xml include ../default.mk diff --git a/office/computers.xml b/office/computers.xml deleted file mode 100644 index 9c3d26c..0000000 --- a/office/computers.xml +++ /dev/null @@ -1,105 +0,0 @@ - - - - -
- -
- -

The Computer Science Club has access to a variety of different architectures to give members a chance to test their programs in different environments.

- -

Here is a list of the computers we have available:

- -
-
caffeine (csclub1.cs)
-
-

This is a Debian stable machine that runs the Computer Science Club, i.e it hosts all the important servers. It is also the machine where your home directory lives.

-

caffeine has 2000 MB of RAM and a AMD Athlon 64 X2 (dual core) 4200+ processor.

-
-
taurine
-
-

This is a Debian stable machine.

-

taurine has 8000 MB of RAM and two Dual-Core AMD Opteron(tm) Processor 2218

-
-
artifical-flavours (csclub2.cs)
-
-

This is a Debian unstable machine that runs a talk mirror.

-

artifical-flavours has a Intel(R) Celeron(R) CPU 3.20GHz

-
-
natural-flavours (csclub4.cs)
-
-

This is a Debian unstable machine that runs a talk mirror.

-

natural-flavours has 2 Intel(R) Core(TM)2 CPUs 6300 @ 1.86GHz

-
-
citric-acid (csclub3.cs)
-
-

This is a Debian unstable machine that runs a talk mirror.

-

citric-acid is a AlphaServer 4100

-
-
perpugilliam (peri)
-
-

This is a Debian stable machine that was formerly ran the Computer Science Club. It is now on backup duty.

-

peri has 512 MB of RAM and dual P3 450 MHz processors.

-
-
glucose-fructose (sugar)
-
-

This is a Debian unstable machine, which means you will find bleeding-edge software available here. This may, or may not, work with the other software installed on your CSC account.

-

It has 512 MB of RAM and dual P3 500 MHz processors.

-
-
caramel-colour
-
-

This is a Debian unstable machine, which means you will find bleeding-edge software available here. This may, or may not, work with the other software installed on your CSC account.

-

It as 512 MB of RAM and a single P3 1GHz processor. Its a good place to do random high-load work

-
- -
phosphoric-acid (h3po4)
-
-

This is a Debian unstable machine, which means you will find bleeding-edge software available here. This may, or may not, work with the other software installed on your CSC account.

-

It as 512 MB of RAM and a single P3 1GHz processor. It also suffers from an extremely dodgy power supply.

-
- - -
carbonated-water (h2o)
-
-

Has been retired

-

This is a Debian stable machine that runs as a backup for perpugilliam. This means that it runs the secondary LDAP server and soon to be kerberos, for authentication; and the backup mail exchange. Sadly, we are unable to provide backup NFS.

-

It has 256 MB of RAM and an AMD-K6 200 MHz processor.

-
-
powerpc0 (aspartame)
-
-

Has been retired

-

powerpc0 is a UW-DIG iMac. It was graciously loaned to us -by CSCF. It currently runs Debian stable, and is a great platform for -porting your software to PowerPC.

-

It has 64 MB of RAM and a 233 MHz PowerPC processor.

-
-
sparc0
-
-

Has been retired

-

sparc0 is a UW-DIG machine. It was graciously loaned to us by Peter Buhr. It currently runs Debian stable, and is a great platform for porting your software to UltraSparc.

-

It has 128 MB of RAM and a TI UltraSparc IIi processor.

-
-
frobisher
-
-

Is currently out of commision (it smells like burning when plugged in)

-

An experimental Corel Netwinder 275. Undead. It is rumoured to eat frosh.

-

It has 64 MB of RAM and a flakey 133 MHz SuperARM processor.

-
-
romana
-
-

A BeBox, running BeOS 4.5. Finally back online!

-
-
aquata
-
-

Retired.

-
-
calum
-
-

Retired.

-
-
- -
- -
- diff --git a/office/directory.xml b/office/directory.xml index 0533b3f..ec7d7d2 100644 --- a/office/directory.xml +++ b/office/directory.xml @@ -7,5 +7,4 @@ - diff --git a/office/index.xml b/office/index.xml index ec92aa2..5a71a93 100644 --- a/office/index.xml +++ b/office/index.xml @@ -12,9 +12,8 @@ open, which basically means it is open most of the time. You can check by taking a look through our web-enabled camera. At the - office we have lots of books, a couple of - computer terminals, and most of the time - an array of knowledgeable + office we have lots of books, + a few computer terminals, and most of the time an array of knowledgeable people to talk to and ask questions.

From d266c39c1b6be2ee022efd1140e2a1767bb1ebaf Mon Sep 17 00:00:00 2001 From: David Bartley Date: Mon, 20 Aug 2007 19:19:48 -0400 Subject: [PATCH 06/51] Removed website documentation. * Docs are outdated and partly incorrect. * Website information should go in the wiki. --- docs/Makefile | 7 +- docs/directory.xml | 1 - docs/editing-example1/Makefile | 3 - docs/editing-example1/directory.xml | 8 - docs/editing-example1/operating-systems.xml | 6 - docs/editing-example2/Makefile | 3 - docs/editing-example2/directory.xml | 9 - docs/editing-example2/operating-systems.xml | 6 - docs/editing-example3/Makefile | 3 - docs/editing-example3/directory.xml | 9 - docs/editing-example3/operating-systems.xml | 13 -- docs/editing-howto.xml | 190 -------------------- docs/index.xml | 1 - docs/website.xml | 4 - 14 files changed, 3 insertions(+), 260 deletions(-) delete mode 100644 docs/editing-example1/Makefile delete mode 100644 docs/editing-example1/directory.xml delete mode 100644 docs/editing-example1/operating-systems.xml delete mode 100644 docs/editing-example2/Makefile delete mode 100644 docs/editing-example2/directory.xml delete mode 100644 docs/editing-example2/operating-systems.xml delete mode 100644 docs/editing-example3/Makefile delete mode 100644 docs/editing-example3/directory.xml delete mode 100644 docs/editing-example3/operating-systems.xml delete mode 100644 docs/editing-howto.xml diff --git a/docs/Makefile b/docs/Makefile index ca60402..84be125 100644 --- a/docs/Makefile +++ b/docs/Makefile @@ -1,7 +1,6 @@ -SUBDIRS = editing-example1 editing-example2 editing-example3 execmanual \ - procedure +SUBDIRS = execmanual procedure INPUTS = index.xml constitution.xml official.xml machine_usage.xml \ - machine_usage_summary.xml website.xml editing-howto.xml \ - constitution-change-20020920.xml execmanual.xml procedure.xml + machine_usage_summary.xml website.xml constitution-change-20020920.xml \ + constitution-change-20040205.xml execmanual.xml procedure.xml include ../default.mk diff --git a/docs/directory.xml b/docs/directory.xml index 4fc0098..52e6b66 100644 --- a/docs/directory.xml +++ b/docs/directory.xml @@ -4,6 +4,5 @@ - diff --git a/docs/editing-example1/Makefile b/docs/editing-example1/Makefile deleted file mode 100644 index 95c1f96..0000000 --- a/docs/editing-example1/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -INPUTS = operating-systems.xml - -include ../../default.mk diff --git a/docs/editing-example1/directory.xml b/docs/editing-example1/directory.xml deleted file mode 100644 index 14b9b7c..0000000 --- a/docs/editing-example1/directory.xml +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/docs/editing-example1/operating-systems.xml b/docs/editing-example1/operating-systems.xml deleted file mode 100644 index aaea6d9..0000000 --- a/docs/editing-example1/operating-systems.xml +++ /dev/null @@ -1,6 +0,0 @@ - - - -

-
- diff --git a/docs/editing-example2/Makefile b/docs/editing-example2/Makefile deleted file mode 100644 index 95c1f96..0000000 --- a/docs/editing-example2/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -INPUTS = operating-systems.xml - -include ../../default.mk diff --git a/docs/editing-example2/directory.xml b/docs/editing-example2/directory.xml deleted file mode 100644 index 1d3fe8e..0000000 --- a/docs/editing-example2/directory.xml +++ /dev/null @@ -1,9 +0,0 @@ - - - - - - - - - diff --git a/docs/editing-example2/operating-systems.xml b/docs/editing-example2/operating-systems.xml deleted file mode 100644 index aaea6d9..0000000 --- a/docs/editing-example2/operating-systems.xml +++ /dev/null @@ -1,6 +0,0 @@ - - - -
-
- diff --git a/docs/editing-example3/Makefile b/docs/editing-example3/Makefile deleted file mode 100644 index 95c1f96..0000000 --- a/docs/editing-example3/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -INPUTS = operating-systems.xml - -include ../../default.mk diff --git a/docs/editing-example3/directory.xml b/docs/editing-example3/directory.xml deleted file mode 100644 index 1d3fe8e..0000000 --- a/docs/editing-example3/directory.xml +++ /dev/null @@ -1,9 +0,0 @@ - - - - - - - - - diff --git a/docs/editing-example3/operating-systems.xml b/docs/editing-example3/operating-systems.xml deleted file mode 100644 index c4a75f4..0000000 --- a/docs/editing-example3/operating-systems.xml +++ /dev/null @@ -1,13 +0,0 @@ - - - -
-
- -

More operating systems may be available.

-
-
- diff --git a/docs/editing-howto.xml b/docs/editing-howto.xml deleted file mode 100644 index 828d2ae..0000000 --- a/docs/editing-howto.xml +++ /dev/null @@ -1,190 +0,0 @@ - - - - - -
-
-

- In order to edit the website you will first have to get the CVS - repository in which it is stored. To do so, go somewhere in your - home directory and type: -

- - export CVS_RSH=ssh
- cvs -d username@caffeine.uwaterloo.ca:/u/www/cvsroot co www - -

- Where username is your CSC user name. You will be - prompted for your password (unless you use an SSH key). After a - while you should have a new directory, www/, with - the CSC pages in it. -

-

- You will also need libxslt and libxml - (including development headers) from Gnome. In debian, - apt-get install libxml2-dev libxslt1-dev. -

-
-
-

- The CSC website is compiled. This means that when you - edit a page, you don't edit the HTML source directly, but - instead edit a page describing the page's content (and - some formatting) and then run a command to generate the HTML - page from these content description pages. -

-

- To generate the CSC website, make sure you are in the directory - into which you checked it out (the www/ directory) - and enter -

- - make - -

- This will compile the whole website. After any changes you make - you will have to recompile the website in the same manner. -

-
-
-

- Let's now suppose we want to add a page detailing what operating - systems the CSC distributes through its CD-burning. First, we go - to the appropriate directory, in this case probably - www/office. Here we now open a new file called - operating-systems.xml in our favourite text editor - (emacs, of course). Take note that the filename ends in - .xml. All CSC web pages should have this file - ending. -

-

- The next thing to do is to add a few standard XML things to the - file. We add the two lines: -

- - <?xml version='1.0'?>
- <!DOCTYPE cscpage SYSTEM "../csc.dtd"> - -

- Note the reference to the file ../csc.dtd. This - file is located in the www/ directory, which is the - parent directory of www/office/, therefore we use - ../. These two lines should appear at the top of - every CSC web page. -

-

- Next we start the actual page. To begin, we open a - cscpage tag with the title attribute set to the - title of our page. We also want to add a header with the CSC - logo, the current section directory and the title of the - page. Don't worry though, as you'll see this is really easy. Add - the following two lines to the end of the page: -

- - <cscpage title="Operating Systems the CSC - distributes">
- <header /> - -

- That's it! So we can see what our page looks like so far, we - also add the footer (with the menu, generation date, and - copyright information) and we close the cscpage - tag. Add the following lines to the end: -

- - <footer />
- </cscpage> - -

- Notice how in the case of header and - footer we have a / before the - >? This is one of the major differences between - HTML and XML: tags that don't really have an end tag, such as - <br> have to be specified as being - empty in XML by adding a / before the - >. This is particularily important to remember - when you add XHTML (XML's version of HTML) to the page. -

-

- Now we want to see what the resulting HTML page looks like. But - first we have to tell make about our new page. To - do so, open up the file www/office/Makefile, find - the line beginning with INPUTS = and simply add - operating-systems.xml to the end of that line. So - the line might look like INPUTS = index.html staff.xml - books.xml operating-systems.xml. Save - Makefile and close it. Now, in the - www/ directory, type make. This will - build the whole website, (hopefully!) including our little - document. Once make is done, have a look at the - resulting file, - www/office/operating-systems.html. It should look - like example - 1 (use your browsers Back button to return to this page - after viewing the example). -

-

- Looking at the generated page, you may have noticed that it does - not yet appear in the menu at the top of the page. Opening up - the special file www/office/directory.xml you will - see several entries, each corresponding to one of the menu - items. After the last line beginning with - <diritem, add in the following line: -

- - <diritem title=""Operating Systems" - href="operating-systems.html" /> - -

- Now recompile the site with make. You should see - that the page now looks something like example - 2. Also note that all the other office pages will now have a - reference to the new operating systems page. -

-

- With that out of the way, it's time to add some content. You may - be happy to hear that you can add regular (X)HTML to any CSC web - page. So, we'll add the following content between the - <header /> and <footer /> - of the page: -

- - <section title="List of operating systems">
- <ul>
- <li><a href="http://www.debian.org/">Debian GNU/Linux</a></li>
- <li><a href="http://www.freebsd.org/">FreeBSD</a></li>
- </ul>
- <p>More operating systems may be available.</p>
- </section>
- -

- As usual, compile your changes using make and have - a look. The resulting file should look something like example 3. A - few things to keep in mind are: -

-
    -
  • - Always use lower-case in your XHTML tags. XML is - case-sensitive. For example: <br/> is good - whereas <BR/> is bad. -
    • -
  • - Always close your tags. If it's a tag that never encloses - anything use the <tag/> syntax. For - example: <ul> <li>Item - 1<br/>Linebreak</li> <li>Item - 2</li></ul> is good, whereas - <ul> <li>Item - 1<br>Linebreak <li>Item 2</ul> is bad. -
    • -
  • - You must place HTML code inside <section> - tags. You can have as many section as you want on the page. -
    • -
-
-
-
-

See the Editing Howto for - information on editing the website

-

I have provided some helpful links regarding XSLT and XML below. From fab538456c93fa412f85718ee67b8bc125b66dd2 Mon Sep 17 00:00:00 2001 From: David Bartley Date: Wed, 22 Aug 2007 02:27:09 -0400 Subject: [PATCH 07/51] Remove outdated operating systems page. * If we want, we can maintain the list on the wiki. --- office/Makefile | 2 +- office/directory.xml | 1 - office/index.xml | 7 +++---- office/operating-systems.xml | 39 ------------------------------------ 4 files changed, 4 insertions(+), 45 deletions(-) delete mode 100644 office/operating-systems.xml diff --git a/office/Makefile b/office/Makefile index 3b3c535..9963b72 100644 --- a/office/Makefile +++ b/office/Makefile @@ -1,5 +1,5 @@ SUBDIRS = books -INPUTS = index.xml staff.xml books.xml operating-systems.xml webcam.xml webcam-streaming.xml +INPUTS = index.xml staff.xml books.xml webcam.xml webcam-streaming.xml include ../default.mk diff --git a/office/directory.xml b/office/directory.xml index ec7d7d2..ed49cf7 100644 --- a/office/directory.xml +++ b/office/directory.xml @@ -6,5 +6,4 @@ - diff --git a/office/index.xml b/office/index.xml index 5a71a93..2780b5e 100644 --- a/office/index.xml +++ b/office/index.xml @@ -18,12 +18,11 @@

One of our most popular services at the office is providing anybody - with CD copies of Free Software and Open Source operating system + with CD/DVD copies of Free Software and Open Source operating system distributions (including, but by no means limited to, Debian GNU/Linux, Mandrake Linux, Red Hat Linux, FreeBSD and NetBSD for various - architectures. Please check here for - a list of available operating systems.). The cost is $0.50 per CD at - the time of this writing, or free if you provide your own CDs. + architectures. The cost is $0.50 per disc at the time of this writing, or + free if you provide your own discs.

Another favourite is our $0.50 pop for members. We have a fridge in diff --git a/office/operating-systems.xml b/office/operating-systems.xml deleted file mode 100644 index 2fd9a74..0000000 --- a/office/operating-systems.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - -

- -
- -

One of the most popular services we offer is providing CD copies of -Free Software and Open Source operating system distributions for anyone -who asks. The cost is $1.00 per CD at the time of writing, or free if -you provide your own CDs.

- -

Here is a list of the operating systems we have available:

- - - -

More operating systems may be available. As well, we can download any -Free operating system to burn on CD upon request. Unfortunately, we -cannot share non-Free operating systems or software with you, due to -various legal restrictions.

-
- -
- From fbd1f3ca1820f4112c3a686b9843fa4a1c1fafc2 Mon Sep 17 00:00:00 2001 From: David Bartley Date: Thu, 23 Aug 2007 02:40:18 -0400 Subject: [PATCH 08/51] Migrated exec manual to wiki and moved old procedure manual into ~www/misc. --- docs/Makefile | 3 +- docs/directory.xml | 1 - docs/execmanual.xml | 20 - docs/execmanual/Makefile | 36 - docs/execmanual/book.xml | 17 - docs/execmanual/general.xml | 93 -- docs/execmanual/president.xml | 64 -- docs/execmanual/sysadmin.xml | 135 --- docs/execmanual/vice-president.xml | 208 ----- docs/index.xml | 3 - docs/procedure.xml | 16 - docs/procedure/.gitignore | 10 - docs/procedure/Makefile | 36 - docs/procedure/csc.procedure.latex | 1377 --------------------------- docs/procedure/procedure.tex | 1379 ---------------------------- 15 files changed, 1 insertion(+), 3397 deletions(-) delete mode 100644 docs/execmanual.xml delete mode 100644 docs/execmanual/Makefile delete mode 100644 docs/execmanual/book.xml delete mode 100644 docs/execmanual/general.xml delete mode 100644 docs/execmanual/president.xml delete mode 100644 docs/execmanual/sysadmin.xml delete mode 100644 docs/execmanual/vice-president.xml delete mode 100644 docs/procedure.xml delete mode 100644 docs/procedure/.gitignore delete mode 100644 docs/procedure/Makefile delete mode 100644 docs/procedure/csc.procedure.latex delete mode 100644 docs/procedure/procedure.tex diff --git a/docs/Makefile b/docs/Makefile index 84be125..d86b300 100644 --- a/docs/Makefile +++ b/docs/Makefile @@ -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 diff --git a/docs/directory.xml b/docs/directory.xml index 52e6b66..88c2bdc 100644 --- a/docs/directory.xml +++ b/docs/directory.xml @@ -4,5 +4,4 @@ - diff --git a/docs/execmanual.xml b/docs/execmanual.xml deleted file mode 100644 index 0a96cff..0000000 --- a/docs/execmanual.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - - -
-
-

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.

-

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.

-

The executive manual is written using DocBook and is available - in HTML format. The - DocBook source is also on-line.

-
-
- diff --git a/docs/execmanual/Makefile b/docs/execmanual/Makefile deleted file mode 100644 index 0b6e0c7..0000000 --- a/docs/execmanual/Makefile +++ /dev/null @@ -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 $@ $< diff --git a/docs/execmanual/book.xml b/docs/execmanual/book.xml deleted file mode 100644 index cffee78..0000000 --- a/docs/execmanual/book.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - -]> - -Computer Science Club Exec Manual -&prez; -&veep; -&sysadmin; -&general; - - diff --git a/docs/execmanual/general.xml b/docs/execmanual/general.xml deleted file mode 100644 index 770dc8e..0000000 --- a/docs/execmanual/general.xml +++ /dev/null @@ -1,93 +0,0 @@ - - - General Information - - Our mailbox is in the MathSoc office. It should be checked on a - regular basis. - - - - Useful Contacts - There are several people that many exec will need contact information - for. Their contact info follows and should be updated when - these people change! - - - - 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 - dschell@uwaterloo.ca or at extension 2207. - - - - 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 - vicd@uwaterloo.ca. 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 vkorody@uwaterloo.ca or - called at ext. 2042. - - - - 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 - president@mathsoc.uwaterloo.ca and - VPF@mathsoc.uwaterloo.ca. They also have a projector that - we can borrow from time to time. - - - - 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). - - - - - - - - The E-mail I sent to Vic: - Hi, - 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. - - Thanks for your consideration. - - Tim Loach - CSC President - - And his Response: - Hi Timothy, - - 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. - - 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. - - Best, - - Vic - - diff --git a/docs/execmanual/president.xml b/docs/execmanual/president.xml deleted file mode 100644 index 111fb23..0000000 --- a/docs/execmanual/president.xml +++ /dev/null @@ -1,64 +0,0 @@ - - - President - - 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. - - - 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. - - - diff --git a/docs/execmanual/sysadmin.xml b/docs/execmanual/sysadmin.xml deleted file mode 100644 index 509e2ba..0000000 --- a/docs/execmanual/sysadmin.xml +++ /dev/null @@ -1,135 +0,0 @@ - - - System Administrator - - 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. - - 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. - - - Your responsibilities - - According to the constitution, the following are the duties - of the sysadmin: - - - - to operate any and all equipment in the possession of the Club; - - - - to maintain and upgrade the software on equipment that is - operated by the Club; - - - - to facilitate the use of equipment that is operated by the Club. - - - - 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. - - - - Useful contacts - - - - You can try getting access to the machine room 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. - - - - - - Changing Users - To alter users and groups please use the cpu command. cpu is setup - to use ldap to change any given user or group. - - To change a users group use cpu usermod -G current,groups,new,groups - man cpu-ldap - cpu groupadd cvs-ceo - - - - Expiring Users - - 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 - - - - 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 - - - - diff --git a/docs/execmanual/vice-president.xml b/docs/execmanual/vice-president.xml deleted file mode 100644 index 4b2282a..0000000 --- a/docs/execmanual/vice-president.xml +++ /dev/null @@ -1,208 +0,0 @@ - - - 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?" - - - - \ No newline at end of file diff --git a/docs/index.xml b/docs/index.xml index c35a465..c120a81 100644 --- a/docs/index.xml +++ b/docs/index.xml @@ -11,9 +11,6 @@

diff --git a/docs/procedure.xml b/docs/procedure.xml deleted file mode 100644 index 4c22299..0000000 --- a/docs/procedure.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - -
-
-

This is an outdated procedures manual written by previous - exec. Useful information from this should get moved into the new exec manual.

-

The procedures manual is written using LaTeX and is available - in PDF format. The - LaTeX source is also on-line.

-
-