Merge branch 'master' of /users/www/www/
Conflicts: favicon.ico
This commit is contained in:
David Tenty
commit
442910af90
12
Makefile
12
Makefile
|
|
@ -1,7 +1,7 @@
|
|||
INPUTS = index.xml
|
||||
SUBDIRS = about events docs office news users clubs media
|
||||
SUBDIRS = about events office news services media
|
||||
|
||||
first: noroot events.ics books.xml members.xml menu.xml all
|
||||
first: noroot events.ics members.xml all
|
||||
find ! -regex '.*/\..*' -type f ! -perm -0664 -print0 | xargs -r0 chmod u=rwX,g=rwX,o=rX || true
|
||||
find ! -regex '.*/\..*' -type d ! -perm 2775 -print0 | xargs -r0 chmod 2775 || true
|
||||
find ! -regex '.*/\..*' -type d ! -group www -print0 | xargs -r0 chgrp www || true
|
||||
|
|
@ -15,12 +15,6 @@ members.xml:
|
|||
ceoquery memberlist | sort | awk -F \| '{ name = $$1; program = $$2; userid = $$3; gsub(/&/, "\\&", name); gsub(/&/, "\\&", program); gsub(/"/, "\\"", name); gsub(/"/, "\\"", program); print "<member name=\"" name "\" program=\"" program "\" userid=\"" userid "\" />"; }' >> $@
|
||||
echo '</memberlist>' >> $@
|
||||
|
||||
books.xml:
|
||||
echo '<?xml version='\''1.0'\'' encoding="ISO-8859-1"?>' > $@
|
||||
echo '<booklist>' >> $@
|
||||
ceoquery booklist | awk -F \| '{ isbn = $$1; title = $$2; author = $$3; edition = $$4; published = $$5; gsub(/&/, "\\&", title); gsub(/&/, "\\&", author); gsub(/&/, "\\&", published); gsub(/&/, "\\&", edition); gsub(/"/, "\\"", title); gsub(/"/, "\\"", author); gsub(/"/, "\\"", published); gsub(/"/, "\\"", edition); print "<book isbn=\"" isbn "\" title=\"" title "\" author=\"" author "\" edition=\"" edition "\" published=\"" published "\"/>"; }' >> $@
|
||||
echo '</booklist>' >> $@
|
||||
|
||||
events.ics:
|
||||
perl scripts/xml2ics.pl events.xml > events.ics
|
||||
|
||||
|
|
@ -30,4 +24,4 @@ default.mk: default.mk.in
|
|||
echo 'ROOT = '`pwd` > $@
|
||||
cat $< >> $@
|
||||
|
||||
.PHONY: members.xml books.xml
|
||||
.PHONY: members.xml
|
||||
|
|
|
|||
10
TODO
10
TODO
|
|
@ -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.
|
||||
|
|
@ -1,4 +1,5 @@
|
|||
INPUTS = index.xml exec.xml members.xml
|
||||
INPUTS = index.xml exec.xml members.xml constitution.xml \
|
||||
constitution-change-20020920.xml constitution-change-20040205.xml
|
||||
|
||||
include ../default.mk
|
||||
|
||||
|
|
|
|||
|
|
@ -6,12 +6,12 @@
|
|||
|
||||
<header />
|
||||
|
||||
<section title="1. Name">
|
||||
<section title="1. Name" anchor="name">
|
||||
<ol><li> The name of this organization shall be the "Computer Science Club
|
||||
of the University of Waterloo".</li>
|
||||
</ol>
|
||||
</section>
|
||||
<section title="2. Purpose">
|
||||
<section title="2. Purpose" anchor="purpose">
|
||||
<ol><li><a id="purpose">The Club</a> is organized and will be operated exclusively for educational
|
||||
and scientific purposes in furtherance of:
|
||||
<ul>
|
||||
|
|
@ -34,7 +34,7 @@ decided by the club membership.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="3. Membership">
|
||||
<section title="3. Membership" anchor="membership">
|
||||
|
||||
<ol>
|
||||
|
||||
|
|
@ -59,7 +59,7 @@ The membership fee is set from time to time by the Executive.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="4. Officers">
|
||||
<section title="4. Officers" anchor="officers">
|
||||
<ol><li> The officers of the Club shall be:
|
||||
<ol><li> President</li>
|
||||
<li> Vice-President</li>
|
||||
|
|
@ -110,7 +110,7 @@ sale. After a reasonable time, control of the meeting is given to the
|
|||
CRO who will manage the election of the President, Vice-President,
|
||||
Treasurer, and Secretary, in that order. Each election shall be
|
||||
carried out by secret ballot, in a manner to be decided on by the CRO,
|
||||
with the approval of the memberdip. An accurate count of votes for
|
||||
with the approval of the membership. An accurate count of votes for
|
||||
each candidate for each position must be made and recorded by the CRO.
|
||||
A simple heads-down-hands-up method is considered acceptable. As soon
|
||||
as possible the CRO will announce the results of the election and the
|
||||
|
|
@ -145,7 +145,7 @@ Such elections would be for all offices which are vacant.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="5. Duties of Officers">
|
||||
<section title="5. Duties of Officers" anchor="duties">
|
||||
<ol>
|
||||
|
||||
<li> The duties of the President shall be:
|
||||
|
|
@ -197,7 +197,7 @@ in <a href="#sysduties">7.2</a>.</li>
|
|||
</li>
|
||||
</ol>
|
||||
</section>
|
||||
<section title="6. Executive Council">
|
||||
<section title="6. Executive Council" anchor="executive">
|
||||
<ol>
|
||||
|
||||
<li> The executive council shall consist of the present officers of
|
||||
|
|
@ -213,7 +213,7 @@ all recent executive council decisions shall be announced at the next
|
|||
regular meeting of the club.</li>
|
||||
</ol>
|
||||
</section>
|
||||
<section title="7. Committees">
|
||||
<section title="7. Committees" anchor="committees">
|
||||
<h3>1. Programme Committee</h3>
|
||||
<ol><li>The programme committee shall be a standing committee.</li>
|
||||
<li> The programme committee shall plan and arrange meetings of the Club in
|
||||
|
|
@ -264,7 +264,7 @@ temporary committees as is deemed necessary.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="8. Meetings">
|
||||
<section title="8. Meetings" anchor="meetings">
|
||||
|
||||
<ol><li> General meetings of the Club shall
|
||||
be called at times designated by the
|
||||
|
|
@ -282,12 +282,12 @@ of the Club.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="9. Finances">
|
||||
<section title="9. Finances" anchor="finances">
|
||||
|
||||
<ol>
|
||||
|
||||
<li> The Treasurer shall present to the Club, before the end of each
|
||||
accademic term, a complete financial statement of the past period, and
|
||||
academic term, a complete financial statement of the past period, and
|
||||
a tentative budget for the following academic term.</li>
|
||||
|
||||
<li> The Treasurer shall present, as part of the tentative budget, a
|
||||
|
|
@ -302,7 +302,7 @@ that the financial records are complete and accurate.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="10. Amendments and Procedures">
|
||||
<section title="10. Amendments and Procedures" anchor="amendments">
|
||||
<ol><li> Amendments to the constitution shall be made in the following
|
||||
manner:
|
||||
|
||||
|
|
@ -342,7 +342,7 @@ Club again within sixty (60) days.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="11. Dissolution">
|
||||
<section title="11. Dissolution" anchor="dissolution">
|
||||
<ol><li> In the event of dissolution of the Club,
|
||||
all assets of the Club shall be
|
||||
transferred to the Mathematics Society of the University of Waterloo.</li>
|
||||
|
|
@ -350,7 +350,7 @@ transferred to the Mathematics Society of the University of Waterloo.</li>
|
|||
|
||||
</section>
|
||||
|
||||
<section title="12. Use of Club Resources">
|
||||
<section title="12. Use of Club Resources" anchor="resources">
|
||||
|
||||
<ol><li> All resources under control of the Club are to be used in accordance with
|
||||
the aims of the Club.</li>
|
||||
|
|
@ -368,7 +368,7 @@ course, responsible to the person granting permission.</li>
|
|||
</ol>
|
||||
</section>
|
||||
|
||||
<section title="Revision">
|
||||
<section title="Revision" anchor="revision">
|
||||
<p>The constitution was last revised on 5 February 2004.</p>
|
||||
</section>
|
||||
|
||||
|
|
@ -3,6 +3,7 @@
|
|||
<!DOCTYPE directory SYSTEM "../csc.dtd">
|
||||
|
||||
<directory title="About">
|
||||
<diritem title="Constitution" href="constitution.html" />
|
||||
<diritem title="The Executive" href="exec.html" />
|
||||
<diritem title="Membership List" href="members.html" />
|
||||
</directory>
|
||||
|
|
|
|||
|
|
@ -4,49 +4,49 @@
|
|||
|
||||
<cscpage title="The CSC Executive">
|
||||
<header />
|
||||
<section title="The Spring 2007 Executive">
|
||||
<section title="The Executive">
|
||||
<execlist>
|
||||
<exec position="President"
|
||||
name="Gaelan D'costa"
|
||||
name="Holden Karau"
|
||||
sex="male"
|
||||
userid="president" />
|
||||
|
||||
<exec position="Vice President"
|
||||
name="Kyle Larose"
|
||||
name="Alex McCausland"
|
||||
sex="male"
|
||||
userid="vice-president" />
|
||||
|
||||
<exec position="Treasurer"
|
||||
name="Kyle Spaans"
|
||||
name="Dominik Chlobowski"
|
||||
sex="male"
|
||||
userid="treasurer" />
|
||||
|
||||
<exec position="Secretary"
|
||||
name="Erik Louie"
|
||||
name="Sean Cumming"
|
||||
sex="male"
|
||||
userid="secretary" />
|
||||
|
||||
<exec position="System Administrator"
|
||||
type="appointed"
|
||||
name="Michael Spang"
|
||||
name="David Tenty"
|
||||
sex="male"
|
||||
userid="sysadmin" />
|
||||
|
||||
<exec position="Librarian"
|
||||
type="appointed"
|
||||
name="David Tenty"
|
||||
name="Nobody"
|
||||
sex="male"
|
||||
userid="librarian" />
|
||||
|
||||
<exec position="Imapd (Individual Making Arrangements for Pop Delivery)"
|
||||
type="appointed"
|
||||
name="could be you? or groccery gateway"
|
||||
name="Nobody"
|
||||
sex="male"
|
||||
userid="imapd" />
|
||||
|
||||
<exec position="Web Master"
|
||||
type="appointed"
|
||||
name="Nick Guenther"
|
||||
name="Nobody"
|
||||
sex="male"
|
||||
userid="www" />
|
||||
</execlist>
|
||||
|
|
@ -58,7 +58,7 @@
|
|||
held, check the <a href="../index.html">homepage</a> and the <a
|
||||
href="http://csclub.uwaterloo.ca/newsgroup/thread.php?group=uw.csc">uw.csc newsgroup</a>. For details on the
|
||||
election rules, see the <a
|
||||
href="../docs/constitution.html">constitution</a>.
|
||||
href="constitution.html">constitution</a>.
|
||||
</p>
|
||||
</section>
|
||||
<footer/>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
|
||||
<section title="What... is your name?">
|
||||
<p>
|
||||
According to our <a href="../docs/constitution.html">constitution</a> we
|
||||
According to our <a href="constitution.html">constitution</a> we
|
||||
are officially the "Computer Science Club of the University
|
||||
of Waterloo." You can contact <a href="exec.html">our
|
||||
executive</a> by e-mail at <a
|
||||
|
|
@ -15,20 +15,18 @@
|
|||
come by the <a href="../office/">office</a> in MC3036/3037 or mail
|
||||
us at the following address.
|
||||
</p>
|
||||
<pre>
|
||||
Computer Science Club
|
||||
<pre>Computer Science Club
|
||||
Math & Computer 3036/3037
|
||||
University of Waterloo
|
||||
200 University Avenue West
|
||||
Waterloo, Ontario, CANADA
|
||||
N2L 3G1
|
||||
</pre>
|
||||
<p>Our office phone number is (519) 888-4567 x33870</p>
|
||||
N2L 3G1</pre>
|
||||
<p>Our office phone number is (519) 888-4567 x33870.</p>
|
||||
</section>
|
||||
|
||||
<section title="What... is your quest?">
|
||||
<p>
|
||||
Again our lovely <a href="../docs/constitution.html">constitution</a> (it
|
||||
Again our lovely <a href="constitution.html">constitution</a> (it
|
||||
really <i>is</i> quite a read, see for yourself!) answers this
|
||||
question. In short, we exist to promote knowledge of and interest
|
||||
in computer science as well as allowing those interested in
|
||||
|
|
@ -39,8 +37,8 @@ N2L 3G1
|
|||
computing and brings together many students and professionals from
|
||||
all over the world with an interest in computing. We have an <a
|
||||
href="../office/">office</a> where members get together, a
|
||||
<a href="../office/books.html">library</a> of computer science books
|
||||
available to our members, computer accounts on our various
|
||||
<a href="http://library.csclub.uwaterloo.ca/">library</a> of computer
|
||||
science books available to our members, computer accounts on our various
|
||||
machines and much more. Frequently we host <a
|
||||
href="../events/">events</a> related to computing, including talks,
|
||||
tutorials and demonstrations.
|
||||
|
|
@ -66,12 +64,12 @@ N2L 3G1
|
|||
|
||||
<section title="Can I join?">
|
||||
<p>
|
||||
If you are (or have been) a student, faculty or staff at the
|
||||
<a href="http://www.uwaterloo.ca/">University of Waterloo</a>, you
|
||||
can become a full member of the CSC. Otherwise, you can become an
|
||||
affiliate member, meaning you can't vote or hold executive
|
||||
office. Membership costs a mere $2 (Canadian) a term at the time of
|
||||
this writing, but may change in the future.
|
||||
In compliance with MathSoc regulations and in recognition of the club being
|
||||
primarily targeted at undergraduate students, full membership is open to all
|
||||
Social Members of the Mathematics Society and restricted to the same.
|
||||
Affiliate membership is open to all others. Affiliate members may not vote
|
||||
or hold executive positions. Membership costs a mere $2 (Canadian) a term
|
||||
at the time of this writing, but may change in the future.
|
||||
</p>
|
||||
</section>
|
||||
<footer />
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 3.3 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 3.3 KiB |
BIN
buttons/csc.png
BIN
buttons/csc.png
Binary file not shown.
|
Before Width: | Height: | Size: 1.5 KiB |
BIN
buttons/csc.xcf
BIN
buttons/csc.xcf
Binary file not shown.
BIN
buttons/docs.png
BIN
buttons/docs.png
Binary file not shown.
|
Before Width: | Height: | Size: 3.9 KiB |
BIN
buttons/docs.xcf
BIN
buttons/docs.xcf
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 2.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 208 B |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
BIN
buttons/home.png
BIN
buttons/home.png
Binary file not shown.
|
Before Width: | Height: | Size: 511 B |
Binary file not shown.
|
Before Width: | Height: | Size: 2.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.5 KiB |
BIN
buttons/koha.png
BIN
buttons/koha.png
Binary file not shown.
|
Before Width: | Height: | Size: 2.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.9 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.0 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
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>
|
||||
21
csc.dtd
21
csc.dtd
|
|
@ -1,9 +1,8 @@
|
|||
<!ELEMENT cscpage (biglogo*, menu*, section*, header*, footer*)>
|
||||
<!ELEMENT cscpage (biglogo*, section*, header*, footer*)>
|
||||
<!ATTLIST cscpage
|
||||
title CDATA #REQUIRED>
|
||||
|
||||
<!ELEMENT biglogo EMPTY>
|
||||
<!ELEMENT menu EMPTY>
|
||||
<!ELEMENT section (#PCDATA)>
|
||||
<!ATTLIST section
|
||||
title CDATA #REQUIRED>
|
||||
|
|
@ -39,24 +38,6 @@
|
|||
|
||||
<!ELEMENT members-this-term EMPTY>
|
||||
|
||||
<!ELEMENT booklist (member*)>
|
||||
<!ELEMENT book EMPTY>
|
||||
<!ATTLIST book
|
||||
isbn CDATA #REQUIRED
|
||||
title CDATA #REQUIRED
|
||||
author CDATA #REQUIRED
|
||||
published CDATA ""
|
||||
edition CDATA "">
|
||||
|
||||
<!ELEMENT all-books EMPTY>
|
||||
|
||||
<!ELEMENT menudefs (menuitem*)>
|
||||
<!ELEMENT menuitem EMPTY>
|
||||
<!ATTLIST menuitem
|
||||
icon CDATA #REQUIRED
|
||||
href CDATA #REQUIRED
|
||||
title CDATA #REQUIRED>
|
||||
|
||||
<!ELEMENT directory (diritem*)>
|
||||
<!ATTLIST directory
|
||||
href CDATA ""
|
||||
|
|
|
|||
BIN
csc_welcome.jpg
BIN
csc_welcome.jpg
Binary file not shown.
|
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-----
|
||||
|
|
@ -5,7 +5,7 @@
|
|||
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns:fn="http://www.w3.org/2005/xpath-functions"
|
||||
xmlns:csc="http://www.csclub.uwaterloo.ca/xslt">
|
||||
xmlns:csc="http://csclub.uwaterloo.ca/xslt">
|
||||
|
||||
<xsl:param name="g_date" required="yes" />
|
||||
<xsl:param name="g_time" required="yes" />
|
||||
|
|
@ -36,9 +36,7 @@
|
|||
<xsl:include href="./xsl/functions.xsl" />
|
||||
<xsl:include href="./xsl/common.xsl" />
|
||||
<xsl:include href="./xsl/directory.xsl" />
|
||||
<xsl:include href="./xsl/menu.xsl" />
|
||||
<xsl:include href="./xsl/exec.xsl" />
|
||||
<xsl:include href="./xsl/books.xsl" />
|
||||
<xsl:include href="./xsl/members.xsl" />
|
||||
<xsl:include href="./xsl/events.xsl" />
|
||||
<xsl:include href="./xsl/news.xsl" />
|
||||
|
|
|
|||
65
default.css
65
default.css
|
|
@ -104,12 +104,6 @@ tr.members1 {
|
|||
tr.members2 {
|
||||
background: #cee6ff;
|
||||
}
|
||||
tr.books1 {
|
||||
background: white;
|
||||
}
|
||||
tr.book2 {
|
||||
background: #cee6ff;
|
||||
}
|
||||
|
||||
img {
|
||||
border-width: 0;
|
||||
|
|
@ -129,8 +123,7 @@ div.webcam {
|
|||
}
|
||||
|
||||
div.biglogo {
|
||||
background: url(./csc_welcome.jpg) -20px 25px transparent no-repeat;
|
||||
height: 340px;
|
||||
height: 100px;
|
||||
}
|
||||
div.biglogo div {
|
||||
float: left;
|
||||
|
|
@ -141,6 +134,10 @@ div.biglogo div.uwlogo {
|
|||
div.biglogo div.acmlogo {
|
||||
margin-top: 12px;
|
||||
}
|
||||
div.biglogo div.csclogo {
|
||||
margin-top: 12px;
|
||||
float: right;
|
||||
}
|
||||
|
||||
div.template-header {
|
||||
padding-top: 5px;
|
||||
|
|
@ -165,43 +162,9 @@ div.webtitle div.csclogo {
|
|||
background-color: #215498;
|
||||
}
|
||||
|
||||
div.menubar {
|
||||
background-color: white;
|
||||
padding-top: 12px;
|
||||
margin: 0 auto;
|
||||
text-align: center;
|
||||
height: 75px;
|
||||
vertical-align: middle;
|
||||
font-size: 11px;
|
||||
text-transform: uppercase;
|
||||
}
|
||||
|
||||
div.menuitem {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
text-align: center;
|
||||
float: left;
|
||||
}
|
||||
|
||||
div.menuitem a {
|
||||
display: block;
|
||||
text-align: center;
|
||||
padding: 5px;
|
||||
margin: 0;
|
||||
text-decoration: none;
|
||||
font-weight: 400;
|
||||
font-family: 'Lucida Grande', Sans, Sans-serif;
|
||||
}
|
||||
|
||||
div.menuitem a:hover {
|
||||
font-weight: 700;
|
||||
color: black;
|
||||
background-color: #eee;
|
||||
border: 1px solid #ccc;
|
||||
}
|
||||
|
||||
a.diritem, a.diritem:link, a.diritem:visited, a.diritem:active {
|
||||
font-family: 'Lucida Grande', Sans, Sans-serif;
|
||||
font-size: 14px;
|
||||
border-left: 4px solid #ccc;
|
||||
padding: 0 15px 0 5px;
|
||||
color: blue;
|
||||
|
|
@ -211,16 +174,15 @@ a.diritem:hover {
|
|||
border-left: 4px solid green;
|
||||
}
|
||||
|
||||
a.headdir {
|
||||
a.homedir {
|
||||
font-weight: 700;
|
||||
}
|
||||
|
||||
a.pagetop, a.pagetop:link, a.pagetop:visited, a.pagetop:hover {
|
||||
font-family: 'Lucida Grande',sans, sans-serif;
|
||||
display: block;
|
||||
padding: 0 10px 10px 10px;
|
||||
margin: 10px 0 0 0;
|
||||
border-top: 1px solid #ccc;
|
||||
padding: 5px 10px 5px 10px;
|
||||
border: 1px solid #ccc;
|
||||
background-color: #eee;
|
||||
color: #999;
|
||||
font-size: 9px;
|
||||
|
|
@ -235,9 +197,14 @@ div.footer {
|
|||
color: #666;
|
||||
}
|
||||
|
||||
p.infobox {
|
||||
div.infobox {
|
||||
border: 1px solid #ccc;
|
||||
padding: 5px 10px;
|
||||
padding: 2px 2px;
|
||||
}
|
||||
|
||||
div.infobox p {
|
||||
margin: 5px;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
p.mediafile {
|
||||
|
|
|
|||
|
|
@ -11,6 +11,6 @@ clean:
|
|||
@for i in $(SUBDIRS) ; do cd $$i && ($(MAKE) clean || exit 1) && cd .. ; done
|
||||
rm -f *.html events.ics
|
||||
|
||||
%.html: %.xml $(ROOT)/csc.dtd $(ROOT)/cscweb.xsl $(ROOT)/xsl/*.xsl $(ROOT)/events.xml $(ROOT)/news.xml $(ROOT)/menu.xml $(ROOT)/default.mk directory.xml
|
||||
%.html: %.xml $(ROOT)/csc.dtd $(ROOT)/cscweb.xsl $(ROOT)/xsl/*.xsl $(ROOT)/events.xml $(ROOT)/news.xml $(ROOT)/default.mk directory.xml
|
||||
java -classpath $(CLASSPATH) net.sf.saxon.Transform -o $@ $< $(ROOT)/cscweb.xsl $(XSLTARGS)
|
||||
sed -i 's| xmlns=""||' $@
|
||||
|
|
|
|||
|
|
@ -2,5 +2,12 @@
|
|||
|
||||
<!DOCTYPE directory SYSTEM "csc.dtd">
|
||||
|
||||
<directory title="Index">
|
||||
<directory>
|
||||
<diritem title="About" href="about/" />
|
||||
<diritem title="Services" href="services/" />
|
||||
<diritem title="Office" href="office/" />
|
||||
<diritem title="Events" href="events/" />
|
||||
<diritem title="Media" href="media/" />
|
||||
<diritem title="Wiki" href="http://wiki.csclub.uwaterloo.ca/" />
|
||||
<diritem title="Webmail" href="https://mail.csclub.uwaterloo.ca/" />
|
||||
</directory>
|
||||
|
|
|
|||
|
|
@ -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>
|
||||
|
||||
<para><prompt>peri# </prompt><userinput>echo username
|
||||
|/root/dead-accounts/unexpire.pl</userinput> If this worked, it should
|
||||
spit back the username.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Extract home directory onto peri</para>
|
||||
|
||||
<para>extract home directory onto peri mount "Expired /u" on
|
||||
sugar (or wherever) copy /$mntpoint/username.tar to somewhere
|
||||
accessible to root@peri</para>
|
||||
|
||||
<para>Note: the home directories are not compressed on the CD,
|
||||
remember this when 'cp' is telling you 'username.tgz: no
|
||||
such file or directory'. tar (below) doesn't need 'z'
|
||||
either. <prompt>peri# </prompt><userinput>tar xf /path/to/username.tar
|
||||
-C /u</userinput></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Restore mail onto peri </para>
|
||||
|
||||
<para><prompt>peri$ </prompt><userinput>grep username
|
||||
/root/dead-accounts/unreadable-accounts</userinput> if the username is
|
||||
there, the mbox is on "Expired mail 2" otherwise, the mbox is
|
||||
on "Expired mail" mount appropriate CD cd to a temporary
|
||||
directory (*not* /var/mail) extract mbox from archive -- on the
|
||||
"Expired mail", this will take a while -- just hit ^C after
|
||||
you see the username printed and you're happy tar has moved on to
|
||||
other files.</para>
|
||||
|
||||
<para>(I say 'sugar', but really any machine with a CD
|
||||
drive...) <prompt>sugar$ </prompt><userinput>tar jxvf
|
||||
/$mntpoint/mail_tar.bz2 username </userinput> (hmm.. I don't
|
||||
remember what the tarball is called on Expired2, maybe the same thing,
|
||||
maybe different, but I'm pretty sure this is the filename for
|
||||
Expired1. Besides, there's only one file on the CD, so just
|
||||
tab-complete the damn thing :) (probably scp username root@peri: or
|
||||
something here) restore mail, appending any mail received since backup
|
||||
was made, and preserving permissions on the file. (Note: this
|
||||
doesn't take into account locks -- i.e., stuff might get screwed
|
||||
if the account receives mail while one of the below cats is running. A
|
||||
message received between the cats simply gets lost.)</para>
|
||||
|
||||
<para> The following commands should also work from another machine if
|
||||
the account was on "Expired mail" (i.e., was not in
|
||||
``unreadable-accounts''). But doing it on peri will always</para>
|
||||
|
||||
<para><prompt>peri#</prompt><userinput>cat /var/mail/username
|
||||
>>username</userinput></para>
|
||||
|
||||
<para><prompt>peri#</prompt><userinput>cat username
|
||||
>/var/mail/username</userinput></para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
|
@ -1,208 +0,0 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<chapter>
|
||||
<title>Vice President</title>
|
||||
|
||||
<para>This chapter covers various useful notes for the CSC vice president,
|
||||
ranging from who to call for room bookings to how to promote your events.</para>
|
||||
|
||||
<sect1>
|
||||
<title>Planning events</title>
|
||||
|
||||
<para>So, you're the CSC Vice President and you want to (hopefully)
|
||||
have the CSC host some really cool events this term. This chapter should
|
||||
help you get started with that.</para>
|
||||
|
||||
<para>For starters, the most important thing to remember is this:
|
||||
<emphasis>plan your events early!</emphasis>. I recommend about 2 to 3
|
||||
weeks in advance. This rough timeline should help:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>2-3 weeks in advance: Get a title and abstract for the event
|
||||
from the speaker as well as a date and time.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>2 weeks in advance: Book the room and any necessary equipment
|
||||
(projectors etc). Make posters for the event. Make initial
|
||||
announcements on Usenet and possibly by e-mail.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>2 Days in advance: E-mail <email>credmond@uwaterloo.ca</email>
|
||||
to get the event into the Daily Bulletin. Include a short
|
||||
(one-paragraph) description.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Day of the event: Try to be at the event, or find someone who
|
||||
will be to make sure things go smoothly. Remember to get the projector
|
||||
if necessary. If there are people in the room you booked, ask them to
|
||||
leave politely. Mention that you have the room booked. Get
|
||||
refreshments to the room as necessary. Introduce the speaker.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>After the event: Thank the speaker in front of the audience and
|
||||
applaud. Offer to take the speaker out for dinner. Clean up the room
|
||||
and return any loaned equipment. Write him or her a cheque for any
|
||||
expenses if necessary. For out-of-town speakers a small gift might be
|
||||
nice.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>The rest of this chapter will outline various tips that should be
|
||||
useful when running events and suggest some events that you might want to
|
||||
run.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Getting ideas and speakers for events</title>
|
||||
|
||||
<para>Obviously you will have to start your planning by coming up with
|
||||
an event. Here are some types of events you might want to hold:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Talks held by CSC members. Ask around, there are probably a
|
||||
few members who have interesting things to give talks on. In the
|
||||
past CSC members have given talks about programming languages they
|
||||
like, Operating Systems, research projects, etc.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Talks held by Faculty: Simply ask your CS profs, or get other
|
||||
exec to ask their profs or interesting faculty. Approaching faculty
|
||||
in person might get you better results than e-mailing, but be sure
|
||||
to follow up with an e-mail so that you have something written to
|
||||
remind them.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Out-of-town speakers. The <ulink
|
||||
url="http://www.acm.org/chapters/stu/">ACM student chapter website</ulink>
|
||||
has a section called "Lectureship series" where you can find
|
||||
information on getting an ACM Distinguished Lecturer. You can also
|
||||
simply approach interesting people (in Academia, Industry or the
|
||||
Free Software scene) by e-mail and ask them if they'd like to
|
||||
come and give a talk (or a few talks). Don't be afraid to ask
|
||||
high-profile people, the worst you can get is a "no." Be
|
||||
sure to have the treasurer budget money to pay for the guest
|
||||
speaker's expenses. If you can, try to pay for travel expenses
|
||||
(unless the speaker offers), but at the very least arrange for meals
|
||||
and accomodation as well as transport from the airport or bus/train
|
||||
station if necessary.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Special events. In the past we've had an event called
|
||||
"Pints with Profs" where we invited the CS faculty (<email>cs-faculty@cs.uwaterloo.ca</email>)
|
||||
and any interested CS students to come out to a pub. The Bomber is a
|
||||
convenient location but we've found their catering to be
|
||||
expensive. Weaver's Arms (in WCRI) might be a good alternative.
|
||||
Be sure to budget this with Mathsoc, so you can pay for free food.
|
||||
Try to get both meat and vegetarian alternatives (e.g. Wings and
|
||||
Veggie Platters). Make sure you publicise this event very well, and
|
||||
don't hesitate to ask the profs to announce it in class (giving
|
||||
them overheads might be a good idea). This is definitely an event
|
||||
you should try to hold. If you can think of any other special
|
||||
events, go right ahead, be creative! Be sure to add them here.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Tutorials. Usually we hold a few UNIX tutorials at the
|
||||
beginning of the term. These are quite popular and you can get
|
||||
Faculty (especiall the first and second-year CS profs) to announce
|
||||
them in class. Be sure to book a lab. If there are more than one or
|
||||
two other people in the lab, politely ask them to leave - in our
|
||||
experience, asking such groups to be quiet doesn't usually work
|
||||
very well. Aside from UNIX you could have tutorials for LaTeX, some
|
||||
programming language, some programming problem (e.g. "Writing a
|
||||
raytracer") or anything you think would be useful for people to
|
||||
learn. </para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Contests. Programming contests can be a lot of fun and will
|
||||
certainly raise interest in the club. Try to get nice prizes so that
|
||||
you can attract a large group of contestants. Be sure to have the
|
||||
rules and the environment set up early on. Game solving contests are
|
||||
a good idea (this can range from writing programs to play
|
||||
rock-paper-scissors to having programs compete at playing chess),
|
||||
demo programming contests can also be fun or you might go for
|
||||
something more useful. It's up to you - be creative!</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Anything else you can think of. Be imaginative and ask for
|
||||
suggestions. The ACM website also has some good suggestions for
|
||||
events. Don't limit yourself to computer-related events - a
|
||||
volleyball match against the Pure Math Club might be fun.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Announcing the event: Posters and Posts</title>
|
||||
|
||||
<para>Once you have the abstract and the room booked you should get the
|
||||
word out. For starters you should send an announcement to the uw.csc
|
||||
newsgroup and possibly to the members by e-mail (try to reserve the
|
||||
latter for special events, although an update with upcoming events every
|
||||
now and then might be a good idea).</para>
|
||||
|
||||
<para>You'll also want to make printed posters. Simon Law made a
|
||||
<filename>cscposter.cls</filename> file for LaTeX which can be used to
|
||||
generate nice-looking posters in letter format. Try to not have too much
|
||||
text on the posters so that they grab more attention. Getting posters
|
||||
out earlier rather than later is definitely beneficial. To actually
|
||||
distribute posters you should use several methods:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Put up the posters on the CSC boards. There are 3 boards: a
|
||||
small one right by the door of MC3036, a large one in the 3rd floor
|
||||
hallway of the MC and another large one on the second floor of the
|
||||
MC (directly below the third floor hallway).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Give 6 posters to Mathsoc. Just drop by 6 posters in the
|
||||
Mathsoc office and they'll put them up around the MC and DC.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Make use of the FEDS poster run. FEDS offers a (reasonably
|
||||
cheap) poster run where they will distribute many posters around
|
||||
campus. Check the <ulink
|
||||
url="http://www.feds.uwaterloo.ca/services/marketing.html">FEDS
|
||||
marketing website</ulink> for pricing and information on how to use
|
||||
it. While we aren't a FEDS club, we are part of MathSoc, so try
|
||||
to get the "student society" price. Also, make sure you
|
||||
budget for this from Mathsoc, you can probably get funds from them
|
||||
to use this.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>There are other ways to get people to know about the event. If the
|
||||
event is relevant to classes, try to convince profs to announce it in
|
||||
class (giving them an overhead with the details is a good idea). Also,
|
||||
have the event announced in the Daily Bulletin (a daily update on the UW
|
||||
website about what's happening on campus). To do so, e-mail Chris
|
||||
Redmond (<email>credmond@uwaterloo.ca</email>).</para>
|
||||
|
||||
<para>Word of mouth is another important channel. Tell others in the CSC
|
||||
(both executives and members) to tell their friends about events. Tell
|
||||
your own friends and classmates about events that they might find
|
||||
interesting. Word of mouth is often how events get most of their
|
||||
publicity.</para>
|
||||
|
||||
<para>Lastly, you'll want to add the event to the website. Contact
|
||||
the CSC webmaster (or if there is none, the sysadmin) to have him or her
|
||||
do that for you, or find out how to do it yourself. This way others can
|
||||
check for events on the website, and you can also conveniently point
|
||||
people there if they ask, "What events is the CSC offering this
|
||||
term?"</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
|
@ -1,23 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Documents">
|
||||
|
||||
<header />
|
||||
<section title="CSC Documents">
|
||||
<p>
|
||||
Here you'll find all kinds of documents pertaining to the CSC or
|
||||
possibly useful to CSC members. So far we have:
|
||||
</p>
|
||||
<ul>
|
||||
<li><a href="official.html">Official documents</a></li>
|
||||
<li><a href="website.html">Documentation about the website</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>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<footer />
|
||||
</cscpage>
|
||||
Binary file not shown.
|
|
@ -1,19 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Official documents">
|
||||
<header />
|
||||
<section title="Official CSC documents">
|
||||
<ul>
|
||||
<li><a href="constitution.html">Our constitution</a></li>
|
||||
<li><a href="machine_usage.html">The machine usage policy</a>
|
||||
(see also the <a href="machine_usage_summary.html">summary</a>)</li>
|
||||
</ul>
|
||||
<p>You may also be interested in:</p>
|
||||
<ul>
|
||||
<li><a href="../about/members.html">Our membership list</a></li>
|
||||
</ul>
|
||||
</section>
|
||||
<footer/>
|
||||
</cscpage>
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Old CSC Procedures manual">
|
||||
<header />
|
||||
<section title="The old CSC Procedures Manual">
|
||||
<p>This is an outdated procedures manual written by previous
|
||||
exec. Useful information from this should get moved into the <a
|
||||
href="execmanual.html">new exec manual</a>.</p>
|
||||
<p>The procedures manual is written using LaTeX and is available
|
||||
<a href="procedure/procedure.pdf">in PDF format</a>. The
|
||||
<a href="procedure/procedure.tex">LaTeX source</a> is also on-line.</p>
|
||||
</section>
|
||||
<footer/>
|
||||
</cscpage>
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
*.html
|
||||
*.fot
|
||||
*.out
|
||||
*.fo
|
||||
*.pdf
|
||||
*.log
|
||||
*.aux
|
||||
*.ps
|
||||
*.dvi
|
||||
*.toc
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
STYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl
|
||||
FOSTYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/fo/docbook.xsl
|
||||
XSLTPROC = xsltproc
|
||||
XMLS = $(wildcard *.xml)
|
||||
HTMLS = $(XMLS:.xml=.html)
|
||||
|
||||
#all: book.html book.tex book.pdf
|
||||
all: procedure.pdf
|
||||
|
||||
%.pdf: %.tex
|
||||
pdflatex $<
|
||||
|
||||
clean-recurse: clean
|
||||
|
||||
clean:
|
||||
rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.toc
|
||||
|
||||
#book.html: $(XMLS)
|
||||
|
||||
#%.html: %.xml
|
||||
# $(XSLTPROC) $(STYLESHEET) $< > $@
|
||||
|
||||
#%.fo: %.xml
|
||||
# $(XSLTPROC) $(FOSTYLESHEET) $< > $@
|
||||
|
||||
#%.tex: %.xml
|
||||
# openjade -t tex -d /usr/share/sgml/docbook/stylesheet/dsssl/modular/print/docbook.dsl $<
|
||||
|
||||
#%.dvi: %.tex
|
||||
# jadetex $<
|
||||
|
||||
#%.pdf: %.tex
|
||||
# pdfjadetex $<
|
||||
|
||||
#%.ps: %.dvi
|
||||
# dvips -o $@ $<
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,48 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="The CSC Website">
|
||||
<header/>
|
||||
<section title="Developing the website">
|
||||
<p>
|
||||
The CSC website is currently being revamped, what you are seeing
|
||||
is the new design and structure of the site. If you would like
|
||||
to help out you should probably e-mail the
|
||||
<a href="mailto:www@csclub.uwaterloo.ca">webmaster</a>, and they'll
|
||||
let you know how to get started.
|
||||
</p>
|
||||
<p>
|
||||
This website is completely generated from XML sources using an
|
||||
XSLT (XML Stylesheet Language Transformation), which is
|
||||
basically a simple XML programming language specifically built
|
||||
for this kind of thing. This allows complete separation of form
|
||||
and content as well as automating a number of tasks (such as
|
||||
generating the <a href="../events/">events pages</a>).
|
||||
</p>
|
||||
</section>
|
||||
<section title="Adding to the website">
|
||||
<p>See the <a href="editing-howto.html">Editing Howto</a> for
|
||||
information on editing the website</p>
|
||||
</section>
|
||||
<section title="Links">
|
||||
<p>
|
||||
I have provided some helpful links regarding XSLT and XML below.
|
||||
</p>
|
||||
<ul>
|
||||
<li><a href="http://www.w3.org/TR/2000/REC-xml-20001006">XML 1.0
|
||||
specification</a></li>
|
||||
<li><a href="http://www.w3.org/TR/xslt">XSLT
|
||||
specification</a></li>
|
||||
<li><a href="http://www.w3.org/TR/xpath">XPath
|
||||
specification</a></li>
|
||||
<li><a href="http://www.garshol.priv.no/download/xmltools/">Free
|
||||
XML tools and software</a></li>
|
||||
<li><a href="http://www.dpawson.co.uk/xsl/xslfaq.html">XSL
|
||||
Frequently Asked Questions</a></li>
|
||||
<li><a href="http://xmlsoft.org/XSLT/">libxslt</a>, which this
|
||||
site uses extensively.</li>
|
||||
</ul>
|
||||
</section>
|
||||
<footer/>
|
||||
</cscpage>
|
||||
120
events.xml
120
events.xml
|
|
@ -34,7 +34,7 @@
|
|||
the benefit of the public--then we must make changes in the other
|
||||
direction.
|
||||
</p><p>
|
||||
Ths CSC would like to thank MEF and Mathsoc for funding this talk.
|
||||
The CSC would like to thank MEF and Mathsoc for funding this talk.
|
||||
</p><p>
|
||||
<a href="http://www.fsf.org/events/waterloo20070706">The Freedom Software Foundation's description</a><br />
|
||||
<a href="http://www.defectivebydesign.org">FSF's anti-DRM campaign</a><br />
|
||||
|
|
@ -164,7 +164,7 @@
|
|||
|
||||
<eventitem date="2007-03-29" time="4:30 PM"
|
||||
room="MC 1056" title="All The Code">
|
||||
<short>A demo/intrdocution to a new source code search engine. A talk by Holden Karau</short>
|
||||
<short>A demo/introduction to a new source code search engine. A talk by Holden Karau</short>
|
||||
<abstract>
|
||||
<p>
|
||||
Source code search engines are a relatively new phenomenon . The general idea of most source code search engines is helping programmers find
|
||||
|
|
@ -270,7 +270,7 @@ recognizer.
|
|||
<abstract>
|
||||
<p>
|
||||
A common misconception amongst software developers is that top quality software
|
||||
encompasses certains platforms, is driven by a particular new piece of
|
||||
encompasses certain platforms, is driven by a particular new piece of
|
||||
technology, or relies solely on a particular programming language. However as
|
||||
developers we tend to miss the less hyped issues and techniques involved in
|
||||
writing world class software. These techniques are universal to all
|
||||
|
|
@ -296,7 +296,7 @@ World Class Software
|
|||
A discussion of software start-ups founded by UW students and what they did
|
||||
that helped them grow and what failed to help. In order to share the most
|
||||
insights and guard the confidences of the individuals involved, none of the
|
||||
companies will be identifed.
|
||||
companies will be identified.
|
||||
</p>
|
||||
</abstract>
|
||||
</eventitem>
|
||||
|
|
@ -371,7 +371,7 @@ promise multi-core holds.
|
|||
-->
|
||||
|
||||
<!-- Fall 2006 -->
|
||||
<!-- Nothing happend :( -->
|
||||
<!-- Nothing happened :( -->
|
||||
|
||||
<!-- Spring 2006 -->
|
||||
|
||||
|
|
@ -550,9 +550,9 @@ together, solder, and eat free food (probably pizza).
|
|||
<p>
|
||||
The venue will include:</p>
|
||||
<p><ul>
|
||||
<li><p>Computer usage agreement discussion (Holden has some changes he'd like to propse)</p></li>
|
||||
<li><p>Web site - Juti is redisigning the web site (you can see <a href="beta/">a beta here</a> - ideas are welcome.</p></li>
|
||||
<li><p>Frosh linux cd's that could be put in frosh math faculty kits.</p></li>
|
||||
<li><p>Computer usage agreement discussion (Holden has some changes he'd like to propose)</p></li>
|
||||
<li><p>Web site - Juti is redesigning the web site (you can see <a href="beta/">a beta here</a> - ideas are welcome.</p></li>
|
||||
<li><p>Frosh Linux cd's that could be put in frosh math faculty kits.</p></li>
|
||||
<li><p>VoIP "not phone services" ideas.</p></li>
|
||||
<li><p>Ideas for talks (people, topics, etc...). We requested Steve Jobs and Steve Balmer, so no idea is too crazy.</p></li>
|
||||
<li><p>Ideas for books.</p></li>
|
||||
|
|
@ -585,12 +585,12 @@ A video of the talk is available for download in our <a href="media/">media</a>
|
|||
<abstract>
|
||||
<p>
|
||||
Have you heard of our famous Unix 101 and Unix 102 tutorials. We've decided to try
|
||||
and put them on the web. This sunday we will be doing a first take.
|
||||
and put them on the web. This Sunday we will be doing a first take.
|
||||
At the same time, we're going to be looking at adding new material
|
||||
that we haven't covered in the past. </p>
|
||||
<p>
|
||||
Why should you come out? Not only will you get to hang out with a wonderful group of people,
|
||||
you can help impart your knowledge to the world. Don't know anything about unix? Thats cool too,
|
||||
you can help impart your knowledge to the world. Don't know anything about Unix? That's cool too,
|
||||
we need people to make sure its easy to follow along and hopefully keep us from leaving something
|
||||
out by mistake.
|
||||
</p>
|
||||
|
|
@ -602,8 +602,8 @@ A video of the talk is available for download in our <a href="media/">media</a>
|
|||
<abstract>
|
||||
<p>
|
||||
We don't know Video 4 Linux, but increasingly people are wanting to do interesting stuff with our webcam which
|
||||
could benefit from a better understanding of Video 4 Linux. So, this saturday a number of us will be trying to learn
|
||||
as much as possible about Video 4 Linux and doing wierd things with webcam(s).
|
||||
could benefit from a better understanding of Video 4 Linux. So, this Saturday a number of us will be trying to learn
|
||||
as much as possible about Video 4 Linux and doing weird things with webcam(s).
|
||||
</p>
|
||||
</abstract>
|
||||
</eventitem>
|
||||
|
|
@ -665,10 +665,10 @@ Elections">
|
|||
|
||||
<eventitem date="2005-11-29" time="5:30 PM"
|
||||
room="TBA" title="Programming Contest">
|
||||
<short>Come out, program, and win shiney things!</short>
|
||||
<short>Come out, program, and win shiny things!</short>
|
||||
<abstract>
|
||||
<p>
|
||||
The Computer Science club is holding a programming contest open to all students on tuesday the 29th of november at 5:30PM. C++,C,Perl,Scheme* are allowed. Prizes totalling in value of $75 will be distributed.
|
||||
The Computer Science club is holding a programming contest open to all students on Tuesday the 29th of November at 5:30PM. C++,C,Perl,Scheme* are allowed. Prizes totalling in value of $75 will be distributed.
|
||||
|
||||
</p>
|
||||
|
||||
|
|
@ -796,8 +796,10 @@ and optional. After some remarks about constraints and opportunities in
|
|||
the near future, I'll open the floor to discussion, and hope to hear
|
||||
some candid comments about the state of CS at UW and how it might be
|
||||
improved.
|
||||
</p><br></br>
|
||||
About the speaker:<br></br>
|
||||
</p>
|
||||
<p>
|
||||
About the speaker:
|
||||
</p>
|
||||
<p>
|
||||
Prabhakar Ragde is a Professor in the School of Computer Science at UW.
|
||||
He was Associate Chair for Curricula during the period that saw the
|
||||
|
|
@ -894,7 +896,7 @@ Elections">
|
|||
<eventitem date="2004-12-08" time="4:30 PM" room="Mongolian Grill"
|
||||
title="CTRL-D">
|
||||
<short> This semesters CTRL-D (or the club that really likes
|
||||
dinner) is going to be at mongolian grill. Be there or be square</short>
|
||||
dinner) is going to be at Mongolian grill. Be there or be square</short>
|
||||
<abstract>
|
||||
<p>
|
||||
Come to the end of term CTRL-D (club that really likes dinner) meeting.
|
||||
|
|
@ -991,7 +993,7 @@ regardless of whatever's in your path? Then you should come out to CSC Lemmings
|
|||
<short>CSC Programming Contest</short>
|
||||
<abstract>
|
||||
<p>
|
||||
The Computer Science Clib will be hosting a programming competition.
|
||||
The Computer Science Club will be hosting a programming competition.
|
||||
You have the entire afternoon to design and implement an AI for a simple
|
||||
game. The competition will run until 5pm.
|
||||
</p>
|
||||
|
|
@ -1676,7 +1678,7 @@ pizza!</p>
|
|||
<p>Nominations will be accepted until Tuesday, September 16 at 4:30 PM.</p>
|
||||
|
||||
<p>Additionally, a Sysadmin will be appointed after the elections. If you
|
||||
like working with unix systems and have experience setting up and
|
||||
like working with Unix systems and have experience setting up and
|
||||
maintaining them, go for it!</p>
|
||||
|
||||
<p>I hope that lots of people will show up; hopefully we'll have a great
|
||||
|
|
@ -1761,7 +1763,7 @@ wireless microphone is dependent on whether MFCF is
|
|||
willing to host it.
|
||||
-Funding for casters was denied.
|
||||
-Shopping for the Video card.
|
||||
-Expecting it after auguest (Stefanus shopping for it.)
|
||||
-Expecting it after August (Stefanus shopping for it.)
|
||||
-Will have to hear back regarding the microphone, best to
|
||||
delay that now, discuss it with MEF.
|
||||
-Better to do it this term, so it doesn't get lost.
|
||||
|
|
@ -1799,9 +1801,9 @@ From last meeting:
|
|||
ACTION ITEM: Biggs and Cass
|
||||
-get labelmaker tape, masking tape
|
||||
whiteboard makers, coloured paper, CD sleeves
|
||||
-keep reciepts for CSC office expenses.
|
||||
-keep receipts for CSC office expenses.
|
||||
|
||||
How is the progess on allowing executives and voters to be non-math
|
||||
How is the progress on allowing executives and voters to be non-math
|
||||
members?
|
||||
-The vote is coming up Monday.
|
||||
-Proposal: Anyone who is a paying member can be a member
|
||||
|
|
@ -1809,7 +1811,7 @@ members?
|
|||
Pay MathSoc fees, or
|
||||
Get your faculty society to recognize CSC as a club.
|
||||
|
||||
Stefanus wanted to mention that we shoudl talk to Yolanda,
|
||||
Stefanus wanted to mention that we should talk to Yolanda,
|
||||
Craig or Louie about a EYT event for frosh week.
|
||||
-Organized by Meg.
|
||||
-Sugar Mountain trying to hook all the Frosh
|
||||
|
|
@ -1909,7 +1911,7 @@ ACTION ITEM: Mike
|
|||
Recently a few high-level languages for shader programming have become
|
||||
available. Sh, a result of research at UW, is one such language. It
|
||||
allows programming powerful shaders in simple and intuitive ways. Sh
|
||||
is particularily interesting because of the way it is
|
||||
is particularly interesting because of the way it is
|
||||
implemented. Instead of coming up with a language grammar and writing
|
||||
a full-fledged compiler, Sh is implemented as a C++ library, and
|
||||
shader programs are effectively written in C++. The actual compilation
|
||||
|
|
@ -1980,7 +1982,7 @@ Feedback from Completed Events
|
|||
--NO CS Profs
|
||||
--Only 1 E& CE prof
|
||||
--Only 2 Math profs
|
||||
--Jim will harrass the profs at the School of CS Council meeting.
|
||||
--Jim will harass the profs at the School of CS Council meeting.
|
||||
|
||||
We're starting to fall behind in planning
|
||||
|
||||
|
|
@ -2021,16 +2023,16 @@ Feedback from Completed Events
|
|||
|
||||
Simon got money from Engsoc
|
||||
|
||||
Cass meeds coloured paper (CSC is out)
|
||||
Cass needs coloured paper (CSC is out)
|
||||
|
||||
ACTION ITEM: Cass and Mark
|
||||
--get labelmaker tape, masking tape,
|
||||
whiteboard makers, coloured paper
|
||||
--keep reciepts for CSC office expenses
|
||||
--keep receipts for CSC office expenses
|
||||
|
||||
NOTICE: Mike is now Imapd
|
||||
|
||||
Simon distibuted budget list
|
||||
Simon distributed budget list
|
||||
Mark got the money from Mathsoc for last budget, deposited it.
|
||||
|
||||
ACTION ITEM:Mark
|
||||
|
|
@ -2408,7 +2410,7 @@ style, go for it!
|
|||
<p>Nominations will be accepted until Tuesday, May 13 at 4:30 PM.</p>
|
||||
|
||||
<p>Additionally, a Sysadmin will be appointed after the elections. If you
|
||||
like working with unix systems and have experience setting up and
|
||||
like working with Unix systems and have experience setting up and
|
||||
maintaining them, go for it!</p>
|
||||
|
||||
<p>I hope that lots of people will show up; hopefully we'll have a great
|
||||
|
|
@ -2436,7 +2438,7 @@ members can vote, but anyone can become a member.</p>
|
|||
|
||||
<p>This is the first in a series of seminars that cover the use of the
|
||||
UNIX Operating System. UNIX is used in a variety of applications, both
|
||||
in academia and industy. We will provide you with hands-on experience
|
||||
in academia and industry. We will provide you with hands-on experience
|
||||
with the Math Faculty's UNIX environment in this seminar.</p>
|
||||
|
||||
<p>Topics that will be discussed include:</p>
|
||||
|
|
@ -2498,7 +2500,7 @@ me also.</p>
|
|||
|
||||
<p>The positions open are:</p>
|
||||
|
||||
<p><b>President</b> -- appoints all commitees of the club, calls and presides at all
|
||||
<p><b>President</b> -- appoints all committees of the club, calls and presides at all
|
||||
meetings of the club and audits the club's financial records. Really, this
|
||||
is the person in charge.</p>
|
||||
|
||||
|
|
@ -2600,7 +2602,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
typeset in L<sup><small>A</small></sup>T<small>E</small>X to great
|
||||
effect. In this session, I will provide examples on how to typeset
|
||||
tables, figures, and references. You will also learn how to make
|
||||
tables of contents, bibliographics, and how to create footnotes.</p>
|
||||
tables of contents, bibliographies, and how to create footnotes.</p>
|
||||
|
||||
<p> I will also examine various packages of
|
||||
L<sup><small>A</small></sup>T<small>E</small>X that can help you
|
||||
|
|
@ -2635,16 +2637,16 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
<p>Before the GNU project ever existed, before the phrase
|
||||
"Free Software" was ever coined, students and researchers
|
||||
at the University of California, Berkeley were already
|
||||
practising it. They had acquired the source cdoe to a
|
||||
practising it. They had acquired the source code to a
|
||||
little-known operating system developed at AT&T
|
||||
Bell Laboratories, and were creating improvments at a
|
||||
Bell Laboratories, and were creating improvements at a
|
||||
ferocious rate.</p>
|
||||
|
||||
<p>These improvements were sent back to Bell Labs, and
|
||||
shared to other Universities. Each of them were licensed
|
||||
under what is now known as the "Original BSD license". Find
|
||||
out what this license means, its implications, and what are
|
||||
its decendents by attending this short talk.</p>
|
||||
its descendents by attending this short talk.</p>
|
||||
|
||||
</abstract>
|
||||
</eventitem>
|
||||
|
|
@ -2664,7 +2666,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
<div style="text-align:right">--- Excerpt from the GNU GPL</div>
|
||||
</blockquote></div>
|
||||
|
||||
<p> The GNU General Public License is one of the most influencial
|
||||
<p> The GNU General Public License is one of the most influential
|
||||
software licenses in this day. Written by Richard Stallman for the
|
||||
GNU Project, it is used by software developers around the world to
|
||||
protect their work.</p>
|
||||
|
|
@ -2693,7 +2695,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
languages for semantically describing a document.</p>
|
||||
|
||||
<p>This talk will describe how to generate correct XML documents,
|
||||
and auxillary technologies that work with XML.</p>
|
||||
and auxiliary technologies that work with XML.</p>
|
||||
|
||||
</abstract>
|
||||
</eventitem>
|
||||
|
|
@ -2724,7 +2726,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
|
||||
<p>A lot of claims have been made lately about the intelligence of
|
||||
computers. Some researchers say that computers will eventually attain
|
||||
super-human intelligence. Others call thse claims... um, poppycock.
|
||||
super-human intelligence. Others call these claims... um, poppycock.
|
||||
Oddly enough, in the search for the truth of the matter, both camps
|
||||
have overlooked an obvious strategy: interviewing a computer and asking
|
||||
her opinion.</p>
|
||||
|
|
@ -2951,7 +2953,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
<h3>Need something to do between assignments/beers?</h3>
|
||||
<p>
|
||||
Did you know that your undergrad account at Waterloo gives you
|
||||
access tothe world's largest computer network? With thousands
|
||||
access to the world's largest computer network? With thousands
|
||||
of discussion groups, gigabytes of files to download, multimedia
|
||||
information browsers, even on-line entertainment?
|
||||
</p>
|
||||
|
|
@ -2973,11 +2975,11 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
<abstract>
|
||||
<h3>From the Minimax Theorem, through Alpha-Beta, and beyond...</h3>
|
||||
<p>
|
||||
This will be a descussion of the pitfalls of using mathematics and
|
||||
This will be a discussion of the pitfalls of using mathematics and
|
||||
algorithms to play classical board games. Thorough descriptions
|
||||
shall be presented of the simple techniques used as the building
|
||||
blocks that make all modern computer game players. I will use
|
||||
tic-tac-toe as a control for my arguements. Other games such as
|
||||
tic-tac-toe as a control for my arguments. Other games such as
|
||||
Chess, Othello and Go shall be the be a greater measure of progress;
|
||||
and more importantly the targets of our dreams.
|
||||
</p>
|
||||
|
|
@ -3035,18 +3037,18 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
any program's life-cycle. Far from an exact science, it's more
|
||||
of an art ... and close to some kind of dark magic. Cryptic
|
||||
error messages, lousy error checking, and icky things like
|
||||
implicit casts can make it nearly impossible toknow what's
|
||||
implicit casts can make it nearly impossible to know what's
|
||||
going on inside your program.
|
||||
</p>
|
||||
<p>
|
||||
Several tools are available to help automate your
|
||||
debuggin. GDB and Purify are among the most powerful
|
||||
debugging. GDB and Purify are among the most powerful
|
||||
debugging tools available in a UNIX environment. GDB is an
|
||||
interactive debugger, allowing you to `step' through
|
||||
aprogram, examine function calls, variable contents, stack
|
||||
a program, examine function calls, variable contents, stack
|
||||
traces and let you look at the state of a program after it
|
||||
crashes. Purify is a commercial program designed to help find
|
||||
and remove memory leaks from programs written inlanguages
|
||||
and remove memory leaks from programs written in languages
|
||||
without automatic garbage collection.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -3096,8 +3098,8 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
<p> This talk will use partial orders, lattice theory, and, if
|
||||
time permits, the Galois connection as carriers to illustrate
|
||||
the use of calculi in mathematics. We hope to show the brevity
|
||||
of many calculations (in order tofight the superstition that
|
||||
formal proofs are necessarily unpractically long), and the
|
||||
of many calculations (in order to fight the superstition that
|
||||
formal proofs are necessarily impractically long), and the
|
||||
strong heuristic guidance that is available for their
|
||||
design. </p>
|
||||
|
||||
|
|
@ -3187,7 +3189,7 @@ Remember: Monday, January 13, 6:00 PM, MC3001/Comfy Lounge.</p>
|
|||
|
||||
<p>This talk will feature an exclusive look at the architecture
|
||||
behind the new J2EE portal: theserverside.com. Join Floyd
|
||||
Marinescu in a walk-through ofthe back-end of the portal,
|
||||
Marinescu in a walk-through of the back-end of the portal,
|
||||
while learning about J2EE and its real world patterns,
|
||||
applications, problems and benefits.</p>
|
||||
</abstract>
|
||||
|
|
@ -3341,7 +3343,7 @@ University of Waterloo<br />
|
|||
<dt>CD Burner</dt>
|
||||
|
||||
<dd>
|
||||
<p>For doing linux burns. It was allocated money on the budget
|
||||
<p>For doing Linux burns. It was allocated money on the budget
|
||||
request - about $300. We should be able to get a decent 12x
|
||||
burner with that (8x rewrite).</p>
|
||||
<p>The obvious things to sell are Linux Distros and BSD variants.
|
||||
|
|
@ -3360,7 +3362,7 @@ University of Waterloo<br />
|
|||
<p>We already put a bit of work into planning the Othello contest
|
||||
before I read Mike's post. I still think it's viable. I've got
|
||||
at least 2 people interested in writing entries for it. This
|
||||
will be talked about more on monday. Hopefully, Rory and I will
|
||||
will be talked about more on Monday. Hopefully, Rory and I will
|
||||
be able to present a basic outline of how the contest is going
|
||||
to be run at that time.</p>
|
||||
</dd>
|
||||
|
|
@ -3551,7 +3553,7 @@ href="ja2morri@uwaterloo.ca">James Morrison</a>.</p>
|
|||
<abstract>
|
||||
This is the first in a series of seminars that cover the use of
|
||||
the UNIX Operating System. UNIX is used in a variety of
|
||||
applications, both in academia and industy. We will be covering
|
||||
applications, both in academia and industry. We will be covering
|
||||
the basics of the UNIX environment, as well as the use of PINE, an
|
||||
electronic mail and news reader.
|
||||
</abstract>
|
||||
|
|
@ -3610,10 +3612,10 @@ href="ja2morri@uwaterloo.ca">James Morrison</a>.</p>
|
|||
<eventitem date="2002-03-01" time="5:00 PM" room="MC4060"
|
||||
title="Computer Go, The Ultimate">
|
||||
<short>Thomas Wolf from Brock University will be holding a talk on
|
||||
the asian game of Go. All are welcome.</short>
|
||||
the Asian game of Go. All are welcome.</short>
|
||||
<abstract>
|
||||
<p>
|
||||
The asian game go is unique in a number of ways. It is the oldest
|
||||
The Asian game go is unique in a number of ways. It is the oldest
|
||||
board game known. It is a strategy game with very simple
|
||||
rules. Computer programs are very weak despite huge efforts and
|
||||
prizes of US$ > 1.5M for a program beating professional
|
||||
|
|
@ -3672,7 +3674,7 @@ Mathematics and restricted to the same.</i>
|
|||
|
||||
<p>
|
||||
The proposed change is illustrated <a
|
||||
href="http://www.csclub.uwaterloo.ca/docs/constitution-change-20020920.html">on
|
||||
href="http://www.csclub.uwaterloo.ca/about/constitution-change-20020920.html">on
|
||||
a web page</a>.
|
||||
</p>
|
||||
|
||||
|
|
@ -3693,7 +3695,7 @@ Mathematics and restricted to the same.</i>
|
|||
<p>
|
||||
This is the first in a series of seminars that cover the use
|
||||
of the UNIX Operating System. UNIX is used in a variety of
|
||||
applications, both in academia and industy. We will provide
|
||||
applications, both in academia and industry. We will provide
|
||||
you with hands-on experience with the Math Faculty's UNIX
|
||||
environment in this seminar.
|
||||
</p>
|
||||
|
|
@ -3828,7 +3830,7 @@ lent to you for the duration of this class.</p>
|
|||
<p>Perhaps you have are you interested in installing GNU/Linux.
|
||||
If so, bring your computer, monitor and keyboard; and we will
|
||||
help you install GNU/Linux on your machine. You can also find
|
||||
knowledgable people who can answer your questions about
|
||||
knowledgeable people who can answer your questions about
|
||||
GNU/Linux.</p>
|
||||
|
||||
<hr />
|
||||
|
|
@ -3889,7 +3891,7 @@ software---to make sure the software is free for all its users.
|
|||
</i><br/>--- Excerpt from the GNU GPL
|
||||
</blockquote>
|
||||
</p>
|
||||
<p>The GNU General Public License is one of the most influencial
|
||||
<p>The GNU General Public License is one of the most influential
|
||||
software licenses in this day. Written by Richard Stallman for the
|
||||
GNU Project, it is used by software developers around the world to
|
||||
protect their work.
|
||||
|
|
@ -3950,7 +3952,7 @@ on the fly for the host CPU.
|
|||
<short>Going to visit the York University Computer Club</short>
|
||||
<abstract><p>YUCC and the UW CSC have having a join meeting at York
|
||||
University. Dave Makalsky, the President of YUCC, will be giving a talk on
|
||||
Design-by-constract and Eiffel. Stefanus Du Toit, Vice-President of the UW
|
||||
Design-by-contract and Eiffel. Stefanus Du Toit, Vice-President of the UW
|
||||
CSC, will be giving a talk on the evil depths of the black art known as C++.
|
||||
</p><p>Schedule</p>
|
||||
<ul><li>1:30pm: Leave UW</li>
|
||||
|
|
@ -4033,7 +4035,7 @@ of Western Ontario. This is his last year in a concurrent
|
|||
Computer Engineering and Computer Science degree. His research
|
||||
interest range from distributed and parallel systems to low
|
||||
level optimized hardware design. He likes playing guitar and
|
||||
just bought a Cort NTL-20, jumbo body, solid spurce top with
|
||||
just bought a Cort NTL-20, jumbo body, solid spruce top with
|
||||
a mahogany back. Carlos hacks on the PARISC Linux kernel, GNU libc,
|
||||
GNU Debugger, GNU Binutils and various Debian packages.
|
||||
</p>
|
||||
|
|
|
|||
BIN
favicon.ico
BIN
favicon.ico
Binary file not shown.
|
Before Width: | Height: | Size: 1.1 KiB After Width: | Height: | Size: 3.6 KiB |
11
index.xml
11
index.xml
|
|
@ -4,14 +4,13 @@
|
|||
|
||||
<cscpage title="Computer Science Club of the University of Waterloo: Home" pre="./">
|
||||
<biglogo />
|
||||
<menu />
|
||||
|
||||
<section title="Welcome!">
|
||||
<p>
|
||||
Welcome to the University of Waterloo Computer Science Club website. Use
|
||||
the menus at the top and bottom of our pages to navigate around our kickass
|
||||
website website. If you're new to the Computer Science Club, be sure to
|
||||
check out our <a href="about/">About section</a>.
|
||||
the menu at the top of our pages to navigate around our kick-ass website.
|
||||
If you're new to the Computer Science Club, be sure to check out our
|
||||
<a href="about/">About section</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
|
|
@ -37,8 +36,8 @@
|
|||
<section title="Getting your own homepage">
|
||||
<p>
|
||||
Many members of the Computer Science Club host their homepage on
|
||||
our webserver. To find out how to
|
||||
get your own, check out the <a href="users/">Users page</a>.
|
||||
our web server. To find out how to
|
||||
get your own, check out the <a href="services/">Services page</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 5.6 KiB |
|
|
@ -5,13 +5,13 @@
|
|||
<header/>
|
||||
<section title="CSC Media">
|
||||
Here you will find a wide variety of audio and video recordings of past
|
||||
CSC and other unversity-related talks. Some of these files are very large,
|
||||
CSC and other university-related talks. Some of these files are very large,
|
||||
and we do not recommend attempting to stream them. Most of these should be
|
||||
available upon request at the Computer Science Club office to be burnt to
|
||||
CD or DVD should you so choose.
|
||||
<ul>
|
||||
|
||||
<mediaitem title="C++0x - An Overview" buttons="yes">
|
||||
<mediaitem title="C++0x - An Overview">
|
||||
<abstract><p>
|
||||
A good programming language is far more than a simple collection of
|
||||
features. My ideal is to provide a set of facilities that smoothly work
|
||||
|
|
@ -151,7 +151,7 @@
|
|||
doctorates.
|
||||
</p><p>
|
||||
The Question and Answer session (starting shortly after the hour and half
|
||||
mark) possed a number of interesting questions including, "Do you support
|
||||
mark) posed a number of interesting questions including, "Do you support
|
||||
the Creative Commons license?" and "Can I use ATI and NVIDIA drivers
|
||||
because Mesa isn't nearly as complete?".
|
||||
<p></p>
|
||||
|
|
@ -179,7 +179,7 @@
|
|||
A discussion of software start-ups founded by UW students and what they
|
||||
did that helped them grow and what failed to help. In order to share the
|
||||
most insights and guard the confidences of the individuals involved, none
|
||||
of the companies will be identifed.
|
||||
of the companies will be identified.
|
||||
</p></abstract>
|
||||
<mediafile file="larry-smith-talk2.avi" type="DivX" size="332M" />
|
||||
<mediafile file="larry-smith-talk2-xvid.avi" type="XviD" size="332M" />
|
||||
|
|
@ -197,7 +197,7 @@
|
|||
vendors are embracing parallelism by multiplying the number of cores on
|
||||
CPUs, following what Graphics Processing Unit (GPU) vendors have been
|
||||
doing for years. The Multi-core revolution promises to provide
|
||||
unparalleled increases in performance, but it comes with a catch:
|
||||
unparallelled increases in performance, but it comes with a catch:
|
||||
traditional serial programming methods are not at all suited to
|
||||
programming these processors and methods such as multi-threading are
|
||||
cumbersome and rarely scale beyond a few cores. Learn how, with hundreds
|
||||
|
|
|
|||
19
menu.xml
19
menu.xml
|
|
@ -1,19 +0,0 @@
|
|||
<menudefs>
|
||||
<menuitem title="Home" icon="homepage" href="index.html"/>
|
||||
<menuitem title="About" icon="csc" href="about/"/>
|
||||
<menuitem title="Events" icon="calendar" href="events/"/>
|
||||
<menuitem title="Docs" icon="docs" href="docs/"/>
|
||||
<!-- <menuitem title="Gallery" icon="gallery" href="/gallery/"/>-->
|
||||
<menuitem title="Office" icon="office" href="office/"/>
|
||||
<!-- <menuitem title="Exec" icon="csc" href="about/exec.html"/> -->
|
||||
<menuitem title="Users" icon="users" href="users/"/>
|
||||
<menuitem title="Clubs" icon="clubs" href="clubs/"/>
|
||||
<!--<menuitem title="Stats" icon="stats" href="/stats/"/>-->
|
||||
<menuitem title="Media" icon="package_multimedia" href="media/"/>
|
||||
<menuitem title="Library" icon="koha" absolute="true" href="http://koha.csclub.uwaterloo.ca/"/>
|
||||
<menuitem title="Wiki" icon="sunflower" absolute="true" href="http://wiki.csclub.uwaterloo.ca/"/>
|
||||
<menuitem title="Webmail" icon="horde" absolute="true" href="https://mail.csclub.uwaterloo.ca/"/>
|
||||
<menuitem title="Mailman" icon="mm-icon" absolute="true" href="http://mailman.csclub.uwaterloo.ca/"/>
|
||||
<menuitem title="gopher" icon="gopher" absolute="true" href="gopher://csclub.uwaterloo.ca/"/>
|
||||
<menuitem title="gitweb" icon="gitweb" absolute="true" href="http://gitweb.csclub.uwaterloo.ca/"/>
|
||||
</menudefs>
|
||||
33
news.xml
33
news.xml
|
|
@ -2,7 +2,17 @@
|
|||
|
||||
<!DOCTYPE newdefs SYSTEM "csc.dtd">
|
||||
<newsdefs>
|
||||
<newsitem author="dtbartle" date="2007-08-13">
|
||||
<newsitem author="dtbartle" date="2007-09-09">
|
||||
The Fall 2007 election has been scheduled for Sept 20 at 4:30 pm in the
|
||||
comfy lounge.
|
||||
</newsitem>
|
||||
<newsitem author="dtbartle" date="2007-09-01">
|
||||
Nominations are now being accepted for Fall 2007 executive positions.
|
||||
Nominiations close on Sept 19 at 4:30 pm. See
|
||||
<a href="/newsgroup/article.php?id=11045&group=uw.csc">uw.csc</a> for
|
||||
details.
|
||||
</newsitem>
|
||||
<newsitem author="dtbartle" date="2007-09-01">
|
||||
Our talks our now mirrored on mirror.cs for ResNet and on-campus users.
|
||||
</newsitem>
|
||||
<newsitem author="mspang" date="2007-05-11">
|
||||
|
|
@ -97,7 +107,7 @@ have the developement tools!), or just watch the funny lights on the front of it
|
|||
</newsitem>
|
||||
<newsitem author="sfllaw" date="2004-02-05">
|
||||
We voted 15 to 0 to 0 in favour of changing the
|
||||
<a href="/docs/constitution.html">constitution</a> to follow MathSoc
|
||||
<a href="/about/constitution.html">constitution</a> to follow MathSoc
|
||||
policy. An updated copy of the document is now online.
|
||||
</newsitem>
|
||||
<newsitem author="sfllaw" date="2004-02-02">
|
||||
|
|
@ -122,7 +132,8 @@ have the developement tools!), or just watch the funny lights on the front of it
|
|||
for reading mail on.
|
||||
</newsitem>
|
||||
<newsitem author="ja2morri" date="2003-08-12">
|
||||
The <a href="docs/procedure.html">CSC Procedures manual</a> has been added to the website. Thanks go to
|
||||
The <a href="http://wiki.csclub.uwaterloo.ca/wiki/Exec_Manual">CSC
|
||||
Procedures manual</a> has been added to the website. Thanks go to
|
||||
Shannon Mann for reminding us of this document.
|
||||
</newsitem>
|
||||
<newsitem author="ja2morri" date="2003-08-06">
|
||||
|
|
@ -161,9 +172,9 @@ have the developement tools!), or just watch the funny lights on the front of it
|
|||
</newsitem>
|
||||
<newsitem author="sjdutoit" date="2002-09-30">
|
||||
The business meeting of 2002-09-30 was concluded and the <a
|
||||
href="/docs/constitution-change-20020920.html">constitutional
|
||||
href="/about/constitution-change-20020920.html">constitutional
|
||||
change</a> was approved with a 14:2 majority (and one spoiled
|
||||
ballot). See the new <a href="/docs/constitution.html">constitution</a>.
|
||||
ballot). See the new <a href="/about/constitution.html">constitution</a>.
|
||||
</newsitem>
|
||||
<newsitem author="sjdutoit" date="2002-09-16">
|
||||
The Fall elections have occured and the <a
|
||||
|
|
@ -176,17 +187,17 @@ have the developement tools!), or just watch the funny lights on the front of it
|
|||
be working quite right yet, but I'm working on it.
|
||||
</newsitem>
|
||||
<newsitem author="sjdutoit" date="2002-04-22">
|
||||
Added <a href="/office/books.html">books</a>! About 2.5 shelves are
|
||||
there, minus a whole lot that weren't readily accessible from the
|
||||
Library of Congress. Getting all of the books on there is going to
|
||||
Added <a href="http://library.csclub.uwaterloo.ca/">books</a>! About 2.5
|
||||
shelves are there, minus a whole lot that weren't readily accessible from
|
||||
the Library of Congress. Getting all of the books on there is going to
|
||||
be a tough job. These are, by the way, managed by good-old (or new?)
|
||||
CEO. Thanks to Ryan Golbeck and Petio for their hard work getting
|
||||
ISBN numbers onto disc.
|
||||
</newsitem>
|
||||
<newsitem author="sjdutoit" date="2002-04-15">
|
||||
Added a bunch of <a href="/events/old.html">old events</a> and <a
|
||||
href="/docs/">some documents</a>, including the <a
|
||||
href="/docs/constitution.html">constitution</a>.
|
||||
Added a bunch of <a href="/events/old.html">old events</a> and some
|
||||
documents, including the <a
|
||||
href="/about/constitution.html">constitution</a>.
|
||||
</newsitem>
|
||||
<newsitem author="sjdutoit" date="2002-04-15">
|
||||
Added the <a href="/about/members.html">membership list</a>. <a
|
||||
|
|
|
|||
|
|
@ -1,6 +1,3 @@
|
|||
SUBDIRS = books
|
||||
INPUTS = index.xml staff.xml books.xml operating-systems.xml webcam.xml webcam-streaming.xml computers.xml
|
||||
INPUTS = index.xml books.xml webcam.xml webcam-streaming.xml
|
||||
|
||||
include ../default.mk
|
||||
|
||||
books.html: ../books.xml
|
||||
|
|
|
|||
|
|
@ -4,8 +4,12 @@
|
|||
|
||||
<cscpage title="CSC Books">
|
||||
<header />
|
||||
<section title="CSC Book list">
|
||||
<all-books />
|
||||
<section title="CSC Books">
|
||||
<p>
|
||||
We are currently transitioning to our new library system, koha.
|
||||
Eventually all our books will listed in this system and checkouts will
|
||||
be handled through it as well.
|
||||
</p>
|
||||
</section>
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
|
|||
|
|
@ -1,3 +0,0 @@
|
|||
INPUTS =
|
||||
|
||||
include ../../default.mk
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE directory SYSTEM "../../csc.dtd">
|
||||
|
||||
<directory title="Office" href="../index.html">
|
||||
<diritem title="Staff" href="../staff.html" />
|
||||
<diritem title="Books" href="../books.html" />
|
||||
</directory>
|
||||
|
|
@ -1,105 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Computers of the CSC">
|
||||
<header />
|
||||
|
||||
<section title="List of computers the CSC controls">
|
||||
|
||||
<p>The Computer Science Club has access to a variety of different architectures to give members a chance to test their programs in different environments.</p>
|
||||
|
||||
<p>Here is a list of the computers we have available:</p>
|
||||
|
||||
<dl>
|
||||
<dt><strong>caffeine (csclub1.cs)</strong></dt>
|
||||
<dd>
|
||||
<p>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.</p>
|
||||
<p>caffeine has 2000 MB of RAM and a AMD Athlon 64 X2 (dual core) 4200+ processor.</p>
|
||||
</dd>
|
||||
<dt><strong>taurine</strong></dt>
|
||||
<dd>
|
||||
<p>This is a Debian stable machine.</p>
|
||||
<p>taurine has 8000 MB of RAM and two Dual-Core AMD Opteron(tm) Processor 2218</p>
|
||||
</dd>
|
||||
<dt><strong>artifical-flavours (csclub2.cs)</strong></dt>
|
||||
<dd>
|
||||
<p>This is a Debian unstable machine that runs a talk mirror.</p>
|
||||
<p>artifical-flavours has a Intel(R) Celeron(R) CPU 3.20GHz</p>
|
||||
</dd>
|
||||
<dt><strong>natural-flavours (csclub4.cs)</strong></dt>
|
||||
<dd>
|
||||
<p>This is a Debian unstable machine that runs a talk mirror.</p>
|
||||
<p>natural-flavours has 2 Intel(R) Core(TM)2 CPUs 6300 @ 1.86GHz</p>
|
||||
</dd>
|
||||
<dt><strong>citric-acid (csclub3.cs)</strong></dt>
|
||||
<dd>
|
||||
<p>This is a Debian unstable machine that runs a talk mirror.</p>
|
||||
<p>citric-acid is a AlphaServer 4100</p>
|
||||
</dd>
|
||||
<dt><strong>perpugilliam (peri)</strong></dt>
|
||||
<dd>
|
||||
<p>This is a Debian stable machine that was formerly ran the Computer Science Club. It is now on backup duty.</p>
|
||||
<p>peri has 512 MB of RAM and dual P3 450 MHz processors.</p>
|
||||
</dd>
|
||||
<dt><strong>glucose-fructose (sugar)</strong></dt>
|
||||
<dd>
|
||||
<p>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.</p>
|
||||
<p>It has 512 MB of RAM and dual P3 500 MHz processors.</p>
|
||||
</dd>
|
||||
<dt><strong>caramel-colour </strong></dt>
|
||||
<dd>
|
||||
<p>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.</p>
|
||||
<p>It as 512 MB of RAM and a single P3 1GHz processor. Its a good place to do random high-load work</p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>phosphoric-acid (h3po4)</strong></dt>
|
||||
<dd>
|
||||
<p>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.</p>
|
||||
<p>It as 512 MB of RAM and a single P3 1GHz processor. It also suffers from an extremely dodgy power supply.</p>
|
||||
</dd>
|
||||
|
||||
|
||||
<dt><strong>carbonated-water (h2o)</strong></dt>
|
||||
<dd>
|
||||
<p>Has been retired</p>
|
||||
<p>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.</p>
|
||||
<p>It has 256 MB of RAM and an AMD-K6 200 MHz processor.</p>
|
||||
</dd>
|
||||
<dt><strong>powerpc0 (aspartame)</strong></dt>
|
||||
<dd>
|
||||
<p>Has been retired</p>
|
||||
<p>powerpc0 is a <a href="http://www.uw-dig.uwaterloo.ca/">UW-DIG</a> 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.</p>
|
||||
<p>It has 64 MB of RAM and a 233 MHz PowerPC processor.</p>
|
||||
</dd>
|
||||
<dt><strong>sparc0</strong></dt>
|
||||
<dd>
|
||||
<p>Has been retired</p>
|
||||
<p>sparc0 is a <a href="http://www.uw-dig.uwaterloo.ca/">UW-DIG</a> 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.</p>
|
||||
<p>It has 128 MB of RAM and a TI UltraSparc IIi processor.</p>
|
||||
</dd>
|
||||
<dt><strong>frobisher</strong></dt>
|
||||
<dd>
|
||||
<p>Is currently out of commision (it smells like burning when plugged in)</p>
|
||||
<p>An experimental Corel Netwinder 275. Undead. It is rumoured to eat frosh.</p>
|
||||
<p>It has 64 MB of RAM and a flakey 133 MHz SuperARM processor.</p>
|
||||
</dd>
|
||||
<dt><strong>romana</strong></dt>
|
||||
<dd>
|
||||
<p>A BeBox, running BeOS 4.5. Finally back online!</p>
|
||||
</dd>
|
||||
<dt><strong>aquata</strong></dt>
|
||||
<dd>
|
||||
<p>Retired.</p>
|
||||
</dd>
|
||||
<dt><strong>calum</strong></dt>
|
||||
<dd>
|
||||
<p>Retired.</p>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
</section>
|
||||
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -4,8 +4,4 @@
|
|||
|
||||
<directory title="Office">
|
||||
<diritem title="Webcam" href="webcam.html" />
|
||||
<diritem title="Staff" href="staff.html" />
|
||||
<diritem title="Books" href="books.html" />
|
||||
<diritem title="Operating Systems" href="operating-systems.html" />
|
||||
<diritem title="Computers" href="computers.html" />
|
||||
</directory>
|
||||
|
|
|
|||
|
|
@ -8,23 +8,22 @@
|
|||
<p>
|
||||
The CSC Office is located at room MC3036/3037, in the Math &
|
||||
Computer Building of the University of Waterloo. The office is open
|
||||
whenever <a href="staff.html">office staff</a> are around to keep it
|
||||
whenever office staff are around to keep it
|
||||
open, which basically means it is open most of the time. You can
|
||||
check by taking a look through our <a href="webcam.html">web-enabled
|
||||
camera</a>. At the
|
||||
office we have <a href="http://koha.csclub.uwaterloo.ca">lots of books</a>, a couple of
|
||||
<a href="computers.html">computer terminals</a>, and most of the time
|
||||
an array of knowledgeable
|
||||
office we have <a
|
||||
href="http://library.csclub.uwaterloo.ca">lots of books</a>,
|
||||
a few computer terminals, and most of the time an array of knowledgeable
|
||||
people to talk to and ask questions.
|
||||
</p>
|
||||
<p>
|
||||
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 <a href="operating-systems.html">here</a> for
|
||||
a list of available operating systems.). The cost is $0.50 per CD at
|
||||
the time of this writing, or <b>free</b> if you provide your own CDs.
|
||||
architectures. The cost is $0.50 per disc at the time of this writing, or
|
||||
<b>free</b> if you provide your own discs.
|
||||
</p>
|
||||
<p>
|
||||
Another favourite is our $0.50 pop for members. We have a fridge in
|
||||
|
|
@ -32,7 +31,7 @@
|
|||
of pop cans.
|
||||
</p>
|
||||
<p>
|
||||
We can always use good <a href="staff.html">office staff</a>, so if
|
||||
We can always use good office staff, so if
|
||||
you're interested in helping out, just come by the office and chat
|
||||
to somebody there, and the office manager will probably give you
|
||||
something to do.
|
||||
|
|
|
|||
|
|
@ -1,39 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Operating Systems the CSC distributes">
|
||||
<header />
|
||||
|
||||
<section title="List of operating systems">
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>Here is a list of the operating systems we have available:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="http://www.debian.org/">Debian GNU/Linux 3.1r0 "Sarge" (x86)</a></li>
|
||||
<li><a href="http://www.debian.org/ports/hurd/">Debian GNU/Hurd K5 (i386)</a></li>
|
||||
<li><a href="http://fedora.redhat.com/">Fedora Core 4 (i386)</a></li>
|
||||
<li><a href="http://www.freebsd.org/">FreeBSD 4.10-RELEASE (i386)</a></li>
|
||||
<li><a href="http://www.freebsd.org/">FreeBSD 5.3-RELEASE (i386)</a></li>
|
||||
<li><a href="http://www.gentoo.org/index.xml">Gentoo Linux 2005.1 (i386)</a></li>
|
||||
<li><a href="http://www.knopper.net/knoppix/index-en.html">Knoppix 3.7 (x86)</a></li>
|
||||
<li><a href="http://www.mandrakelinux.com/en/">MandrakeLinux 10.1 (i586)</a></li>
|
||||
<li><a href="http://www.redhat.com/">Red Hat Linux 9 (i386)</a></li>
|
||||
<li><a href="http://www.opendarwin.org">OpenDarwin 6.6.x (x86, powerpc)</a></li>
|
||||
<li><a href="http://www.slackware.com/">Slackware Linux 10.0 (i386)</a></li>
|
||||
<li><a href="http://www.novell.com/linux/suse">SuSE Linux 9.1 Personal (x86)</a></li>
|
||||
<li><a href="http://www.ubuntulinux.org/">Ubuntu 5.04 (x86, amd64, powerpc)</a></li>
|
||||
</ul>
|
||||
|
||||
<p>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.</p>
|
||||
</section>
|
||||
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -1,24 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="CSC Office Staff">
|
||||
<header />
|
||||
<section title="Office staff responsibilities">
|
||||
<p>
|
||||
The CSC office staff have the following responsibilities:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Keep the office open as much as possible</li>
|
||||
<li>Keep the office clean at all times, through weekly cleaning and
|
||||
consistent removal of garbage</li>
|
||||
<li>Take care of adding new members, updating memberships and any
|
||||
other membership-related tasks through the use of CEO (CSC
|
||||
Electronic Office)</li>
|
||||
<li>Burn our free operating system CDs</li>
|
||||
<li>Answer questions</li>
|
||||
<li>Make sure the fridge is always full of pop</li>
|
||||
</ul>
|
||||
</section>
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -8,11 +8,11 @@
|
|||
|
||||
<p>Spy on the office, see whether it's open or who is passing by the door!</p>
|
||||
|
||||
<div class="webcam">
|
||||
<div class="webcam"><p>
|
||||
<img src="http://glucose-fructose.csclub.uwaterloo.ca:8080/" width="640" height="480" alt="Sugar's Webcam"/>
|
||||
<br/><br/>
|
||||
</p><p>
|
||||
<img src="http://phosphoric-acid.csclub.uwaterloo.ca:8080/" width="640" height="480" alt="Phosphoric-acid's Webcam"/>
|
||||
</div>
|
||||
</p></div>
|
||||
|
||||
<p>Tired of streaming? Try the <a href="webcam.html">regular version</a>.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@
|
|||
|
||||
<p>Spy on the office, see whether it's open or who is passing by the door!</p>
|
||||
|
||||
<div class="webcam">
|
||||
<div class="webcam"><p>
|
||||
<img src="http://glucose-fructose.csclub.uwaterloo.ca:8080/singleframe" width="640" height="480" alt="Sugar's Webcam"/>
|
||||
<br/><br/>
|
||||
</p><p>
|
||||
<img src="http://phosphoric-acid.csclub.uwaterloo.ca:8080/singleframe" width="640" height="480" alt="Phosphoric-acid's Webcam"/>
|
||||
</div>
|
||||
</p></div>
|
||||
|
||||
<p>Try the <a href="webcam-streaming.html">streaming version</a> for
|
||||
streamy goodness.</p>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@ UID:${ical_date}T${ical_start}\@csclub.uwaterloo.ca
|
|||
SEQUENCE:11
|
||||
DTSTART;TZID=Canada/Eastern:${ical_date}T${ical_start}
|
||||
DTEND;TZID=Canada/Eastern:${ical_date}T${ical_end}
|
||||
SUMMARY:<a href=http://www.csclub.uwaterloo.ca>$talk_title</a> -- $short
|
||||
SUMMARY:<a href=http://csclub.uwaterloo.ca>$talk_title</a> -- $short
|
||||
DESCRIPTION:$ical_abstract
|
||||
END:VEVENT
|
||||
END_OF_EVENT
|
||||
|
|
|
|||
|
|
@ -0,0 +1,5 @@
|
|||
INPUTS = index.xml clubs.xml machine_usage.xml machine_usage_summary.xml \
|
||||
machine_usage-change-20070819.xml
|
||||
SUBDIRS =
|
||||
|
||||
include ../default.mk
|
||||
|
|
@ -1,18 +1,10 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Clubs the CSC hosts">
|
||||
<cscpage title="Clubs list">
|
||||
|
||||
<header/>
|
||||
<section title="Clubs">
|
||||
<p>We have had a long history of serving the clubs at the University.
|
||||
We currently host <a href="#websites">websites</a> and
|
||||
<a href="#lists">mailing lists</a> for various organizations.</p>
|
||||
|
||||
<p>If you'd like to have your club hosted on our servers, please
|
||||
contact the Systems Committee at <a href="mailto:systems-committee@csclub.uwaterloo.ca">systems-committee@csclub.uwaterloo.ca</a>.</p>
|
||||
|
||||
</section>
|
||||
<section title="Club websites we host or have hosted" id="websites">
|
||||
<p>The following is a listing of clubs whose websites the CSC hosts
|
||||
or has hosted in the past:</p>
|
||||
|
|
@ -34,7 +26,7 @@
|
|||
<li><a href="http://csclub.uwaterloo.ca/~glow/">GLOW</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~hellenic/">Hellenic Students Assoctiation</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~indsa/">Indian Students Association</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~intsa/">International Student Association</a></li>
|
||||
<li>International Student Association <!-- http://csclub.uwaterloo.ca/~intsa/ --></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~italian/">Patrimonio Italian Student's Association</a></li>
|
||||
<li><a href="http://www.jewishstudentsassociation.org/">Waterloo Region Jewish Students Association</a></li>
|
||||
<li><a href="http://konja.uwaterloo.ca">Konnichiwa Japan</a></li>
|
||||
|
|
@ -52,7 +44,7 @@
|
|||
<li><a href="http://csclub.uwaterloo.ca/~twsa/">Taiwanese Student Association</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~ultimate/">Ultimate Waterloo</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~uwssa/">UW Serbian Students Association</a></li>
|
||||
<li>Waterloo Christian Fellowship</li>
|
||||
<li><a href="http://wcf.uwaterloo.ca/">Waterloo Christian Fellowship</a></li>
|
||||
<li><a href="http://csclub.uwaterloo.ca/~vsa/">Vietnamese Student Association</a></li>
|
||||
<li>Waterloo Chinese Catholic Community</li>
|
||||
<li>UW Tamil Students Association</li>
|
||||
|
|
@ -61,12 +53,5 @@
|
|||
</ul>
|
||||
</section>
|
||||
|
||||
<section title="Mailing lists we host" id="lists">
|
||||
<p>We also host a number of <a
|
||||
href="http://mailman.csclub.uwaterloo.ca/">mailing lists</a>
|
||||
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.</p>
|
||||
</section>
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE directory SYSTEM "../csc.dtd">
|
||||
|
||||
<directory title="Services">
|
||||
<diritem title="Usage Agreement" href="machine_usage.html" />
|
||||
<diritem title="Usage Agreement Summary" href="machine_usage_summary.html" />
|
||||
<diritem title="Webmail" href="https://mail.csclub.uwaterloo.ca/" />
|
||||
<diritem title="Library" href="http://library.csclub.uwaterloo.ca/" />
|
||||
</directory>
|
||||
|
|
@ -0,0 +1,95 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="Services that the CSC offers">
|
||||
|
||||
<header />
|
||||
<section title="Machine accounts">
|
||||
<p>
|
||||
The main benefit of becoming a CSC member is to get access to our various
|
||||
machines. We offer a large range of hardware, including Alpha, MIPS,
|
||||
UltraSPARC, i386, and AMD64. Our primary development machine, taurine, is
|
||||
a dual AMD Opteron (4 cores in total) with 8 GiB of RAM. Most of our
|
||||
machines are connected via gigabit ethernet. We offer 2 GiB of disk quota
|
||||
that is accessible across all of our machines. Our wiki contains a <a
|
||||
href="http://wiki.csclub.uwaterloo.ca/wiki/Machine_List">full machine
|
||||
list</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Email">
|
||||
<p>
|
||||
Members also receive a username@csclub.uwaterloo.ca email address.
|
||||
Mailboxes are considered as part of your disk quota, so your mailbox may
|
||||
grow up to the amount of disk quota you have. Attachments of any file size
|
||||
or type may be sent. Our mail server runs a POP3, IMAP, and SMTP server with
|
||||
SSL/TLS enabled. You can also access your mail via a <a
|
||||
href="https://mail.csclub.uwaterloo.ca">secure web interface</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Web space">
|
||||
<p>
|
||||
Many of members take advantage of our web hosting service. Our web server
|
||||
runs on Apache, and has PHP, Python, and Perl modules installed. We also
|
||||
have MySQL and PostgreSQL databases available upon request.
|
||||
</p><p>
|
||||
If you are already a member, you can enable your web space as follows:
|
||||
</p><ol>
|
||||
<li>
|
||||
Log in to one of the CSC machines (e.g. csclub.uwaterloo.ca)
|
||||
using an <a href="http://www.openssh.com/">SSH</a> client (e.g. <a
|
||||
href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a> on
|
||||
Windows or <a href="http://www.openssh.com/">OpenSSH</a> on *nix).
|
||||
</li><li>
|
||||
Create a directory called <code>www</code> in your home directory by
|
||||
typing <code>mkdir ~/www</code>.
|
||||
</li><li>
|
||||
Put the files you want on your web page in your new <code>www</code>
|
||||
directory. <code>index.html/php/py</code> will be loaded by default.
|
||||
You can upload files using an scp client (e.g. <a
|
||||
href="http://winscp.net/">WinSCP</a> on Windows or <a
|
||||
href="http://www.openssh.com/">OpenSSH</a> on *nix).
|
||||
</li>
|
||||
<li>
|
||||
Visit your snazzy new web page at
|
||||
<code>http://csclub.uwaterloo.ca/~username/</code>, where
|
||||
<code>username</code> should be replaced by your username.</li>
|
||||
</ol><p>
|
||||
If you're still having trouble getting your page up, just contact
|
||||
the <a href="mailto:webmaster@csclub.uwaterloo.ca">Webmaster</a> or the
|
||||
<a href="mailto:syscom@csclub.uwaterloo.ca">Systems Committee</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Club hosting">
|
||||
<p>
|
||||
If you're a club and looking for web space, the CSC is the place go. We
|
||||
offer clubs the same services we offer members (e.g. disk quota,
|
||||
databases). We also offer the following additional services to clubs:
|
||||
</p><ul>
|
||||
<li>
|
||||
club.uwaterloo.ca domain registration.
|
||||
</li><li>
|
||||
president@club.uwaterloo.ca or similar email addresses.
|
||||
</li><li>
|
||||
mailing-lists@club.uwaterloo.ca or similar mailing lists.
|
||||
</li>
|
||||
</ul><p>
|
||||
You can view a list of clubs that we have hosted or still host on our
|
||||
<a href="clubs.html">clubs list</a>.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Library">
|
||||
<p>
|
||||
The CSC maintains an extensive collection of Computer Science related
|
||||
books. You browse our library online by going to our <a
|
||||
href="http://library.csclub.uwaterloo.ca/">library system</a>. CSC members
|
||||
are free to borrow most of the books in the library. Certain books must
|
||||
remain in the club office, and can be read there.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -0,0 +1,275 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="CSC Machine Policy, 15 February 1995">
|
||||
<header/>
|
||||
|
||||
<section title="Notes">
|
||||
<p>
|
||||
Everyone who receives an account on one of the CSC machines must sign
|
||||
the agreement in the final section. This document does not state who
|
||||
will be allowed accounts on CSC machines, the normal expiry period of
|
||||
accounts, nor any other similar matters. Further, this policy does
|
||||
not, in general, guarantee any ``rights'' to users.
|
||||
</p>
|
||||
<p>
|
||||
Policies for group accounts and administrative accounts are not yet
|
||||
available (this section will contain links to them when they do become
|
||||
available). There is also a brief (instead of legalese)
|
||||
<a href="machine_usage_summary.html">summary of the usage policy</a> available.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Usage Policy">
|
||||
|
||||
<p>The usage policy is divided into the following sections:</p>
|
||||
<ol>
|
||||
<li><a href="#usageaccept">Acceptable and Unacceptable Use</a></li>
|
||||
<li><a href="#usagerespons">User Responsibilities</a></li>
|
||||
<li><a href="#usagesecurity">Security</a></li>
|
||||
<li><a href="#usagerights">Rights of the Systems Committee and the CSC Executive</a></li>
|
||||
</ol>
|
||||
|
||||
<p>
|
||||
Note that in the following sections, the term "user" implies a user of a
|
||||
CSC machine, unless otherwise specified.
|
||||
</p>
|
||||
|
||||
<h3><a id="usageaccept">Acceptable and Unacceptable Use</a></h3>
|
||||
|
||||
<p>
|
||||
The CSC machines are intended for research, personal projects,
|
||||
and general use in accordance with the aims of the CSC (see the
|
||||
<a href="../about/constitution.html">CSC Constitution</a> for further details).
|
||||
Projects that are of interest to the CSC may be given special priority
|
||||
by the CSC Systems Committee.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Users must adhere to the CSC's policies concerning machine usage.
|
||||
</p>
|
||||
|
||||
<h3><a id="usagerespons">User Responsibilities</a></h3>
|
||||
<p>
|
||||
Users must be responsible for their behaviour.
|
||||
Users, and not the CSC, will be held accountable for any of their illegal,
|
||||
damaging or unethical actions. Such actions are obviously not permitted
|
||||
on CSC machines.
|
||||
</p>
|
||||
<p>
|
||||
Users must act responsibly, and the needs of others with regard to
|
||||
computing resources must be considered at all times. In particular, no
|
||||
user should use any resource to an extent that other users are prevented
|
||||
from similarly using that resource, and no user's actions shall disrupt
|
||||
the work of other users.
|
||||
</p>
|
||||
<p>
|
||||
Users must also abide by the usage policies of all machines that they
|
||||
connect to from CSC machines, or use to connect to CSC machines. It is
|
||||
the users' responsibility to check the policies of <em>all</em> machines
|
||||
that they connect to.
|
||||
|
||||
</p>
|
||||
|
||||
<h3><a id="usagesecurity">Security</a></h3>
|
||||
<p>
|
||||
Users may not attempt to gain access to accounts
|
||||
other than those which they have been permitted to use.
|
||||
Similarly, users may not attempt to access other users'
|
||||
private files, nor may they attempt to find out the password of
|
||||
any account.
|
||||
</p>
|
||||
<p>
|
||||
An account may only be used by the person assigned to it. <em>Do not
|
||||
tell your password to anybody, or let anyone else use your account</em>.
|
||||
Users should consider the security implications of their actions. For
|
||||
example:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Passwords for accounts on CSC machines should not be used on
|
||||
other machines</li>
|
||||
|
||||
<li>Accounts not on MFCF or CSC machines should not be granted
|
||||
automatic access to CSC accounts (e.g. via .rhosts files).</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
The appropriate members of the systems committee must be notified immediately
|
||||
in the event that a security problem is found. Naturally, the problem
|
||||
should neither be exploited nor made public until it can be corrected.
|
||||
</p>
|
||||
|
||||
<h3><a id="usagerights">Rights of the Systems Committee and the CSC Executive</a></h3>
|
||||
<p>
|
||||
The Systems Committee may examine any files or programs believed to be out of
|
||||
control or in violation of the usage policies for the CSC network.
|
||||
Examination of a program includes examination of the running process
|
||||
and its binary. Files believed to be the data or source to the process
|
||||
may also be examined. The process may be killed, stopped or otherwise
|
||||
interrupted at the discretion of the Systems Committee. If
|
||||
the Systems Committee takes any of the
|
||||
above actions, the owner of the process will be notified.
|
||||
</p>
|
||||
<p>
|
||||
The Systems Committee may at any time revoke a user's permission to
|
||||
access an account provided that a written (possibly electronic)
|
||||
explanation is given. Cause for removal of access to an account
|
||||
includes, but is not limited to, violation of the machine usage policy.
|
||||
In the event of a dispute, a user whose account has been revoked
|
||||
may appeal to the CSC Executive for its reinstatement, as per the
|
||||
<a href="../about/constitution.html">CSC Constitution</a>.
|
||||
|
||||
</p>
|
||||
<p>
|
||||
The CSC Executive has the right to update any policy, including this one,
|
||||
with reasonable notice.
|
||||
</p>
|
||||
|
||||
</section>
|
||||
|
||||
<section title="Club Accounts">
|
||||
<p>The club accounts policy is divided into the following 2 sections:</p>
|
||||
<ol>
|
||||
<li><a href="#clubaccess">Access Control</a></li>
|
||||
<li><a href="#clubrespons">Responsibility and Accountability</a></li>
|
||||
</ol>
|
||||
|
||||
<h3><a id="clubaccess">Access Control</a></h3>
|
||||
<p>
|
||||
Note: For the given section, any mention of the club, except in direct
|
||||
reference to the Computer Science Club, will refer an club other than the
|
||||
CSC, which has, or requests, an account on a Computer Science Club machine.
|
||||
</p>
|
||||
<p>
|
||||
Clubs are given accounts to provide them with e-mail and WWW pages, but are
|
||||
subject to the following to certain rules. They are as follows:
|
||||
</p>
|
||||
<ol>
|
||||
<li>
|
||||
The club account is subject to all restrictions of a users
|
||||
account, except that it is a shareable account.
|
||||
</li>
|
||||
<li>
|
||||
The club members must have regular user accounts on the CSC
|
||||
machine that the club account will be on. If the club member
|
||||
does not already have such an account, one will be created
|
||||
to allow the member to manage the club account.
|
||||
</li>
|
||||
<li>
|
||||
The members of the club with access to the club
|
||||
account shall be known to the CSC Systems
|
||||
Administrator to ensure that these people are aware of this
|
||||
section of the user agreement.
|
||||
</li>
|
||||
<li>
|
||||
The club members with access to the club account shall not grant
|
||||
access to any other members by any means that are available to
|
||||
them, other than approaching the CSC System Administrator and
|
||||
requesting the change of access.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<h3><a id="clubrespons">Responsibility and Accountable</a></h3>
|
||||
<p>
|
||||
The account is the responsibility of the members who have access. If the
|
||||
resources owned by the club account are found to be in violation of any
|
||||
policy/rule/law of any of, but not limited to, the Computer Science Club,
|
||||
MFCF, the University of Waterloo, or any relevant law enforcement agency,
|
||||
then the members with access will be held <b>equally</b> responsible for
|
||||
that action.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section title="Definitions">
|
||||
<dl>
|
||||
<dt>CSC</dt>
|
||||
<dd>The University of Waterloo <a href="/">Computer Science Club</a>,
|
||||
a student chapter of the ACM. The CSC office is located in room
|
||||
3036/3037 of Mathematics and Computer Building (UW campus),
|
||||
telephone number (519) 888-4657 x3870.
|
||||
</dd>
|
||||
|
||||
<dt>CSC Network</dt>
|
||||
<dd>
|
||||
The network of computer hardware and peripherals owned by,
|
||||
rented to, on loan to, or otherwise under the control of the CSC.
|
||||
</dd>
|
||||
<dt>MFCF</dt>
|
||||
<dd>
|
||||
The <a href="http://www.math.uwaterloo.ca/mfcf/">Math Faculty
|
||||
Computing Facility</a> at the University of Waterloo.
|
||||
</dd>
|
||||
|
||||
<dt>Machine</dt>
|
||||
<dd>
|
||||
Computer, terminal or other piece of hardware. Non-CSC machines
|
||||
include MFCF's xterms and printers.
|
||||
</dd>
|
||||
<dt>Systems Committee</dt>
|
||||
<dd>
|
||||
An appointed body responsible for the operation of the CSC network
|
||||
and the software that runs on it.
|
||||
A complete description is available in the
|
||||
<a href="../about/constitution.html">CSC Constitution</a>.
|
||||
</dd>
|
||||
|
||||
<dt>Network Bandwidth</dt>
|
||||
<dd>
|
||||
The percentage of bytes per unit of time that can be handled by
|
||||
the network(s) in question. These networks include the University
|
||||
of Waterloo on-campus network and the Internet.
|
||||
</dd>
|
||||
<dt>Computing Resources</dt>
|
||||
<dd>Resources the CSC considers limited include
|
||||
<ul>
|
||||
<li>public temporary disk space</li>
|
||||
|
||||
<li>swap space</li>
|
||||
<li>other commonly held disk space
|
||||
(which may include the home file system)</li>
|
||||
<li>inodes</li>
|
||||
<li>memory</li>
|
||||
<li>CPU time</li>
|
||||
<li>processes</li>
|
||||
|
||||
<li>ttys and pseudo-ttys</li>
|
||||
<li>network bandwidth</li>
|
||||
<li>ports</li>
|
||||
<li>computer paper</li>
|
||||
</ul>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
|
||||
<section title="User Agreement">
|
||||
<p>
|
||||
I have read and understood the usage policy of 29 August 2007, and I
|
||||
agree to use my account(s) on the CSC network in accordance with this
|
||||
policy. I am responsible for all actions taken by anyone using this
|
||||
account. Furthermore, I accept full legal responsibility for all of the
|
||||
actions that I commit using the CSC network according to
|
||||
any and all applicable laws.
|
||||
</p>
|
||||
<p>
|
||||
I understand that with little or no notice machines on the CSC
|
||||
network and resources on these machines may become unavailable.
|
||||
Machines may ``go down'' while users are using them, and I will
|
||||
not hold the CSC responsible for lost time or data.
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
Name: ___________________________
|
||||
|
||||
Signature: ___________________________
|
||||
|
||||
Office Staff: ___________________________
|
||||
|
||||
Signature: ___________________________
|
||||
|
||||
Date: ___________________________
|
||||
</pre>
|
||||
</section>
|
||||
|
||||
<footer />
|
||||
|
||||
</cscpage>
|
||||
|
|
@ -40,7 +40,7 @@ CSC machine, unless otherwise specified.
|
|||
<p>
|
||||
The CSC machines are intended for research, personal projects,
|
||||
and general use in accordance with the aims of the CSC (see the
|
||||
<a href="constitution.html">CSC Constitution</a> for further details).
|
||||
<a href="../about/constitution.html">CSC Constitution</a> for further details).
|
||||
Projects that are of interest to the CSC may be given special priority
|
||||
by the CSC Systems Committee.
|
||||
</p>
|
||||
|
|
@ -82,8 +82,8 @@ any account.
|
|||
<p>
|
||||
An account may only be used by the person assigned to it. <em>Do not
|
||||
tell your password to anybody, or let anyone else use your account</em>.
|
||||
Users should consider the security implications of their actions.<br/>
|
||||
For example:
|
||||
Users should consider the security implications of their actions. For
|
||||
example:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Passwords for accounts on CSC machines should not be used on
|
||||
|
|
@ -117,7 +117,7 @@ explanation is given. Cause for removal of access to an account
|
|||
includes, but is not limited to, violation of the machine usage policy.
|
||||
In the event of a dispute, a user whose account has been revoked
|
||||
may appeal to the CSC Executive for its reinstatement, as per the
|
||||
<a href="constitution.shtml">CSC Constitution</a>.
|
||||
<a href="../about/constitution.html">CSC Constitution</a>.
|
||||
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -142,33 +142,30 @@ CSC, which has, or requests, an account on a Computer Science Club machine.
|
|||
</p>
|
||||
<p>
|
||||
Clubs are given accounts to provide them with e-mail and WWW pages, but are
|
||||
subject to the following to certain rules.<br/>
|
||||
They are as follows:
|
||||
subject to the following to certain rules. They are as follows:
|
||||
</p>
|
||||
<ol>
|
||||
<li>
|
||||
The club account is subject to all restrictions of a users
|
||||
account, except that it is a shareable account
|
||||
account, except that it is a shareable account.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
The account shall be accessable to only 3 members of the club.
|
||||
Further, these 3 members shall be known to the CSC Systems
|
||||
Administrator to insure that these people are aware of this
|
||||
The club members must have regular user accounts on the CSC
|
||||
machine that the club account will be on. If the club member
|
||||
does not already have such an account, one will be created
|
||||
to allow the member to manage the club account.
|
||||
</li>
|
||||
<li>
|
||||
The members of the club with access to the club
|
||||
account shall be known to the CSC Systems
|
||||
Administrator to ensure that these people are aware of this
|
||||
section of the user agreement.
|
||||
</li>
|
||||
<li>
|
||||
The club members must be full members of the Computer Science
|
||||
Club, and have regular user accounts on the CSC machine that the
|
||||
club account will be on.
|
||||
</li>
|
||||
<li>
|
||||
The club members with access to the club account shall not grant
|
||||
access to any other members by any means that are available to
|
||||
them, other than approaching the CSC System Administrator and
|
||||
requesting the change of access. If there are already 3 club
|
||||
members with access, then a member with access must be removed
|
||||
before a new member can be given access.
|
||||
requesting the change of access.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
|
|
@ -213,7 +210,7 @@ Computer, terminal or other piece of hardware. Non-CSC machines
|
|||
An appointed body responsible for the operation of the CSC network
|
||||
and the software that runs on it.
|
||||
A complete description is available in the
|
||||
<a href="constitution.shtml">CSC Constitution</a>.
|
||||
<a href="../about/constitution.html">CSC Constitution</a>.
|
||||
</dd>
|
||||
|
||||
<dt>Network Bandwidth</dt>
|
||||
|
|
@ -246,7 +243,7 @@ The percentage of bytes per unit of time that can be handled by
|
|||
|
||||
<section title="User Agreement">
|
||||
<p>
|
||||
I have read and understood the usage policy of 17 April 1994, and I
|
||||
I have read and understood the usage policy of 29 August 2007, and I
|
||||
agree to use my account(s) on the CSC network in accordance with this
|
||||
policy. I am responsible for all actions taken by anyone using this
|
||||
account. Furthermore, I accept full legal responsibility for all of the
|
||||
|
|
@ -22,7 +22,7 @@ things that the users will agree to.
|
|||
<h3>Use of accounts:</h3>
|
||||
<ul>
|
||||
<li>one person only</li>
|
||||
<li>for hacking, not for course work or cracking</li>
|
||||
<li>for hacking or course work, not for cracking</li>
|
||||
<li>if you're not working on a specially authorized project, don't
|
||||
abuse system resources</li>
|
||||
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
INPUTS = index.xml
|
||||
SUBDIRS =
|
||||
|
||||
include ../default.mk
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<!DOCTYPE directory SYSTEM "../csc.dtd">
|
||||
|
||||
<directory title="User webpages">
|
||||
<diritem title="Membership List" href="../about/members.html" />
|
||||
</directory>
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
|
||||
|
||||
<cscpage title="User homepages at the CSC">
|
||||
|
||||
<header />
|
||||
<section title="Getting a homepage on here">
|
||||
<p>
|
||||
Would you like your own homepage on our server? That's easy! First,
|
||||
just make sure that you have a CSC <a
|
||||
href="../about/members.html">membership</a> and account (just
|
||||
come by our <a href="../office/">office</a> and sign up if not), then
|
||||
follow these easy steps:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Log in to one of the CSC machines (e.g. csclub.uwaterloo.ca)
|
||||
using an <a href="http://www.openssh.com/">SSH</a> client (e.g. <a
|
||||
href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a> on
|
||||
Windows or <a href="http://www.openssh.com/">OpenSSH</a> on
|
||||
unix).</li>
|
||||
<li>Create a directory called <code>www</code> by typing
|
||||
<code>mkdir www</code> from your home directory.</li>
|
||||
<li>Put the files you want on your web page in your new
|
||||
<code>www</code> directory. <code>index.html</code> will be loaded
|
||||
by default.</li>
|
||||
<li>Go visit your snazzy new webpage at
|
||||
<code>http://www.csclub.uwaterloo.ca/~username/</code>, where
|
||||
<code>username</code> should be replaced by your username!</li>
|
||||
</ul>
|
||||
<p>
|
||||
If you're still having trouble getting your page up, just contact
|
||||
the <a href="mailto:webmaster@csclub.uwaterloo.ca">Webmaster</a> or
|
||||
<a href="mailto:sysadmin@csclub.uwaterloo.ca">Sysadmin</a> by
|
||||
e-mail.
|
||||
</p>
|
||||
</section>
|
||||
<footer />
|
||||
</cscpage>
|
||||
|
|
@ -1,63 +0,0 @@
|
|||
<?xml version='1.0'?>
|
||||
|
||||
<xsl:stylesheet version="2.0"
|
||||
xmlns="http://www.w3.org/1999/xhtml"
|
||||
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns:fn="http://www.w3.org/2005/xpath-functions"
|
||||
xmlns:csc="http://www.csclub.uwaterloo.ca/xslt">
|
||||
|
||||
<xsl:template match="all-books">
|
||||
<p>The books we currently own include:</p>
|
||||
<table>
|
||||
<tr>
|
||||
<th>Title</th>
|
||||
<th>Author</th>
|
||||
</tr>
|
||||
<xsl:for-each select="document(concat($g_root, '/books.xml'))/booklist/book">
|
||||
<xsl:variable name="class">
|
||||
<xsl:choose>
|
||||
<xsl:when test="position() mod 2 = 0">books1</xsl:when>
|
||||
<xsl:otherwise>books2</xsl:otherwise>
|
||||
</xsl:choose>
|
||||
</xsl:variable>
|
||||
<tr class="{$class}" >
|
||||
<td>
|
||||
<a href="{$pre}office/books/{translate(@isbn, ' ', '_')}.html">
|
||||
<xsl:value-of select="@title" />
|
||||
<xsl:if test="@edition != ''">
|
||||
(<xsl:value-of select="@edition" />)
|
||||
</xsl:if>
|
||||
</a>
|
||||
</td>
|
||||
<td>
|
||||
<xsl:value-of select="@author" />
|
||||
</td>
|
||||
</tr>
|
||||
<xsl:result-document method="xml" encoding="ISO-8859-1"
|
||||
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
|
||||
href="{translate(concat($g_root, '/office/books/', @isbn, '.html'), ' ', '_')}">
|
||||
<html>
|
||||
<head>
|
||||
<title>Book: <xsl:value-of select="@title" /></title>
|
||||
<link rel="stylesheet" href="{$pre}default.css" type="text/css" />
|
||||
</head>
|
||||
<body><div>
|
||||
<xsl:call-template name="header" />
|
||||
<p>
|
||||
<b>Title: </b> <xsl:value-of select="@title" /><br />
|
||||
<b>Edition: </b> <xsl:value-of select="@edition" /><br />
|
||||
<b>ISBN: </b> <xsl:value-of select="@isbn" /><br />
|
||||
<b>Author: </b> <xsl:value-of select="@author" /><br />
|
||||
<b>Published: </b> <xsl:value-of select="@published" /><br />
|
||||
</p>
|
||||
<xsl:call-template name="footer" />
|
||||
</div></body>
|
||||
</html>
|
||||
</xsl:result-document>
|
||||
</xsl:for-each>
|
||||
</table>
|
||||
</xsl:template>
|
||||
|
||||
</xsl:stylesheet>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue