Board Meeting Notes 2019-10-01: Difference between revisions
From Pumping Station One
Kathryn007 (talk | contribs) |
No edit summary |
||
| (21 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Board Meeting Notes | {{Board Meeting Notes | ||
| Previous YYYY-MM-DD= | | Previous YYYY-MM-DD= 2019-09-17 | ||
| Next YYYY-MM-DD= | | Next YYYY-MM-DD= 2019-10-15 | ||
| YYYY= | | YYYY=2019 | ||
}} | }} | ||
| Line 9: | Line 9: | ||
== Attendance == | == Attendance == | ||
* Board Members | * Board Members | ||
** | **Kathryn B | ||
** Ese O | |||
** Andrew C | |||
** Molly A | |||
* Other Members | * Other Members | ||
** | ** Ron O | ||
== Agenda == | == Agenda == | ||
| Line 18: | Line 21: | ||
* Check talk page for board meeting notes, see if any discussion on the agenda took place | * Check talk page for board meeting notes, see if any discussion on the agenda took place | ||
* Consent Agenda | * Consent Agenda | ||
** Are meeting minutes good? | |||
*** vote = okey dokey | |||
* Committee Reports | * Committee Reports | ||
** No reports or reporters from MMT | |||
** MMT - amp up the focus on prep for Open House Chicago-- MMT owns this. Need volunteer spreadsheet. Ese is going to the training; he will collaborate with Joe. | |||
** continue to review written materials ; share a drive so we can do better document collaboration (make a folder in BoD); we may offer to do a 2-hour workshop to "bang it out" -- combine old drafts with new drafts? Orientation needs to be finalized before open house -- workshop with Ese and Andrew around October 12. | |||
** scholarship review - discussed biweekly (alternate weeks) communication. 2 named applicants (both scholarships approved), 1 speculative/delayed. We should write an SOP about how we review these and communicate. | |||
* Read mail | * Read mail | ||
* Financial/membership report | * Financial/membership report | ||
* Review the PayPal and banking transactions | * Review the PayPal and banking transactions | ||
* Member leaving reason reports | * Member leaving reason reports | ||
* Check | * Check Fresh Desk queue | ||
* New business | * New business | ||
* Old business | * Old business | ||
| Line 30: | Line 39: | ||
=== Discussion on previous minutes === | === Discussion on previous minutes === | ||
Notes are here https://wiki.pumpingstationone.org/Board_Meeting_Notes_2019-09-17 | |||
=== Consent Agenda === | === Consent Agenda === | ||
| Line 40: | Line 50: | ||
=== Financial Report === | === Financial Report === | ||
* '''Chase Checking:''' | * '''Chase Checking:''' 9,471.63 | ||
* '''Chase Savings:''' | * '''Chase Savings:''' 154,974.35 | ||
* '''PEX:''' | * '''PEX:''' 17,586.05 | ||
* '''PayPal:''' | * '''PayPal:''' 14,104.78 | ||
=== Membership Report === | === Membership Report === | ||
| Line 49: | Line 59: | ||
* '''Number of Members:''' | * '''Number of Members:''' | ||
* '''Quorum:''' | * '''Quorum:''' | ||
** Gary N to switch from red ticket to ops committee | |||
=== Review the PayPal and banking transactions === | === Review the PayPal and banking transactions === | ||
| Line 58: | Line 70: | ||
=== New Business === | === New Business === | ||
* Power Hammer Vote | * Power Hammer Vote-- approved. KB needs to do the paperwork. | ||
* Welding reimbursement timeline | * Welding reimbursement timeline. The delay was auditing the check date. | ||
* Wild Apricot - for scheduling; | * Wild Apricot - for scheduling; | ||
**separate projects- functionality and/or authorization tracking | |||
*** lets' talk about checking authorization boxes. Either makes duplicate requests. What about giving WA access? Does it give ability to wipe out databases? Volunteer authorizer's hands are tied. Ron "wrote a program to do just that." Yea, Ron. He can do something where you type in name, and it saves it into WA. This is quite awesome. Currently a little out of whack when added new equipment. Ron will return to the project. | |||
**separate projects- functionality for seeing auth events in calendar view vs/and/or authorization tracking | |||
*** OK, so here are the options for auth automation, even including quizzes | |||
*** 4 ways | |||
*** event on google calendar | |||
*** event on meetup (problematic) /(calendar connects to our calendar) | |||
*** WA - has calendar, also public -- connects to app that tracks checkins-- *** 3 tiers, member discount | |||
***Canvas- canvas event -- | |||
*** Dream is widget - pings WA or AD -- do you have this auth... can tie into actual machine. | |||
*** So to look at this overarching issue from a project management perspective, what can we do in parallel. Can we make life easier for authorizers while we work on a web calendar that shows ALLLLLLL (every single one) of the authorizations scheduled for October. | |||
* Spitball - like a block party where 10 people have to endorse. We can talk about a future meeting. With new voting system, what are the dynamics or quorum and things passing. What will future trends show us? Can we do financial "load balancing" between the 9 areas. What if one area had 90% of the member vote budget. | |||
* Dust collection - waiting on electrical | |||
* incident needs us to write a DRC report. | |||
* Pet Policy - needs further discussion | |||
* Jim B has a bill that needs to be paid, pls email it to expenses@... Needs to get card replaced. | |||
*** Kathryn wants award for most avand garde use of bullet points. | |||
* Reminder - something about authorizers for next week- topic unknown | |||
=== Old Business === | === Old Business === | ||
== Votes == | == Votes == | ||
