Emergency Decision Making (2 days or more) Policy
- Emergency decisions can be made over email.
- Emergency decision making will follow the same consensus procedure as our regular decision making, except where changes have to be made to accommodate email communication, as detailed below.
- Emergency decisions will be made by the Collective.
- The Collective will consist of active members who wish to participate in this kind of decision making, and the list of members on the Collective will be updated regularly.
- A proposal can be put forth for consideration by the Collective by emailing the everyone on the Collective.
- Timeline: the proposal must be put forth at least 2 days in advance of the decision deadline, and before the next meeting (otherwise it should be discussed at the meeting).
- The Collective should only deal with real emergencies, something that can't wait - it shouldn't be something you simply forgot to bring up at a meeting.
- Proposals can amended and modified through discussion over email. Anyone participating in the discussion should "Reply All" so that everyone can see their input. We will eventually set up a proper mailing list to make this an easier process.
- A proposal will be passed when a quorum of members has emailed their assent or abstention, which can be signalled by expressing agreement, non-support, reservations, or standing aside (see consensus procedure for definitions)
- Quorum consists of half of the members of the Collective list (rounding down in case of an odd number) + 1. E.g. if there are 15 people on the list, quorum = 7.5+1, which rounds down to 8.
- If quorum is not reached the proposal cannot be passed.
- Any Collective member can block a proposal by explicitly stating in an email that they block the proposal.
Emergency Decision Making (under 2 days) Policy
- If a decision needs to be made in less than 2 days, the decision can be made by an RSSC member.
- A note must left in the Social Centre immediately, explaining the decision.
- A full explanation of the decision must be emailed to the Collective list as soon as possible, and not later than 24 hours after the decision has been made.
- All emergency decisions will be reviewed and discussed at the following Social Centre general meeting.
Grants Policy Grant criteria:
- Grants should be for projects rather than operational funding, although grants can contribute to some administrative expenses. We don't want to be dependent on grants for funding.
- Grants must be for projects that help us fulfill our mandate
Grant application process:
- Projects and grant applications should be developed at other meetings, then brought to a Social Centre meeting for further discussion and approval, if there is time to do this before the grant deadline.
- If there isn't time to bring grant to a Social Centre meeting, the Collective should be e-mailed about it and asked for suggestions and concerns. If concerns are expressed that need to be discussed in person, we can call a meeting. If there are no unresolved concerns the grant application can go through.
Policy for Upstairs Guests
1. Guests should look for other options first.
2. A RSCC member can ask for a guest to stay at in the Crow's Nest space by making a proposal at as RSCC General Meeting, or by making a proposal over email to the Collective.
3. A proposal must be made at least one week in advance of the guest's arrival.
4. The proposal must include:
4.1. clear arrival and departure dates (there is a maximum stay of 3 nights)
4.2. how the guest will contribute to the Social Centre (e.g. financially, or by providing a service like cleaning, giving a workshop, fixing something)
4.3. the name of an RSCC member who is sponsoring (and taking responsibility for) the guest. The guest's sponsor is responsible for the guest's conduct while they are staying at the centre, and for cleaning up after they leave.
5. The guest must be informed of our expectations of them, which are:
5.1. Keep the Crow's Nest, kitchen and bathroom tidy.
5.2. Do your dishes.
5.3. Put away your belongings and bed before you leave for the day, and before people come up to use the Crow's Nest, if it's booked.
6. The space is not being offered as a residence; RSSC events are first priority.
7. An email reminder should be sent to the Collective list a day before the guest arrives.
8. A note with the guest's name and dates he/she will be staying should be posted on the door to the Crow's Nest (in the kitchen) for the duration of the guest's stay.
9. For longer term planning, it would be a good idea to coordinate with the calendar committee and residency committees by email.
Key Policy
The Ink Storm and Anchor Archive key policies both require that someone:
- request a key at a meeting,
- make a $20 deposit for the key,
- fill out a key-holder's form, including name, phone, address, and other pertinent contact info,
- will not copy or loan out the key to non-key-holding members,
- understand that this is a privilege and will be a responsible key holding member.
The Ink Storm Screenprinting Collective requires that someone:
- has taken an orientation, intro, or a three-part screen printing class at Ink Storm,
- has shadowed an Ink Storm member during open hours,
- has done at least three shifts of open hour duties,
- will attend monthly meetings as often as possible, send regrets when they cannot, and share in Ink Storm duties,
- will return their keys after four months without involvement.
The Anchor Archive Regional Zine Project requires that someone:
- work four volunteer shifts,
- will have their key revoked after one year without working a shift.
The Roberts Street Social Centre Collective requires that someone:
- has been involved with the Collective for at least 4 months,
- has come to at least 2 Collective meetings,
- has taken on a role or joined a committee,
- has a role or task that requires access to the building.
Exceptions can be made to the above criteria if the Collective agrees.