Team:Membership: Difference between revisions

From Nottinghack Wiki
Jump to navigation Jump to search
Layjet (talk | contribs)
mNo edit summary
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Team
{{Team
|trustee=[[User:Layjet|James Taylor]]
|members=[[User:Kate|Kate Bolin]], [[User:Elsen|Sophie Wilinson]], [[User:Froggy|Adam Froggatt]], [[User:Matinglinksys|Toby Jackson]], [[User:Mousetad|Matthew Gates]], [[User:Robert|Rob Hunt]], [[User:freekyboyal|Alex Wells]], [[User:Layjet|James Taylor]], [User:iandickinson|Ian Dickinson]]
|email=membership@nottinghack.org.uk
|email=membership@nottinghack.org.uk
|budget=£285.00
|budget=
|discord=https://discord.com/channels/1016848183726448660/1053102740798185522
|hms=https://hms.nottinghack.org.uk/teams/27
|started=September 2015
|started=September 2015
}}
}}
Line 12: Line 12:
=== Scope ===
=== Scope ===
The Membership Team is responsible for:
The Membership Team is responsible for:
* Tours for prospective members on Open Nights, and training other members on how to provide adequate tours
* [[Open Night Tours|Tours for prospective members on Open Nights]], and training other members on how to provide adequate tours
* Assist Trustees in running Open Days/parties
* Assist Trustees in running Open Days/parties
* Ensure the wiki is up to date on enrolling new members on HMS
* Ensure the wiki is up to date on enrolling new members on HMS
* Ensure the wiki is up to date with useful new member information
* Ensure the wiki is up to date with useful [[New Members]] information
* Set up RFID cards for new members
* Set up RFID cards for new members
* Respond to emails sent to membership@nottinghack.org.uk  
* Respond to emails sent to membership@nottinghack.org.uk  
* Check and approve contact details submitted by members
* Check and approve contact details submitted by members
* Audit members’ boxes to ensure ex members boxes are emptied
* Audit [[Members Storage]] boxes to ensure ex members boxes are emptied
* Updating the Member Handbook
* Updating the Member Handbook
* Assisting with the in depth tours for new members on “using the space”
* Assisting with the in depth tours for new members on “using the space”
Line 37: Line 37:


=== Issues: ===
=== Issues: ===
There must be at least 4 people on the Membership Team to ensure one person can attend once per month on a Wednesday. Solution: Rota to be in place to ensure coverage. Slack to be used to discuss absences
There must be at least 4 people on the Membership Team to ensure one person can attend once per month on a Wednesday. Solution: [[Team:Membership/Rota | Rota]] to be in place to ensure coverage. Discord to be used to discuss absences
If the Membership Team fails, new members may not receive a high quality tour on arrival. Solution: Ensure tour handbook is up to date and those members giving tours are comfortable and aware of the handbook.
If the Membership Team fails, new members may not receive a high quality tour on arrival. Solution: Ensure tour handbook is up to date and those members giving tours are comfortable and aware of the handbook.
If the Membership Team fails, new members may not be able to receive their RFID card and be inducted into the space. Solution: Ensure this process is documented and accessible via Discourse/elsewhere
If the Membership Team fails, new members may not be able to receive their RFID card and be inducted into the space. Solution: Ensure this process is documented and accessible via Discourse/elsewhere
Line 49: Line 49:
* Be understanding of different cultures and capable of dealing with people without causing offence
* Be understanding of different cultures and capable of dealing with people without causing offence
* Be able to attend at least 1 out of every 4 Wednesday evenings
* Be able to attend at least 1 out of every 4 Wednesday evenings
* Be able to attend Open Days/Events as much as possible, discussing presence required on Slack beforehand
* Be able to attend Open Days/Events as much as possible, discussing presence required on Discord beforehand
* Be comfortable using Slack as a means of communication
* Be comfortable using Discord as a means of communication
* Be happy to follow the guidelines in the Hackspace Tour Guide without deviating off the content outlined in the guide to any extreme
* Be happy to follow the guidelines in the Hackspace Tour Guide without deviating off the content outlined in the guide to any extreme
* Be clean and well presented in order to provide prospective Hackspace members with a good impression of the Hackspace
* Be clean and well presented in order to provide prospective Hackspace members with a good impression of the Hackspace


=== You will be removed from the Membership Team if: ===
=== You will be removed from the Membership Team if: ===
You fail to attend your allocated Wednesday monthly/Open Day without good cause
*You fail to attend your allocated Wednesday monthly/Open Day without good cause
You fail to respond to important queries from the other members of the team/emails by the deadline given in each email.
*You fail to respond to important queries from the other members of the team/emails by the deadline given in each email.
You behave inappropriately towards other members of the Hackspace/prospective members
*You behave inappropriately towards other members of the Hackspace/prospective members
You go AWOL for 10 weeks with no notice on Slack or via email communication
*You go AWOL for 10 weeks with no notice on Discord or via email communication


