www
/
www
7
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Added a bunch of documents.

news-update
Stefanus Du Toit 2002-04-16 03:50:59 +00:00
parent a51c0d9a42
commit 250923598c
5 changed files with 793 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

369
docs/constitution.xml Executable file
View File

@ -0,0 +1,369 @@
<?xml version='1.0'?>
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
<cscpage title="Constitution of the Computer Science Club of the University of Waterloo">
<header />
<section title="Name">
<ol><li> The name of this organization shall be the ``Computer Science Club
of the University of Waterloo''.</li>
</ol>
</section>
<section title="Purpose">
<ol><li> The Club is organized and will be operated exclusively for educational
and scientific purposes in furtherance of:</li>
<ol><li> promoting an increased knowledge of computer science and its applications.</li>
<li> promoting a greater interest in computer science and
its applications; and</li>
<li> <a name="comm">&#160;</a> providing a means of communication between persons
having interest in computer science.</li>
</ol>
<li> the above purposes will be fulfilled by the organization of
discussions and lectures with professionals and academics in the field
of computer science and related fields, co-operation with the Student
Chapter of the ACM of the University of Waterloo, the maintenance of a
library of materials related to computer science, the maintenance of
an office containing the library as an aid to aim (<a
href="#comm">1c</a>) above, and such other means as
decided by the club membership.</li>
</ol>
</section>
<section title="Membership">
<ol>
<li> Recognizing that the Computer Science Club has, in the past,
benefitted from the participation of individuals who were not
undergraduates at the University of Waterloo, full membership in this
organization shall be open to all members of the University of
Waterloo community. This includes, but is not limited to, students,
staff, and faculty, and anyone who has previously belonged to one of
these categories. In the event of a dispute, the Executive shall
decide whether an individual is eligible for full membership.<br />
At their discretion, the Executive may also allow individuals not satisfying
the above description to obtain a full membership.</li>
<li> Affiliate membership in this Club shall be open to all other
persons. Affiliate members shall have all the rights of full members
except for the rights of voting and holding executive office.</li>
<li> A person is not a member until he or she has paid
the current membership
fee and has been issued a membership card.
Membership lasts until the end of the term in which it was issued.
The membership card indicates, at least, a member's name, membership number,
the term for which the membership is valid, and an indication that
the member is an associate member, if indeed that is true.
The membership fee is set from time to time by the Executive.</li>
</ol>
</section>
<section title="Officers">
<ol><li> The officers of the Club shall be:</li>
<ol><li> President</li>
<li> Vice-President</li>
<li> Secretary</li>
<li> Treasurer</li>
<li> System Administrator</li>
</ol>
<li> The faculty advisor shall be an ex-officio member of the
Club.</li>
<li> The choice of officers shall be limited to full members of the
Club.</li>
<li> All officers, other than the System Administrator, shall be
elected at a meeting to be held no later than three weeks after the
start of each school term, such start defined as the beginning of
lectures in the Winter and Spring terms, and as the beginning of
Orientation Week in the Fall term.</li>
<li> The election of officers shall be accomplished by the following
procedure:</li>
<ol>
<li> The past executive shall choose a willing Chief Returning
Officer, with duties defined below, set an election date, and set a
date for the opening of nominations such that the nomination period
(from the opening of nominations to 4:30 P.M. on the day preceding
the elections) is at least one week.</li>
<li> Announcements of the election and the nomination procedure must
be distributed to all members by one or more of electronic mail,
Usenet, or posters in at least the Math and Computer building.</li>
<li> During the nomination period, the Chief Returning Officer (CRO)
shall be available to receive nominations for the posts of officers of
the club, either in person, by depositing nomination forms in the
CSC's mailbox in the MathSoc office, or by writing the nomination in a
place in the CSC office to be specified by the CRO.</li>
<li> A nomination shall consist of the nominee's name, and post(s)
nominated for. Nominees must be full members of the Computer Science
Club.</li>
<li> The election shall commence with the offering of memberships for
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
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
winner will be removed from subsequent contests. If this removal or
lack of nominations results in a vacant post, elections for such posts
may not be held at the election meeting, but elections for such posts
may be held at a later date, in accordance with the election
procedures. The membership decides whether or not to hold extra
elections.</li>
</ol>
<li> Following the elections, it is the responsibility of the new executive
to select a System Administrator. The selection of System Administrator must
then be ratified by the membership of the Club. If a suitable System
Administrator is not available, then the executive may delay their selection
until one becomes available. In this case the selection of System
Administrator must be ratified at the next meeting of the Club.</li>
<li> The faculty advisor shall be appointed by the present executive council
within three (3) weeks of each term's elections. The faculty
advisor shall be a person having membership in the Association for Computing
Machinery and having a genuine interest in the Club.</li>
<li> Any two offices may be held by a single person if the President
deems this advisable, subject to the consent of the membership.</li>
<li> In the case of a resignation of an officer or officers, the membership
may call elections to replace such officer(s).
If they are called, they must follow the given election procedure.
Such elections would be for all offices which are vacant.</li>
</ol>
</section>
<section title="Duties of Officers">
<ol>
<li> The duties of the President shall be:</li>
<ol>
<li> to call and preside at all general, special, and executive
meetings of the Club;</li>
<li> to appoint all committees of the Club and the committee chairmen
of such committees, except the chairman of the programmes committee;
and</li>
<li> to audit, or to appoint a representative to audit, the financial
records of the club at the end of each academic term.</li>
</ol>
<li> The duties of the Vice-President shall be:</li>
<ol><li> to assume the duties of the President
in the event of the President's absence;</li>
<li> to act as chairman of the programmes committee; and</li>
<li> to assume those duties of the President
that are delegated to him by the President.</li>
</ol>
<li> The duties of the Secretary shall be:</li>
<ol><li> to keep minutes of all Club meetings;</li>
<li> to prepare the annual Club report for
approval by the executive council;</li>
<li> to care for all Club correspondence;</li>
</ol>
<li> The duties of the Treasurer shall be:</li>
<ol>
<li> to collect dues and maintain all financial and membership records;</li>
<li> to produce a financial or membership statement when requested;</li>
</ol>
<li> The duties of the System Administrator shall be:</li>
<ol>
<li> to chair the Systems Committee</li>
<li> to perform in conjunction with the Systems Committee, the duties listed
in <a href="#sysduties">7.2</a>.</li>
</ol>
</ol>
</section>
<section title="Executive Council">
<ol>
<li> The executive council shall consist of the present officers of
the Club and the faculty advisor. The new executive council shall
take effect immediately following the installation of new officers or
a new faculty advisor.</li>
<li> The executive council has the power of a general assembly, though
an actual general assembly may overrule its decisions. Minutes of the
executive council meetings shall be available for inspection by any
member of the Club and shall be filed with the Club records. Further,
all recent executive council decisions shall be announced at the next
regular meeting of the club.</li>
</ol>
</section>
<section title="Committees">
<h3>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
accordance with apparent membership interests and the aims of the
Club as set forth in Section <a href="#purpose">2</a>.</li>
<li> The programme committee shall be responsible to the executive
council.</li>
</ol>
<h3>Systems Committee</h3>
<ol><li> The Systems Committee will be a standing committee, chaired by the
Systems Administrator.</li>
<li> The Executive Council shall appoint members to the Systems Committee.
Such members should show interest and ability in Systems Administration.</li>
<li> The Systems Committee will collectively, under the leadership of the
Systems Administrator,</li>
<ol><li> to operate any and all equipment in the possession of the Club.</li>
<li> to maintain and upgrade the software on equipment that is operated by
the Club.</li>
<li> to facilitate the use of equipment that is operated by the
Club.</li>
</ol></ol>
<h3>Library Committee</h3>
<ol><li> The library committee will be a standing committee, headed by the
Librarian of the Computer Science Club.</li>
<li> The Librarian shall be selected by the Executive Council.</li>
<li> Either the Executive Council or the Librarian may appoint members to
the library committee.</li>
<li> The library committee will be responsible for</li>
<ol><li> purchasing new materials to be added to the Computer Science Club
library, with a target amount of money to spend indicated by the Treasurer;</li>
<li> keeping the library in some semblance of order;</li>
<li> in conjunction with the Systems Committee, maintaining an up-to-date,
online record of the materials in the library.</li>
</ol></ol>
<h3>Other Committees</h3>
<ol>
<li> The President, with approval of the executive council, may appoint such
temporary committees as is deemed necessary.</li>
</ol>
</section>
<section title="Meetings">
<ol><li> General meetings of the Club shall
be called at times designated by the
executive council, at the recommendations of the programme committee.</li>
<li> Special meetings may be called at any time
deemed necessary by the executive council or
by the faculty advisor.</li>
<li> All members shall be notified at
least two days prior to a forthcoming meeting.
Electronic mail and/or posting to Usenet will be considered sufficient
notification, though other forms of notification are also encouraged.</li>
<li> The Club shall hold meetings only in places
that are open to all members
of the Club.</li>
</ol>
</section>
<section title="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
a tentative budget for the following academic term.</li>
<li> The Treasurer shall present, as part of the tentative budget, a
recommended fee to be levied on the members in the following academic
period.</li>
<li> The signing officers shall be the Treasurer, and one of the
President or Vice-President.</li>
<li> At the end of each term, the President or his/her representative shall ensure
that the financial records are complete and accurate.</li>
</ol>
</section>
<section title="Amendments and Procedures">
<ol><li> Amendments to the constitution shall be made in the following
manner:</li>
<ol><li> the proposed amendment shall be announced to all members via
one or more of</li>
<ol><li> a general meeting</li>
<li> electronic mail</li>
<li> Usenet</li>
</ol>
<li> the proposed amendment shall be made available for viewing by all
members in the Computer Science Club office;</li>
<li> A business meeting shall be held
at least seven (7) days after the announcement and no more than thirty (30) days after;</li>
<li> At this business meeting,
the amendment shall be read again and voted upon.
Two thirds of those present
and voting shall be required to carry the amendment;</li>
</ol>
<li> A quorum necessary for the conduct of business
is defined as fifteen (15) members
or 2/3 of the membership, whichever is smaller.</li>
<li> Rulings on any point of procedure
not included in this constitution shall be
made by the President with approval of the faculty advisor.</li>
<li> The executive council must bring before the members,
within three (3) weeks,
any motions with the
signatures of ten (10) members affixed to it.</li>
<li> For a normal motion to pass, a simple majority is required.
For motions of impeachment and motions calling for new elections, a 2/3
majority is required, as is seven (7) days notice of voting on such a motion.
In addition, if such a motion is defeated, it cannot be brought before the
Club again within sixty (60) days.</li>
</ol>
</section>
<section title="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>
</ol>
</section>
<section title="Use of Club Resources">
<ol><li> All resources under control of the Club are to be used in accordance with
the aims of the Club.</li>
<li> The President and Vice-President are jointly responsible
for the proper use of all Club
resources, except that the entire executive is responsible for the main Club
account on the main Math Faculty Computing Facility computer.
Permission to use a resource is automatically granted to someone responsible
for that resource, and optionally as determined by unanimous vote of those
responsible for a resource.
Granting permission to someone to use a resource does not make that person
responsible for the proper use of the resource, although the user is, of
course, responsible to the person granting permission.</li>
</ol>
</section>
<footer/>
</cscpage>

