Board Meeting - August 8th, 2022: Difference between revisions

From Hive13 Wiki
Jump to navigation Jump to search
No edit summary
Line 12: Line 12:
*Intweb
*Intweb
*Member Tours & Signup Process
*Member Tours & Signup Process
*Member storage space assignment
*Leadership Communications etiquette  
*Leadership Communications etiquette  
**ALWAYS thread responses in slack #announcments channel, it's the one channel members can't choose to leave, and only leaders can post in.
**ALWAYS thread responses in slack #announcments channel, it's the one channel members can't choose to leave, and only leaders can post in.
Line 20: Line 21:
*Get an @hive13.org email if you don't have one.
*Get an @hive13.org email if you don't have one.
*Add your contact details to the Leadership Contacts to the extent that you are comfortable.
*Add your contact details to the Leadership Contacts to the extent that you are comfortable.
*Conflict of Interest Statements. Please sign and return.
===Finance Issues===
*Warden budget now needs to be determined and voted on.
*Warden discount status.
**No longer in bylaws.
**Are we still doing it? Should we?


===Discourse for Leadership and Warden emails===
===Discourse for Leadership and Warden emails===
Line 40: Line 49:
=== Reporting Problems ===
=== Reporting Problems ===


* messes left behind
* Messes left behind
* safety problems
** How do we encourage improvement? Preferably continuous improvement.
* unattended guests
* Safety problems
* Unattended guests
* IDKWTFs
* IDKWTFs



Revision as of 00:00, 7 August 2022

Board Meetings
Previous: July 11th, 2022 Meeting Procedure Next: September 12th, 2022

Time: 7:30 PM
Place: Google Meet Telecom
To join the video meeting, click this link: https://meet.google.com/bdr-rjhv-cbk
Otherwise, to join by phone, dial [302-751-5581|+1 302-751-5581] and enter this PIN: 260 934 004#
To view more phone numbers, click this link: https://tel.meet/bdr-rjhv-cbk?hs=5

Agenda

New Leader Orientation

  • Intweb
  • Member Tours & Signup Process
  • Member storage space assignment
  • Leadership Communications etiquette
    • ALWAYS thread responses in slack #announcments channel, it's the one channel members can't choose to leave, and only leaders can post in.
      • There are a very few but genuine exceptions. COO will explain.
    • Keep ALL conversation not directly related to a confidential topic out of #leadership_private, if not security/privacy sensitive, all discussion should be in #leadership_discussion.
    • CC leadership@hive13.org on official business emails so others know what is being taken care of and what still needs responses.
    • Where possible use a handle/login that clearly identifies who you are. Your name not you position.
  • Get an @hive13.org email if you don't have one.
  • Add your contact details to the Leadership Contacts to the extent that you are comfortable.
  • Conflict of Interest Statements. Please sign and return.

Finance Issues

  • Warden budget now needs to be determined and voted on.
  • Warden discount status.
    • No longer in bylaws.
    • Are we still doing it? Should we?

Discourse for Leadership and Warden emails

  • Discourse seems ill-equipped for handling leadership and warden email
    • HTML messages get broken
    • Reply and CC features break threading of responses
    • Reply formatting is broken, replaces email context with discourse links and styling, does not present cohesive response experience outside our organization
  • Can it be made better? Can/should we switch leadership and wardens emails back to google groups till we figure it out?

HVAC

  • AC was never actually designed to handle our space and functions.
    • We got the largest units that would work with our furnaces.
  • Barely keeping up on hot days.
    • Humidity and the heat of the building itself big parts of the problem.
  • Maintenance? Set up annual checkup with AC fund drive reserves?
  • Possible window coverings for the front windows.

Reporting Problems

  • Messes left behind
    • How do we encourage improvement? Preferably continuous improvement.
  • Safety problems
  • Unattended guests
  • IDKWTFs

Status of Pending Requests on Intweb

  • 7 pending applications
  • 2 pending storage requests


Minutes

Attendees

Discussion Notes

Action Items