Standing Orders

Committee Matters

  • Committee business should not be discussed outside of committee, unless specifically decided so by the committee.
  • Collective responsibility should apply for all committee decisions. Individual committee members should not express views at odds with those decided upon by the committee.
  • General correspondence should as much as possible be dealt with by the Secretary. Drafts of responses on major issues should ideally be discussed on the list before being sent to the members.
  • Members seeking an official committee response should either post to the .committee board, or email committee@redbrick.dcu.ie.
  • A post by a committee member to the boards will only be considered as official if it is made from a committee account.

Meetings

  • At the beginning of each year, there should be a 1 hour slot set aside for a weekly committee meeting.
  • These meetings should begin with the secretary taking attendance, and the chair providing a summary of who has been excused from the meeting.
  • Minutes from the previous meeting should ideally be provided to committee members within a week of the meeting.
  • These minutes must be approved at the begining of the next meeting.

Systems Administrators

  • Only those who have been elected admins may be added to the official mailing list (rb-admins).
  • All root holders must be members of this list.
  • Previous admins may remain on the list, at the sole discretion of the elected admins.
  • If the Webmaster is a root holder, he must be a member of the list.
  • Root and other passwords should ideally be changed every 6 months

Redbrick Policy on the Abuse of Non-quota Based Filesystems

  • Individuals placing copyrighted material (which they do not have permission to use), or other materials which contravene Redbrick, CSD or HEAnet Acceptable Usage Policy will have write permission revoked and the files deleted. Deletion should be delayed until it is confirmed the user does not have permission, but the file should not be publically readable unless it has been confirmed.
  • Individuals abusing the lack of quota (at the discretion of admins, to be reviewed by committee in case of complaint), will have their write permission revoked and the file(s) deleted.
  • In the event of an abuse of the unquotad nature, if it can be proven to be accidental, then write permission will be restored when the faulty script/program has been altered. At the discretion of the admins, a quota may be imposed on that user in addition to/instead of revoking write permissions for the relevant filesystem, for a time period at the discretion of the admins.

Guest Accounts

  • Application for a guest account must be made by email to the committee.
  • It must be shown that the prospective guest account would make some contribution to the society.
  • Guest accounts are bound by Redbrick operational regulations under constitution article 10.6 and do not hold voting rights at meetings.
  • Guest accounts will be charged at a level set by the Office of Student Life, although this will be an amount no less than that charged for an associate.
  • Guest accounts are reviewable at any time by the Committee
  • Guest accounts may only be held by those not eligible to hold a member, associate or staff account.

Disuserment Policy

  • Disuserment shall be the sole prerogative of the committee.
  • Disuserment shall be issued on the basis of abuse of society resources, or on the basis of constant abuse of society members.
  • Where necessary, an admin may disable the account of a member while the committee is deliberating. This should only be for cases of serious abuse of system resources.