This is an old revision of the document!


BOTLab AGM and members' meeting 28 March 2017

Date/time and location: 7pm, 28 March 2017 at the Hackspace

  • AGM
    • Vote on proposed system for election of new committee members - see this page
    • Presentation of annual accounts for members' approval - draft accounts here
    • Committee report on previous year and objectives for next year
    • Appointment of new committee members
  • Food!
  • Members' meeting
    • What to do about the Hardinge lathe?
    • How to encourage involvement in inductions/maintenance for Hackspace tools?
    • Incident log for accidents and near misses

Toby Se, Tarim, John W, Pam D, Russell D, John D, Richard L, Arthur A, Russ C, Nic M, David W (minutes-taker), Ian A-S

Apologies: Nick G, David H

  • AGM
    • Vote on proposed system for election of new committee members
      • JW: how do we set the maximum number of committee members? Constitution doesn't specify a maximum.
      • T: Distinction between Committee and Directors - AGM exists to elect Directors, not necessarily the same as committee. Currently they are the same. Likewise BOTLab membership is the same as Hackspace membership.
      • TS: Maybe say 6 as an arbitrary upper limit? IA-S: maybe relate to the number of members? T: limit #directors to 5 to avoid deadlock but allow directors to appoint arbitrary numbers of resposibility positions. DW: Directors set
      • TS: Odd or even number of directors? All: Odd.
      • IA-S: felt more responsibility by being elected as a director rather than a
      • Vote in favour of setting 5 directors: Unanimous
      • Who has responsibility for approving proposals?
      • PD: could bring in sub-committees to deal with specific matters - IAS:
      • IAS: How are committee members appointed? By majority of directors
      • AA: If committee exists, would consider stepping down as director and becoming a . IAS: directors do have liability, they have been conscious of this, but insurance limits this? TS: Insurance doesn't cover if we act negligently. JW: feels strongly that unpaid directors should not have liability in this situation. TS: maybe goal for year is to engage with other hackspaces and understand how their liability is managed.
      • PD: Emphasises H&S during tours of the space for new members but would help if there was a booklet or other formal information on ground rules, where to report broken items/accidents, provide a point of contact.
      • JW: Also need a members' agreement for people to sign when they join - make it clear the hackspace doesn't have a “manager” who takes responsibility - make them aware of responsibilities.
      • Voting system: Approved unanimously.
    • Presentation of annual accounts for members' approval
      • JW: Should we record laser credit balances separately? Is it the case that people would be owed their money back if we couldn't provide the . DW: Was not made clear initially. TS: Should be made clearer next time a similar big fundraising drive happens, the terms on which people are contributing money. IS: Should be broken out and recorded separately for reference.
      • Approved unanimously.
    • Committee report on previous year and objectives for next year
    • Appointment of new committee members
      • IAS is chosen by drawing lengths of wire to stand for reelection
      • IAS, NG and RC are unaimously elected to driectors
  • Food!
  • Members' meeting
    • What to do about the Hardinge lathe?
    • How to encourage involvement in inductions/maintenance for Hackspace tools?
    • Incident log for accidents and near misses
    • AOB:
      • bristol@hackspace.org.uk email address
  • botlab/agm_20170328.1490728460
  • Last modified: 3 years ago
  • by dwyatt