Resources‎ > ‎

Standard Procedures


There are a number of standard operational procedures at ViSLAB to make sure things run smoothly. Every member of ViSLAB should be familiar with these procedures.  


Create your personal page

If you wish to create a separate web-site, you can follow the instructions under "Create your site".

Create your blog

If you wish to create a separate blog hosted at blogger.com you can follow the instructions under "Create your blog @ blogger.com".

Create a project page

If you wish to create a separate web-site, you can follow the instructions under "Creating project site".

Creating an Information Page



Communication

Communication is a very common theme at ViSLAB and we use a number of forms to make sure that information is shared and stored efficiently.  Work that is not accessible may as well not exist and not have been done.  Obviously, as well as the methods outlined below, you can always stop by to talk to someone.


IM (Instant Messaging)

IM is used for informal communication. Think of IM as dropping by and having a chat. All ViSLAB staff/students should have Google Talk running while they are at work, so it is a good way to see if they are available and to ask a few quick questions. IM meetings can also be organised and are useful because the meeting log can be stored and refered to later.

To configure Google Talk, see Using Google Talk.


Email

Email is used mostly for formal communication.  Make sure to use email for formal requests or notification.

All ViSLAB users have Gmail account (username@vislab.net).  If you wish not to use your ViSLAB email as your regular email destination, you should set an appropriate auto-forward email address under your vislab.net Gmail account.

If you wish to email out to all ViSLAB members, please use vislab@vislab.net.  

Meetings

ViSLAB meetings are held every week on Thursday at 1pm in the SIT Boardroom.  It is a forum for interactive presentation and discussion.  All members of ViSLAB (staff and students) are encouraged to give presentation at meetings.  For students, at least one presentation is expected at the end of the project term.

Proxy

All outgoing port 80 traffic is blocked at the University border; you need to use a proxy.  
  • If your computer is connected to ViSLAB network, you can do one of followings:
    • use the auto configuration script at http://sydney.edu.au/proxy.pac
    • use the explicit proxy (web-cache.usyd.edu.au:8080)
  • If your computer is connected to SIT network, you can do one of followings:
    • use the auto configuration script at http://www.it.usyd.edu.au/proxy.pac
    • use the explicit proxy (www-cache.it.usyd.edu.au:8000)
For programs like command-line tools (w3m, wget, etc.), set the following environment:
export http_proxy=http://www-cache.sydney.edu.au:8080/
or
export http_proxy=http://www-cache.it.usyd.edu.au:8000/


Printing


Passwords


Backups

All project directories, your home directory, and only your ViSLAB home directory is backed up; this can be recovered, see and administrator for help. If you would like to back up files/folders from your local machine, you are encouraged to back them up onto your ViSLAB home directory.  The following tools might be useful for doing backup:

Project Repository (git, subversion)

All ViSLAB projects should use git or subversion for code/document management. This means that anyone else at ViSLAB can use and contribute to your code.  For students, code submission logs can be used as reference when marking (and marks for group projects can be weighted accordingly if discrepancies arise)

See also: git and subversion