David Tenty
16 years ago
commit
442910af90
@ -1,10 +0,0 @@ |
||||
Convert cellspacing and cellpadding to CSS equivalents. |
||||
IMO (dtbartle), keyboard thing on front page is way too big - reduce or remove. |
||||
Make RSS and ICS feeds more prominent. |
||||
Replace /events with a web-based calendar? |
||||
Replace all email addresses with generated graphics? |
||||
Remove books.xml or get it to work with koha. |
||||
Possibly rewrite web page build instructions. |
||||
On media pages, get rid of trailing comma. |
||||
Replace <br>'s with <p>'s wherever it makes sense. |
||||
Replace <strong>, <b>, <i>, etc... tags with CSS. |
||||
|
Before Width: | Height: | Size: 3.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.3 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.7 KiB |
|
Before Width: | Height: | Size: 1.6 KiB |
|
Before Width: | Height: | Size: 208 B |
|
Before Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 511 B |
|
Before Width: | Height: | Size: 2.4 KiB |
|
Before Width: | Height: | Size: 3.5 KiB |
|
Before Width: | Height: | Size: 2.0 KiB |
|
Before Width: | Height: | Size: 3.6 KiB |
|
Before Width: | Height: | Size: 2.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
|
Before Width: | Height: | Size: 3.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
|
Before Width: | Height: | Size: 2.7 KiB |
@ -1,4 +0,0 @@ |
||||
INPUTS = index.xml
|
||||
SUBDIRS =
|
||||
|
||||
include ../default.mk |
||||
@ -1,8 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE directory SYSTEM "../csc.dtd"> |
||||
|
||||
<directory title="Clubs"> |
||||
<diritem title="Mailing Lists" |
||||
href="http://mailman.csclub.uwaterloo.ca/" /> |
||||
</directory> |
||||
|
Before Width: | Height: | Size: 95 KiB |
Binary file not shown.
@ -0,0 +1,30 @@ |
||||
-----BEGIN CERTIFICATE----- |
||||
MIIFMzCCBBugAwIBAgIJAPR1nfSO+Jy1MA0GCSqGSIb3DQEBBQUAMIHBMR8wHQYD |
||||
VQQKExZVbml2ZXJzaXR5IG9mIFdhdGVybG9vMR4wHAYDVQQLExVDb21wdXRlciBT |
||||
Y2llbmNlIENsdWIxKDAmBgkqhkiG9w0BCQEWGWNlcnRzQGNzY2x1Yi51d2F0ZXJs |
||||
b28uY2ExETAPBgNVBAcTCFdhdGVybG9vMRAwDgYDVQQIEwdPbnRhcmlvMQswCQYD |
||||
VQQGEwJDQTEiMCAGA1UEAxMZQ1NDIENlcnRpZmljYXRlIEF1dGhvcml0eTAeFw0w |
||||
NzA4MjkxMjEyMDdaFw0xNzA4MjkxMjEyMDdaMIHBMR8wHQYDVQQKExZVbml2ZXJz |
||||
aXR5IG9mIFdhdGVybG9vMR4wHAYDVQQLExVDb21wdXRlciBTY2llbmNlIENsdWIx |
||||
KDAmBgkqhkiG9w0BCQEWGWNlcnRzQGNzY2x1Yi51d2F0ZXJsb28uY2ExETAPBgNV |
||||
BAcTCFdhdGVybG9vMRAwDgYDVQQIEwdPbnRhcmlvMQswCQYDVQQGEwJDQTEiMCAG |
||||
A1UEAxMZQ1NDIENlcnRpZmljYXRlIEF1dGhvcml0eTCCASIwDQYJKoZIhvcNAQEB |
||||
BQADggEPADCCAQoCggEBALdpE8mFzGLpAQRtNSy+mJs4P335wuyEEXzjYM+elffk |
||||
TO6ek74NiFSCymfcWNwCG62y4HQoAjY+bYm+b1qp+5iHGWEHWHSTz3IMzV9UdrZo |
||||
zHXKV3YWxAkjXg8NU1PQVybj6F9ICjhf19POg2NDJ2dHxDAGJtfoBB8vbm9wcj16 |
||||
Aa3dSSj5PZ7rPTUyChiqQg6DPAgvveNtc6SEcwnfD8Fhf7evBCw3En0YxvLFNiaa |
||||
cd7173EsKXzICADnEdhqCSyc8HwUwc0KA012NymP/IWQx1qlYthNVjHKNorBMcVt |
||||
hW3QrE97RqiOUdZ2UCpGom6F1bdO5dd2bDWvV9Rvnj0CAwEAAaOCASowggEmMAwG |
||||
A1UdEwQFMAMBAf8wHQYDVR0OBBYEFLiqXbgrCsS9f+KZeHrGhB/s1MwPMIH2BgNV |
||||
HSMEge4wgeuAFLiqXbgrCsS9f+KZeHrGhB/s1MwPoYHHpIHEMIHBMR8wHQYDVQQK |
||||
ExZVbml2ZXJzaXR5IG9mIFdhdGVybG9vMR4wHAYDVQQLExVDb21wdXRlciBTY2ll |
||||
bmNlIENsdWIxKDAmBgkqhkiG9w0BCQEWGWNlcnRzQGNzY2x1Yi51d2F0ZXJsb28u |
||||
Y2ExETAPBgNVBAcTCFdhdGVybG9vMRAwDgYDVQQIEwdPbnRhcmlvMQswCQYDVQQG |
||||
EwJDQTEiMCAGA1UEAxMZQ1NDIENlcnRpZmljYXRlIEF1dGhvcml0eYIJAPR1nfSO |
||||
+Jy1MA0GCSqGSIb3DQEBBQUAA4IBAQA5z4a8c7PXhDUm2wgslWBftfCiY7lek7Vt |
||||
nZK/gPQ7gqg4IVuRMVhbjt7MUAXV/3PqJqJTIcLqJ6NlqIviryafaX4Njqr6EUq3 |
||||
LqAEeqqFtGSLnIQxF6SrWOkMNNvj6yRD1cCz6Sbj4sPxh301wfDJCvxnRRsWMxDH |
||||
NjYtQq0+hTK2FIlHP9FDp9FjHYOJw12WtatAQEfeB0tcXNMaUGtCjy15OGgFoLMT |
||||
x+iD/QU27fU2eeUlZowCtKrsYTnHPE65PY9czBxUnSCkFISldzuQ8/N9qkW9JnLI |
||||
xqplu2SWNdPTtUhBjCxYai4NeAAjVc0RYUC9xIDFXY1PrkfNUb6v |
||||
-----END CERTIFICATE----- |
||||
@ -1,7 +0,0 @@ |
||||
SUBDIRS = editing-example1 editing-example2 editing-example3 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
|
||||
|
||||
include ../default.mk |
||||
@ -1,9 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE directory SYSTEM "../csc.dtd"> |
||||
|
||||
<directory title="Documents"> |
||||
<diritem title="Official documents" href="official.html" /> |
||||
<diritem title="Website documents" href="website.html" /> |
||||
<diritem title="Executive manual" href="execmanual.html" /> |
||||
</directory> |
||||
@ -1,3 +0,0 @@ |
||||
INPUTS = operating-systems.xml
|
||||
|
||||
include ../../default.mk |
||||
@ -1,8 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE directory SYSTEM "../../csc.dtd"> |
||||
|
||||
<directory title="Office"> |
||||
<diritem title="Staff" href="staff.html" /> |
||||
<diritem title="Books" href="books.html" /> |
||||
</directory> |
||||
@ -1,6 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
<!DOCTYPE cscpage SYSTEM "../../csc.dtd"> |
||||
<cscpage title="Operating Systems the CSC distributes" pre="../../"> |
||||
<header/> |
||||
<footer/> |
||||
</cscpage> |
||||
@ -1,3 +0,0 @@ |
||||
INPUTS = operating-systems.xml
|
||||
|
||||
include ../../default.mk |
||||
@ -1,9 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE directory SYSTEM "../../csc.dtd"> |
||||
|
||||
<directory title="Office"> |
||||
<diritem title="Staff" href="staff.html" /> |
||||
<diritem title="Books" href="books.html" /> |
||||
<diritem title="Operating Systems" href="operating-systems.html" /> |
||||
</directory> |
||||
@ -1,6 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
<!DOCTYPE cscpage SYSTEM "../../csc.dtd"> |
||||
<cscpage title="Operating Systems the CSC distributes" pre="../../"> |
||||
<header/> |
||||
<footer/> |
||||
</cscpage> |
||||
@ -1,3 +0,0 @@ |
||||
INPUTS = operating-systems.xml
|
||||
|
||||
include ../../default.mk |
||||
@ -1,9 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE directory SYSTEM "../../csc.dtd"> |
||||
|
||||
<directory title="Office"> |
||||
<diritem title="Staff" href="staff.html" /> |
||||
<diritem title="Books" href="books.html" /> |
||||
<diritem title="Operating Systems" href="operating-systems.html" /> |
||||
</directory> |
||||
@ -1,13 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
<!DOCTYPE cscpage SYSTEM "../../csc.dtd"> |
||||
<cscpage title="Operating Systems the CSC distributes" pre="../../"> |
||||
<header/> |
||||
<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> |
||||
<footer/> |
||||
</cscpage> |
||||
@ -1,190 +0,0 @@ |
||||
<?xml version='1.0'?> |
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd"> |
||||
|
||||
<cscpage title="CSC Website Editing Howto"> |
||||
<header/> |
||||
<section title="Getting started"> |
||||
<p> |
||||
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: |
||||
</p> |
||||
<code> |
||||
export CVS_RSH=ssh<br /> |
||||
cvs -d username@caffeine.uwaterloo.ca:/u/www/cvsroot co www |
||||
</code> |
||||
<p> |
||||
Where <code>username</code> 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, <code>www/</code>, with |
||||
the CSC pages in it. |
||||
</p> |
||||
<p> |
||||
You will also need <code>libxslt</code> and <code>libxml</code> |
||||
(including development headers) from Gnome. In debian, |
||||
<code>apt-get install libxml2-dev libxslt1-dev</code>. |
||||
</p> |
||||
</section> |
||||
<section title="Compiling the website"> |
||||
<p> |
||||
The CSC website is <i>compiled</i>. 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 <i>content</i> (and |
||||
some formatting) and then run a command to generate the HTML |
||||
page from these content description pages. |
||||
</p> |
||||
<p> |
||||
To generate the CSC website, make sure you are in the directory |
||||
into which you checked it out (the <code>www/</code> directory) |
||||
and enter |
||||
</p> |
||||
<code> |
||||
make |
||||
</code> |
||||
<p> |
||||
This will compile the whole website. After any changes you make |
||||
you will have to recompile the website in the same manner. |
||||
</p> |
||||
</section> |
||||
<section title="Adding a regular page"> |
||||
<p> |
||||
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 |
||||
<code>www/office</code>. Here we now open a new file called |
||||
<code>operating-systems.xml</code> in our favourite text editor |
||||
(emacs, of course). Take note that the filename ends in |
||||
<code>.xml</code>. All CSC web pages should have this file |
||||
ending. |
||||
</p> |
||||
<p> |
||||
The next thing to do is to add a few standard XML things to the |
||||
file. We add the two lines: |
||||
</p> |
||||
<code> |
||||
<?xml version='1.0'?><br /> |
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd"> |
||||
</code> |
||||
<p> |
||||
Note the reference to the file <code>../csc.dtd</code>. This |
||||
file is located in the <code>www/</code> directory, which is the |
||||
parent directory of <code>www/office/</code>, therefore we use |
||||
<code>../</code>. These two lines should appear at the top of |
||||
every CSC web page. |
||||
</p> |
||||
<p> |
||||
Next we start the actual page. To begin, we open a |
||||
<code>cscpage</code> 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: |
||||
</p> |
||||
<code> |
||||
<cscpage title="Operating Systems the CSC |
||||
distributes"><br /> |
||||
<header /> |
||||
</code> |
||||
<p> |
||||
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 <code>cscpage</code> |
||||
tag. Add the following lines to the end: |
||||
</p> |
||||
<code> |
||||
<footer /><br /> |
||||
</cscpage> |
||||
</code> |
||||
<p> |
||||
Notice how in the case of <code>header</code> and |
||||
<code>footer</code> we have a <code>/</code> before the |
||||
<code>></code>? This is one of the major differences between |
||||
HTML and XML: tags that don't really have an end tag, such as |
||||
<code><br></code> have to be specified as being |
||||
<i>empty</i> in XML by adding a <code>/</code> before the |
||||
<code>></code>. This is particularily important to remember |
||||
when you add XHTML (XML's version of HTML) to the page. |
||||
</p> |
||||
<p> |
||||
Now we want to see what the resulting HTML page looks like. But |
||||
first we have to tell <code>make</code> about our new page. To |
||||
do so, open up the file <code>www/office/Makefile</code>, find |
||||
the line beginning with <code>INPUTS = </code> and simply add |
||||
<code>operating-systems.xml</code> to the end of that line. So |
||||
the line might look like <code>INPUTS = index.html staff.xml |
||||
books.xml operating-systems.xml</code>. Save |
||||
<code>Makefile</code> and close it. Now, in the |
||||
<code>www/</code> directory, type <code>make</code>. This will |
||||
build the whole website, (hopefully!) including our little |
||||
document. Once <code>make</code> is done, have a look at the |
||||
resulting file, |
||||
<code>www/office/operating-systems.html</code>. It should look |
||||
like <a href="editing-example1/operating-systems.html">example |
||||
1</a> (use your browsers Back button to return to this page |
||||
after viewing the example). |
||||
</p> |
||||
<p> |
||||
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 <code>www/office/directory.xml</code> you will |
||||
see several entries, each corresponding to one of the menu |
||||
items. After the last line beginning with |
||||
<code><diritem</code>, add in the following line: |
||||
</p> |
||||
<code> |
||||
<diritem title=""Operating Systems" |
||||
href="operating-systems.html" /> |
||||
</code> |
||||
<p> |
||||
Now recompile the site with <code>make</code>. You should see |
||||
that the page now looks something like <a |
||||
href="editing-example2/operating-systems.html">example |
||||
2</a>. Also note that all the other office pages will now have a |
||||
reference to the new operating systems page. |
||||
</p> |
||||
<p> |
||||
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 |
||||
<code><header /></code> and <code><footer /></code> |
||||
of the page: |
||||
</p> |
||||
<code> |
||||
<section title="List of operating systems"><br/> |
||||
<ul><br/> |
||||
<li><a href="http://www.debian.org/">Debian GNU/Linux</a></li><br/> |
||||
<li><a href="http://www.freebsd.org/">FreeBSD</a></li><br/> |
||||
</ul><br/> |
||||
<p>More operating systems may be available.</p><br/> |
||||
</section><br/> |
||||
</code> |
||||
<p> |
||||
As usual, compile your changes using <code>make</code> and have |
||||
a look. The resulting file should look something like <a |
||||
href="editing-example3/operating-systems.html">example 3</a>. A |
||||
few things to keep in mind are: |
||||
</p> |
||||
<ul> |
||||
<li> |
||||
Always use lower-case in your XHTML tags. XML is |
||||
case-sensitive. For example: <code><br/></code> is good |
||||
whereas <code><BR/></code> is bad. |
||||
</li> |
||||
<li> |
||||
Always close your tags. If it's a tag that never encloses |
||||
anything use the <code><tag/></code> syntax. For |
||||
example: <code><ul> <li>Item |
||||
1<br/>Linebreak</li> <li>Item |
||||
2</li></ul></code> is good, whereas |
||||
<code><ul> <li>Item |
||||
1<br>Linebreak <li>Item 2</ul></code> is bad. |
||||
</li> |
||||
<li> |
||||
You must place HTML code inside <code><section></code> |
||||
tags. You can have as many section as you want on the page. |
||||
</li> |
||||
</ul> |
||||
</section> |
||||
<footer /> |
||||
</cscpage> |
||||
@ -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> |
||||