280
docs/machine_usage.xml Executable file
View File

@ -0,0 +1,280 @@
<?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 &quot;user&quot; implies a user of a
CSC machine, unless otherwise specified.
</p>
<h3><a name="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="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 are subject to the restriction that course, thesis and commercial
work is prohibited. In addition, users must adhere to the CSC's policies
concerning machine usage.
</p>
<h3><a name="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 name="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.<br/>
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 name="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="constitution.shtml">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 name="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.<br/>
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 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
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.
</li>
</ol>
<h3><a name="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="constitution.shtml">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 17 April 1994, 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>

77
docs/machine_usage_summary.xml Executable file
View File

@ -0,0 +1,77 @@
<?xml version='1.0'?>
<!DOCTYPE cscpage SYSTEM "../csc.dtd">
<cscpage title="CSC Machine Policy Summary, 15 February 1995">
<header/>
<section title="Notes">
<p>
Policies for group accounts and administrative accounts are not yet
available (this section will contain links to them when they do become
available). This is a brief (instead of legalese) version of the
<a HREF="policy.shtml">usage policy</a>.
Everyone who receives an account on one of the CSC machines must sign
the agreement based on the usage policy, and this summary lists the
things that the users will agree to.
</p>
</section>
<section title="Summary">
<h3>Use of accounts:</h3>
<ul>
<li>one person only</li>
<li>for hacking, not for course work or cracking</li>
<li>if you're not working on a specially authorized project, don't
abuse system resources</li>
<li>don't abuse other users, either</li>
</ul>
<h3>Security:</h3>
<ul>
<li>again, don't crack</li>
<li>your .rhosts file should only contain your user IDs on CSC and
MFCF machines</li>
<li>don't use passwords that you use elsewhere, and <em>never</em>
tell anyone your password</li>
<li>be secure!</li>
<li>if you find security holes, report them to the sysadmin but
don't blab or try to take advantage of them</li>
</ul>
<h3>The Systems Committee may:</h3>
<ul>
<li>
Examine programs that seem to be violating policy or security;
this includes the following <em>when necessary</em>
<ul>
<li>watching what the program does</li>
<li>looking at the executable and source</li>
<li>looking at files that the program seems to be using</li>
</ul>
(you will be informed if any of this happens)
</li>
<li>Remove accounts with an explanation but no notice (especially
if the user is violating the machine policy)</li>
</ul>
<h3>General:</h3>
<ul>
<li>you are completely responsible for your actions</li>
<li>don't do illegal, damaging, or unethical things</li>
<li>the exec can change their policies with reasonable notice</li>
<li>CSC machines will not be up at all times, and may even crash
while you are using them</li>
<li>if CSC machines cause you to lose time, data, sleep or your SO,
then it's your own tough luck</li>
</ul>
</section>
<footer/>
</cscpage>

19
docs/official.xml Executable file
View File

@ -0,0 +1,19 @@
<?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>

48
docs/website.xml Executable file
View File

@ -0,0 +1,48 @@
<?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 me, that is, <a
href="mailto:sjdutoit@uwaterloo.ca">Stefanus Du Toit</a> and
I'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="Documentation">
<p>Soon I'll hopefully have some documentation here on how to add
content to the website and make other changes.</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>