Member Meeting Agenda for Apr 16, 2019

From HackPittsburgh Wiki
Revision as of 16:34, 6 May 2019 by SimonH (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

HackPGH member’s meeting agenda for March 19, 2019

Call to order

Welcome New members

Quote

PSA’s

  • Don't leave heckin' box cutters and razors lying around

Past events

Events for April

  • Shop clean, the April 28th
  • Next meeting, May 1st

Old business

  • Phone number???
  • Mailing List: Monthly mailing lists etc. Being set up by Simon.
  • Swag: T-Shirts, stickers, swag in limbo. Still in progress.
  • HackPGH Birthday Party - June 1
  • Heckin' dust collection
  • Need to get the 3D box given away
  • Need FAQ poster -- Opening and closing shop, membership guidelines, donation guidelines, tool usage, safety stuff locations, who to contact for stuff
  • Need tool training docs

New business

  • We have a server!
  • We need to crack down on donations -- when we literally aren't getting rid of junk fast enough, it's a problem.
  • RFID tool lockouts
  • More shop vacs?
  • We honestly need a suggestions/complaints box

Shop updates

  • Talked to Dale about the ceiling. He doesn't want to just throw in a drop ceiling and call it a day, as the building owner he wants to Do It Right. Fire code issues, ventilation, etc.
  • Dale also has concerns about indoor air pollution, wants to talk with the Board about some sort of solution there
  • The door latch will be installed whenever his contractor gets to it but they're busy with the bathroom -- it's on their to-do list
  • We have permission to do pretty much whatever we want with the door and our area around it -- paint, put up Cool Maker-y Stuff, etc. Can we find/make a bunch of gears and make some sort of interlocking mural or something?

Voting items

  • Make it official -- board members who are spouses/financially dependent on each other can't approve each other's expenses
  • Make it official -- elections have to be run by someone who is not running and NOBODY else should have access to them


Project updates