--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/MHMC/2024-08-29/notes.xml	Tue Apr 29 15:47:02 2025 +0100
@@ -0,0 +1,119 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE doc PUBLIC "-//Henry S. Thompson//DTD doc//EN" "d:\\lib\\xml\\doc.dtd" >
+<doc xmlns:x="http://www.w3.org/1999/xhtml">
+ <head><title>MEK Meeting 2024-08-29</title><author>Henry S.
+Thompson</author><date>Tuesday 29 August 2024<x:br/>7 Victoria Terrace</date><style>.a::before {content: "ACTION: "; font-weight: bold}</style></head>
+ <body>
+  <div>
+   <title>Attendance</title>
+   <p>Eliza Giles (EG), Ken Latham (KL), Majk Stokes (MS), Henry S. Thompson
+(HST)</p>
+  </div>
+  <div>
+   <title>Report on MHMC meeting 2024-08-27</title>
+   <p>HST shared aspects of the Committee's meeting:</p>
+   <p>C'ttee very pleased with staff's stepping up in challenging
+circumstances.</p>
+   <p>MS to be given the title of Acting Manager</p>
+   <p>Salary uplift to continue until new Manager in place, at least through
+October.</p>
+   <p>Interviews and appointment of new casual staff can be done for October if
+it's clear that help is needed due to bookings received.</p>
+   <p class="a">MS to move forward with carpet</p>
+  </div>
+  <div>
+   <title>Staff feedback on the last seven weeks</title>
+   <div>
+    <title>Problems</title>
+    <p>A number of missing or broken items. Consumables were often missing; loo roll
+didn’t arrive until 15/8, soap often missing. E.g. one Sunday when no loo roll in any of the
+loos.</p>
+    <p>We had to do some emptying of bin bags.</p>
+    <p>WiFi - This impacted our own ability to do our own work, because of
+low bandwidth and/or ‘no internet’</p>
+    <p>Kitchen - Not our cleaners job, did CV expect it? MEK cleaned it
+from time to time: sweeping and wiping surfaces. Performers in there? Gap(s) in
+the licence. Food out, so mice flourished. Fridge available? “You have to name
+and date your food, or we’ll through it away”. Buckets left with dirty water
+in.</p>
+    <p>Use of kitchen by them as an office
+made cleaning difficult.</p>
+    <p>Weekend cleaning is necessary, doesn't appear to have been happening,
+we did some cleaning on Sunday and/or Monday morning (kitchen, loos, loo seats
+in particular).</p>
+    <p>Some emergency lights were completely blacked out, H&amp;S violation</p>
+    <p>Staffing level seemed low in general, and several venue managers
+resigned in the early weeks.</p>
+    <p>A fair amount of wall scarring from use of blue-tack</p>
+   </div>
+   <div>
+    <title>For next time, if there is one</title>
+    <p>Paper hand towels? We didn’t this time, worked OK? Probably some
+use of loo roll for drying</p>
+    <p>Should we require use of our own consumables suppliers next time: fits
+with ethos, fits our containers. </p>
+    <p>Start and end of day procedures – define/clarify, who’s responsible
+for what. E.g. turning <emph>on</emph> the emergency lighting is our job.</p>
+    <p>Clarify who repairs things. We do a daily inspection and fix things/bill
+for getting them fixed</p>
+    <p>In general if there are things we agree are are responsibility that we
+are going to do for their benefit, we will have to charge
+for that, not clear how e.g. lump sum vs. timesheet.</p>
+    <p>Leave less cutlery/plates etc. out for them</p>
+    <p>Ask for kitchen counters to be cleared away each night?</p>
+    <p>Clarify who is going to empty bin bags, get agreement on how does/polices triage (recyclable/food
+waste/rubbish). Do we have to be responsible for all this so it can be done as
+we would like?</p>
+    <p>We need to spend more time up front preparing the
+building and flats.  Should we do a complete set of photos?  What is 'complete'?</p>
+    <p>Emergency lights can’t be completely covered, dimmed, e.g. with gel overlay, is
+OK</p>
+    <p>We need a designated contact person, who is on site most of most days, for niggles (E.g.
+shoes in the kitchen :-).  If this changes, or is a shared task, continuity
+needs to be ensured.</p>
+    <p>Better policing of companies wrt care of the building in general, e.g. blue-tack</p>
+   </div>
+   <div>
+    <title>General comments</title>
+    
+   <p>One negative comment on the first Sunday about the meeting space, but
+most feedback on that was positive.</p>
+   <p>In general Sundays went well. Mid-week Meeting also worked well, bar steps for Tony
+Peach, Margaret Anderson and someone else with limited mobility.</p>
+   <p>As an ethical workplace, how do we feel about the way C Venues treats
+their staff, both volunteer and paid?</p>
+   </div>
+  </div>
+  <div>
+   <title>Was it OK? Do this again (with C Venues or someone else)?</title>
+   <list type="defn">
+    <item term="KL">More ‘unexpected work’ than
+‘unpleasant’</item>
+    <item term="EG">The annoying things could be sorted in the agreement,
+including a process for things that are still unclear (e.g. the toilet leak)</item><item term="MS">Niggles rather than disasters. Worth looking for alternatives,
+e.g. Greenside, before committing to C Arts, bearing in mind that they would
+have <emph>their</emph> teething problems</item>
+   </list>
+  </div>
+  <div>
+   <title>Miscellaneous</title>
+   <p class="a">HST to get C Venue's (local)
+network guy’s contact details from Hartley</p><p class="a">KL to scan and
+distribute missing/broken items list</p>
+  <p class="a">HST to figure out how to
+address the need for a regular MEK - MCMember meeting with a schedule that has
+no full MEK overlap time in it.</p>
+  <p>Clarification wrt staff cover going forward: Ellie
+is <emph>not</emph> happy about evening or Saturday working, and MEK are covering a
+lot of evening/Saturday shifts in September.</p>
+  <p>Keith Gunn to go ahead with new cable
+trays.</p>
+  <p>MS has renewed Giffgaff contract</p>
+  <p>Ian Wilson will be visiting about caf&eacute;
+some time soon</p>
+  <p class="a">HST to check the state of the T&amp;C redo by
+Trustees.</p>
+  <p class="a">HST, with respect to the matter of listing 7 VT on meeting agency sites that charge a
+premium, take this to MHMC for review/decision.</p></div>
+ </body>
+</doc>