Add the old procedures manual and start the president section of the

executive manual
James Morrison 2003-08-12 23:13:52 +00:00
parent 16ca51cb34
commit d929bc1236
10 changed files with 2910 additions and 2 deletions

View File

@ -1,6 +1,7 @@
SUBDIRS = editing-example1 editing-example2 editing-example3 execmanual
SUBDIRS = editing-example1 editing-example2 editing-example3 execmanual \
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
constitution-change-20020920.xml execmanual.xml procedure.xml
include ../

View File

@ -2,10 +2,12 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
<!ENTITY prez SYSTEM "president.xml">
<!ENTITY veep SYSTEM "vice-president.xml">
<book><title>Computer Science Club Exec Manual</title>

docs/execmanual/president.xml Executable file
View File

@ -0,0 +1,89 @@
<?xml version="1.0" encoding="UTF-8"?>
<para>This chapter covers various useful notes for the CSC president,
ranging from who to call for room bookings to when the term should end.
I&#39;ll rant some more later.</para>
<title>What to do</title>
<para>The President is the person responsible. As ungrammatical as that
may seem, it is exactly accurate. He or she is responsible to make certain
that everything the CSC is involved in gets proper attention.Specifically,
the President&#39;s duties are:</para>
<para> to call and preside at all general, special, and executive
meetings of the Club;</para>
<para> to call and preside at all general, special, and executive
meetings of the Club;</para>
<para> to appoint all committees of the Club and the committee chair
of such committees, except the chair of the Programme Committee;</para>
<para> to audit, or to appoint a representative to audit, the
financial records of the club at the end of each academic term.</para>
<para>Wherever possible, the President should delegate tasks to others.
Not doing this can overburden the President.</para>
<para>As listed above the president is responsible for appointing
committee chair&#39;s and other positions. So, it is basically up to the
president to decide whether or not there is an explicit office staff. How
do people become office staff? Must the office close every day? What do
the members expect to get out of the club in this term? </para>
<para>The CSC is a MathSoc club as such you should know the <ulink
url="">MathSoc club policies</ulink>
and know that the president is a non-voting member of MathSoc council,
like MathSoc directors.</para>
<title>Planning events</title>
<para>Planning events is a useful thing to know, so go read the
Vice-President&#39;s section.</para>
<title>Useful contacts</title>
<para>It&#39;s a good thing to know who controls the keys to the
office and the money going to the club. Mathsoc does most of this
stuff, so besure to know the President and Treasurer of Mathsoc. They
can be emailed at and</para>
<para>You can try getting a projector from MFCF/CSCF. You probably
want to talk to Dave Gawley, <email></email>.
He&#39;s been really friendly to the CSC in the past and is a cool guy
in general.</para>

View File

@ -13,6 +13,8 @@
<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">CSC Procedures manual</a> This will get integrated into the executive manual</li>
<li><a href="">Mathsoc Clubs manual</a></li>

docs/ Executable file

Binary file not shown.

docs/procedure.xml Executable file
View File

@ -0,0 +1,20 @@
<?xml version='1.0'?>
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
<cscpage title="CSC Procedures manual">
<header />
<section title="The CSC Procedures 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 procedures manual is 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 procedures manual is written using LaTeX and is available
<a href="procedure/procedure.pdf">in PDF format</a>. The
<a href="procedure/procedure.latex">LaTeX source</a> is also on-line.</p>

docs/procedure/Makefile Executable file
View File

@ -0,0 +1,36 @@
STYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl
FOSTYLESHEET = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/fo/docbook.xsl
XSLTPROC = xsltproc
XMLS = $(wildcard *.xml)
HTMLS = $(XMLS:.xml=.html)
#all: book.html book.tex book.pdf
all: procedure.pdf
%.pdf: %.tex
pdflatex $<
clean-recurse: clean
rm -f *.html *.fot *.out *.fo *.pdf *.log *.aux *.ps *.dvi *.toc
#book.html: $(XMLS)
#%.html: %.xml
# $(XSLTPROC) $(STYLESHEET) $< > $@ %.xml
#%.tex: %.xml
# openjade -t tex -d /usr/share/sgml/docbook/stylesheet/dsssl/modular/print/docbook.dsl $<
#%.dvi: %.tex
# jadetex $<
#%.pdf: %.tex
# pdfjadetex $< %.dvi
# dvips -o $@ $<

docs/procedure/csc.procedure.latex Executable file

File diff suppressed because it is too large Load Diff

docs/procedure/procedure.tex Executable file

File diff suppressed because it is too large Load Diff

View File

@ -2,6 +2,10 @@
<!DOCTYPE newdefs SYSTEM "csc.dtd">
<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
Shannon Mann for reminding us of this document.
<newsitem author="ja2morri" date="2003-08-06">
We've finally gotten around to disabling accounts. If you find your
account has been improperly disabled please email