SPAM code

Christopher Fraser (chrisf@nospam.sour.sw.oz.au)
Fri, 4 Nov 1994 17:10:49 +1100

OK, this is a *very* rough draft but I wanted to get something out before
the meeting.

The name SPAM is a working title. I expect a name will be settled on at the
meeting next week.

Minor corrections and clarifications should be mailed directly to me.
Major stuff should be mailed to the ProgSoc list or brought up at the
meeting next week.

Volunteers to edit this and the AUP into shape would be most welcome.

Glossary:

AGM - Annual General Meeting. We usually have this early first semester.

AUP - Acceptable usage policy. There's a copy of this on ftoomsh on
at (http://ftoomsh.socs.uts.EDU.AU/~chrisf/aup.html). It still
needs some more work and input from other people.

CSO - Computer Systems Officer. A currently vacant ProgSoc office position
with a somewhat undefined role. (I guess Sbg is currently acting
CSO, seeing as he's the one helping Andrew with ftoomsh the most).

SPAM (Society Panel on Acceptable-use Matters)
==============================================

This policy attempts to outline the roles and responsibilities of
users, system administrators, and in particular the members of SPAM
in ensuring that the operation of ProgSoc services are fair, trouble
free and long lasting.

Users
-----

Users should keep aware of and attempt to abide by the terms of
the ProgSoc Acceptable Usage Policy (AUP). If you feel that some
aspect of the operation of ProgSoc machines is too regulated, or
is in need of more control, you should contact either the current
system administrators <system@nospam.ftoomsh> or make a posting to the
ProgSoc mailing list.

If you believe that some other user is being unfair in their use
of system resources, you should either take the matter up with user
in question or talk to the current system administrators. Directs
violations of the AUP you should be reported to both the current
system administrators and members of SPAM <spam@nospam.ftoomsh>. Random
allegations of wrong doing should not be posted to the ProgSoc list
-- if nothing else it's potentially libelous.

System Administrators
---------------------

As well as usual administration duties, the system administrators
are responsible for bringing matters to the attention of SPAM,
collecting information as required by SPAM and for enacting their
decisions.

If a system administrator believes that an account may be involved in
a breach of security or AUP they may lock that account while the matter is
assessed by SPAM. Matters which may be of concern to SoCS or ITD they should
reported to that party.

SPAM
----

SPAM is responsible for interpreting the AUP, and should (as much as
possible) be independent of the ProgSoc executive and system
administrators.

The membership of SPAM is selected every year at the Society AGM. Further
elections may occur as positions become vacant (at the discretion of the
current SPAM). There are usually 3-5 elected members of SPAM. When active
membership falls below three an election must be called.

It is required that members of SPAM be able to respond to a matter brought
before the SPAM within one weeks notice. Members may resign with two weeks
notice (or less under exceptional circumstances).

A majority of elected SPAM members must not also be members
of the ProgSoc executive. A person currently holding the positions
of system administrator or CSO cannot also be a member of SPAM.
The current ProgSoc President is always an appointed member of SPAM,
but only has voting power to resolve cases of tied votes.

Matters brought before SPAM can be:

* Dismissed as being trivial, acceptable usage or completely unintentional.
If the account in question is currently locked it must be unlocked.

* Judged to be in breach in the AUP. SPAM should then determine the
appropriate action(s) to be carried out.

* Referred to the ProgSoc list for further discussion.

SPAM can only interpret matters covered by the scope of the AUP. Matters
outside this need to be referred to the membership for approval.
SPAM members should take an active role in forming the AUP.

SPAM can recommend a variety of actions, depending on how serious the breach
of the AUP was and to what extent was malicious or irresponsible:

* trivial: person in question gets a warning.

* minor: banned from using ProgSoc machines for for period
of time (typically 2 months). During this time the account remains locked.
Any attempt to use any other persons account will result in loosing
account permanently. Any files owned by the account may be deleted at the
discretion of SPAM.

* anything else: loose account. All files deleted etc. In this case files
owned by the account should be kept for a period of two weeks before
being terminated with extreme prejudice...

Once someone has lost their account, it can only be got back by
petitioning at the next AGM and having a vote of confidence passed.

TODO:

* How should someone be called upon to defend themselves?

* Appealing against a decision by SPAM?

* Identifying contacts within SoCS and ITD.

-- 
Christopher Fraser   ``First time surrealists are often confused by the
chrisf@nospam.sw.oz.au        similarities between fish and telephones.''