=== Membership Team members will: ===
=== Membership Team members will: ===
Line 66: Line 66:
* Have access to HMS in order to check PIN numbers and assign new RFID cards for members
* Have access to HMS in order to check PIN numbers and assign new RFID cards for members
* Be able to reset PIN numbers for members that have lost their RFID card/got a new card
* Be able to reset PIN numbers for members that have lost their RFID card/got a new card
* Have access to the Membership Slack
* Have access to the Membership Discord
 
=== Rota for weekly Membership Tours ===
[[Team:Membership/Rota | Weekly Rota]]
 
[[Category:Teams]]
[[Category:Teams]]
[[Category:Member admin]]
[[Category:Member admin]]

Latest revision as of 19:04, 10 October 2023

Membership team
Started September 2015
Email membership@nottinghack.org.uk
Discord Membership channel
Slack [{{{slack}}} Membership channel] (deprecated)
Lead {{{lead}}}
Members Team members listed on HMS.
HMS page Membership Team on HMS
HMS page (2) [{{{hms2}}} Membership Team on HMS (2)]
Budget
Status Dissolved
Teams:   Aboutall pages        {{}}

3D PrintingBikeCommsCraftElectronicsInfrastructureLaserMembershipMetalworkingNetworkResources and SnackspaceSafetySoftwareToolsWoodworking

Aim

The aim of the Membership Team is to be first response for all membership queries by email, as well as handle tours and any queries relating to membership by users.

Scope

The Membership Team is responsible for:

  • Tours for prospective members on Open Nights, and training other members on how to provide adequate tours
  • Assist Trustees in running Open Days/parties
  • Ensure the wiki is up to date on enrolling new members on HMS
  • Ensure the wiki is up to date with useful New Members information
  • Set up RFID cards for new members
  • Respond to emails sent to membership@nottinghack.org.uk
  • Check and approve contact details submitted by members
  • Audit Members Storage boxes to ensure ex members boxes are emptied
  • Updating the Member Handbook
  • Assisting with the in depth tours for new members on “using the space”
  • Completing monthly member audits, warning members when a payment is not received and removing members after 2 months of non-payment, to allow for account issues/transfers/missed payments et al.
  • Monitoring stock of RFID cards and Membership Boxes
  • Purchasing additional RFID cards and Membership Boxes

The Membership Team is not responsible for:

  • Running workshops or events
  • Sending out the newsletter/communications (responsibility of the Communications Team)
  • Marketing to new members

Timescales:

  • Email queries must be responded to within 48 hours
  • Contact details must be approved within 24 hours
  • One member of the membership team needs to be in the space every Wednesday, from 6:30pm until 9:00pm.

Issues:

There must be at least 4 people on the Membership Team to ensure one person can attend once per month on a Wednesday. Solution: Rota to be in place to ensure coverage. Discord to be used to discuss absences If the Membership Team fails, new members may not receive a high quality tour on arrival. Solution: Ensure tour handbook is up to date and those members giving tours are comfortable and aware of the handbook. If the Membership Team fails, new members may not be able to receive their RFID card and be inducted into the space. Solution: Ensure this process is documented and accessible via Discourse/elsewhere If the Membership Team fails, new members may not be approved or given the correct information to set up their standing order. Solution: Ensure this process is documented and accessible via Discourse/elsewhere Solutions are in place to ensure these points of failure do not occur. Support may be needed from other members/Trustees on recruiting high quality staff for the team.

Person Specification

In order to be on the Membership Team, you must:

  • Be fluent in English
  • Be confident when dealing with people of varying ages and backgrounds
  • Be understanding of different cultures and capable of dealing with people without causing offence
  • Be able to attend at least 1 out of every 4 Wednesday evenings
  • Be able to attend Open Days/Events as much as possible, discussing presence required on Discord beforehand
  • Be comfortable using Discord as a means of communication
  • Be happy to follow the guidelines in the Hackspace Tour Guide without deviating off the content outlined in the guide to any extreme
  • Be clean and well presented in order to provide prospective Hackspace members with a good impression of the Hackspace

You will be removed from the Membership Team if:

  • You fail to attend your allocated Wednesday monthly/Open Day without good cause
  • You fail to respond to important queries from the other members of the team/emails by the deadline given in each email.
  • You behave inappropriately towards other members of the Hackspace/prospective members
  • You go AWOL for 10 weeks with no notice on Discord or via email communication

Membership Team members will:

  • Have access to HMS in order to register new members
  • Have access to HMS in order to approve contact details
  • Receive the membership@nottinghack.org.uk emails
  • Have access to HMS in order to check PIN numbers and assign new RFID cards for members
  • Be able to reset PIN numbers for members that have lost their RFID card/got a new card
  • Have access to the Membership Discord

Rota for weekly Membership Tours

Weekly Rota