Mercurial > hg > rsof
changeset 466:caf8bedb7b71
HST complete
| author | Henry Thompson <ht@markup.co.uk> |
|---|---|
| date | Thu, 27 Jun 2024 15:03:14 +0100 |
| parents | 32706d65abeb |
| children | d1a1a6a32075 |
| files | MHMC/2024-06-24/minutes.html MHMC/2024-06-24/minutes.xml |
| diffstat | 2 files changed, 190 insertions(+), 51 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/MHMC/2024-06-24/minutes.html Thu Jun 27 15:03:14 2024 +0100 @@ -0,0 +1,141 @@ +<?xml version="1.0" encoding="US-ASCII"?> +<!DOCTYPE html + PUBLIC "-//HST//DTD XHTML5 1.0 Transitional//EN" "http://www.ltg.ed.ac.uk/~ht/xhtml5.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"><head><meta name="copyright" content="Copyright © 2024 <a href="http://www.ltg.ed.ac.uk/~ht/">Henry S. Thompson</a>&#160;<a href="http://creativecommons.org/licenses/by-sa/3.0/deed.en">CC-BY-SA</a>"/><meta http-equiv="Content-type" content="text/html; charset=utf-8"/><style type="text/css"> + ul.nolabel { margin: 0; margin-left: -2.5em} + ul.naked.nolabel {margin: 0; margin-left: 0; padding-left: 0} + ul.cdefn {clear: both} + div.ndli { margin-bottom: 1ex } + div.hidden {display: none} + + ul.naked > li { list-style-type: none; background: none; margin-left: 2em; +margin-bottom: 0 } + li ul.naked > li, dd ul.naked > li { list-style-type: none; background: none; margin-left: 0; +margin-bottom: 0 } + li.cdefni {} + li.cdefni span.cl {display: inline-block; vertical-align: bottom} + li.cdefni span.cr {display: inline-block; margin-left: 1em; vertical-align: bottom} + pre.code {display: inline-block} + blockquote.vanilla {display: inline-block; margin-left: 1em; + border: solid 1px; background: rgb(238,234,230); + padding: .5ex .5em} + blockquote.vanilla ul.naked li {margin-left: 0 ! important;font-size: 100%} + ol ol ol, ol ol ol li {list-style-type: lower-roman} + ol ol, ol ol li {list-style-type: lower-alpha} + i i {font-style: normal} + li li {font-style: normal} + li ul li {font-style: normal} + li { line-height: 100%; margin-top: 0.3em} + .math {font-family: 'Arial Unicode MS', 'Lucida Sans Unicode', serif} + .sub {font-size: 80%; vertical-align: sub} + .termref {text-decoration: none; color: #606000} + .licence {margin-left: 1em; font-size: 70%} + .credits {margin-left: 1.5em; font-size: 70%} + .right {position: absolute} + .stackdown {vertical-align: text-top; margin-top: 0} + body {font-size: 12pt} + pre.numbered { + white-space: pre-wrap; + } + div.counter { + counter-reset: listing; + } + pre.numbered code { + counter-increment: listing; + } + pre.cl code::before { + content: "$ " ; + font-size: 80%; + width: 2em + } + pre.numbered code::before { + content: counter(listing) ". "; + display: inline-block; + font-size: 80%; + width: 3em; + padding-left: auto; + margin-left: auto; + text-align: right; + } + + /* content doesn't combine :-( */ + pre.numbered.cl code::before { + content: counter(listing) ". $ "; + display: inline-block; + font-size: 80%; + width: 3em; + padding-left: auto; + margin-left: auto; + text-align: right; + } + @page { size: A4 portrait; margin: 2cm; + orphans: 2; widows: 2;} + @media screen { + body {width: 20cm; margin-left: auto; margin-right: auto} + } + @media print { + body {font-size: 10pt} + h1, h2, h3, h4 {page-break-after: avoid} + } + pre.code {font-family: monospace; + font-weight: bold; + line-height: 120%; + padding-top: 0.2em; + padding-bottom: 0.2em; + padding-left: 1em; + padding-right: 1em; + border-style: solid; + border-left-width: 1em; + border-top-width: thin; + border-right-width: thin; + border-bottom-width: thin; + border-color: #95ABD0; + color: #00428C; + background-color: #E4E5E7; +} + pre {margin-left: 0em} + div.toc h2 {font-size: 120%; margin-top: 0em; margin-bottom: 0em} + div.toc h4 {font-size: 100%; margin-top: 0em; margin-bottom: 0em; + margin-left: 1em} + div.toc h1 {font-size: 140%; margin-bottom: 0em} + div.toc ul {margin-top: 1ex} + .byline {font-size: 120%} + div.figure {margin-left: 2em} + div.caption {font-style: italic; font-weight: bold; margin-top: 1em} + i i {font-style: normal} + img {border: 0} + .copyright {font-size: 70%} + .note {width: 20%; float: right; clear: right; margin-left: .5em} + </style><style type="text/css">.r {margin-left: 3em} + .a::before {content: "ACTION: "; font-weight: bold} + </style><title>Meeting +House Management Committee Minutes 2024-05-07</title></head><body style="font-family: DejaVu Sans, Arial; background: rgb(254,250,246)"><div style="text-align: center" class="head"><h1>Meeting +House Management Committee Minutes 2024-05-07</h1><hr/><div class="byline">Convenor: Henry S. Thompson</div><div class="byline">Monday 24 June, p.m., in 7 Victoria Terrace</div><div class="copyright">Copyright © 2024 <a href="http://www.ltg.ed.ac.uk/~ht/">Henry S. Thompson</a> <a href="http://creativecommons.org/licenses/by-sa/3.0/deed.en">CC-BY-SA</a></div></div><div class="body"><div><h2>1. Attendance</h2><dl class=" "><dt><b><a name="Present">Present</a></b></dt><dd>Rachel Fitzgerald (RF), Miranda Girdlestone +(MG) (in part), Katrina McCrea (KM), +Jacqueline Noltingk (JN), Laragh Quinney (LQ), +Henry S. Thompson(HST) + </dd><dt><b><a name="Prevented">Prevented</a></b></dt><dd>Sue Sierra (SS)</dd><dt><b><a name="Copy_to">Copy to</a></b></dt><dd>Susie Harding, Neil Turner</dd></dl></div><div><h2>2. Transition and hiring</h2><div><h4>2.1. Transition cover</h4><p>MG asks for questions</p><p>Do you foresee any problems for contract staff (Majk Stokes (M), +Eliza Giles (E), Ken Latham (K)) going forward?</p><p>Having 3 people in an office along with 2 PCs is not likely to work +well. So we need to work hard to encourage M&K to take annual leave.</p><p class="a">MG & HST to identify work for MEK to do during July/August towards +improving the booking process</p><p>E has a project to move forward on sustainable reusables, K + on signage</p><p>MEK all have annual leave cards, fill in and bring it to MG, it's on TeamUp</p><p>MG thinks MEK's Job Descriptions are sufficient for what's coming</p><p>At Annual Review time, we'll look at their Job Descriptions if need be.</p><p>Structure between the three of them should be as flat as possible: when in doubt, send email + to all three. Leave it up to them to choose who + does something that you ask to be done. Always be +encouraging them to work + as a team.</p><p>A small uplift across the board, say 1%, would be a good + signal that we recognise their contribution.</p></div><div><h4>2.2. Security issues</h4><p>Safe is in two parts, MS and MG have keys to the top, there's a + key to the bottom therein</p><p class="a">MG to add "safe key" to [relevant log]</p><p class="a">MG to inventory the safe and send to HST</p><p>Passwords?</p><p>Building security in the absence of anyone on the stair:</p><p class="a">HST and MG to arrange for more building keys, for MHMC + contacts and CArts</p><p class="a">HST to bring the matter of the intruder alarm back to a + subsequent meeting</p></div><div><h4>2.3. Hiring</h4><p>MG: This [her leaving] is not an uncommon problem, the difficulties + of [the situation] are widely shared</p><p>You'll need to reset/review/renew the situation with MEK + for what's coming next, say next 3 months</p><p>Gave a relevant Job Description for Manchester to HST</p><p class="a">HST to circulate Manchester Job Description</p><p class="a">Get a system for notice when contract renewal + (e.g. maintenance) are coming up.</p></div><div><h4>2.4. Minor points</h4><p>September - carpet changeover will need attention from staff, but + they should be up for it</p><p>E cares for the wee garden and the plants</p><p>K/E will be tasked with checking empty flat(s) regularly to satisfy insurance</p><p class="a">MG to notify JN when she cancels the utility contract +for 3F2, take meter reading and send to JN as she leaves.</p><p class="a">MG to be sure that new lighting invoice from Gunn is addressed +to Area Meeting and goes to JN</p></div></div><div><h2>3. Practical matters during Fringe</h2><div><h4>3.1. On-call rota for 7 weeks</h4><p class="a">RF to arrange contact rota with HST, RF</p><p class="a">MG to get HST, RF, KM access to TeamUps</p></div><div><h4>3.2. Staff rota for 7 weeks</h4><p>In case of illness/family urgency, staff will contact us if + can't sort out between themselves.</p><p class="a">MG to send August staff rota to HST</p><p class="a">HST to send staff rota to RF, KM</p></div><div><h4>3.3. Staff tasks during their weeks</h4><p class="a">HST to ask staff to think about this at all-hands on 25/6 <b>DONE</b></p></div></div><div><h2>4. Time without staff</h2><p>We have had time without staff, which was taken up with a good threshing session.</p><p>Job Description is simple to update, key + part of expectation management for new hire(s) is getting the Aims and Objectives right. + Calling this a 'Manager' post carries an expectation of e.g. a 5-year + plan and a budget.</p><p>[The following will be removed before uploading/circulating outside MHMC]</p><p>[MG: MS was not the Assistant Meeting House Manager that MG needed -- +outstanding Meeting House Assistant, but + resisted attempts to get him to step up sooner.]</p></div><div><h2>5. Date of next meeting</h2><p>Tuesday 2 July, 5 p.m., at 7 Victoria Terrace</p></div></div></body></html> \ No newline at end of file
--- a/MHMC/2024-06-24/minutes.xml Thu Jun 27 12:42:33 2024 +0100 +++ b/MHMC/2024-06-24/minutes.xml Thu Jun 27 15:03:14 2024 +0100 @@ -26,94 +26,92 @@ </div> <div> <title>Transition and hiring</title> - <div> - <title> Recommendations from the outgoing Meeting House Manager</title> <div> - <title> Transition cover</title> + <title>Transition cover</title> <p>MG asks for questions</p> <p>Do you foresee any problems for contract staff (Majk Stokes (M), Eliza Giles (E), Ken Latham (K)) going forward?</p> - <p>August: 3 people in an office with 2 PCs</p> - <p>Need to work hard to encourage M&K to take annual leave</p> - <p class="a">MG & HST to identify work for them to do towards + <p>Having 3 people in an office along with 2 PCs is not likely to work +well. So we need to work hard to encourage M&K to take annual leave.</p> + <p class="a">MG & HST to identify work for MEK to do during July/August towards improving the booking process</p> <p>E has a project to move forward on sustainable reusables, K on signage</p> <p>MEK all have annual leave cards, fill in and bring it to MG, it's on TeamUp</p> - <p>Security issues: Add safe key to list in FD doc wrt Banking and - financial reporting</p> - <p>Safe is in two parts, MS and MG have keys to the top, there's a - key to the bottom therein</p> - <p>Passwords?</p> - <p>September - carpet changeover will need attention from staff, but - they should be up for it</p> - <p>E cares for the wee garden and the plants</p> - <p>K/E will be tasked with checking flats -</p> -<p class="a">on MG to inventory the safe and send to HST</p> -<p class="a">on MG to notify JN when she cancels the utility contract -for 3F2, take meter reading and send to JN as she leaves.</p> -<p class="a">MG to be sure that new lighting invoice from Gunn is addressed -to AM and goes to JN</p> -<p class="a">HST to bring the matter of the intruder alarm back to a - subsequent meeting</p> - </div> - <div> - <title> Transition Management structure</title> - <p>MG: Thinks JD is sufficient for what's coming</p> - <p>At AR time, we'll look at the JD if need be</p> - <p>Structure: As flat as possible: when in doubt, send email - to all 3. Leave it up to them to choose who - does something that you ask to be done. Work + <p>MG thinks MEK's Job Descriptions are sufficient for what's coming</p> + <p>At Annual Review time, we'll look at their Job Descriptions if need be.</p> + <p>Structure between the three of them should be as flat as possible: when in doubt, send email + to all three. Leave it up to them to choose who + does something that you ask to be done. Always be +encouraging them to work as a team.</p> <p>A small uplift across the board, say 1%, would be a good signal that we recognise their contribution.</p> - <p>Building security in the absence of anyone on the stair</p> + </div> +<div> + <title>Security issues</title> + <p>Safe is in two parts, MS and MG have keys to the top, there's a + key to the bottom therein</p> + <p class="a">MG to add "safe key" to [relevant log]</p> + <p class="a">MG to inventory the safe and send to HST</p> + <p>Passwords?</p> + <p>Building security in the absence of anyone on the stair:</p> <p class="a">HST and MG to arrange for more building keys, for MHMC contacts and CArts</p> - </div> +<p class="a">HST to bring the matter of the intruder alarm back to a + subsequent meeting</p></div> <div> <title> Hiring</title> <p>MG: This [her leaving] is not an uncommon problem, the difficulties of [the situation] are widely shared</p> <p>You'll need to reset/review/renew the situation with MEK for what's coming next, say next 3 months</p> - <p>Gave a relevant JD for Manchester to HST</p> -<p class="a">HST to circulate Manchester JD</p> + <p>Gave a relevant Job Description for Manchester to HST</p> +<p class="a">HST to circulate Manchester Job Description</p> <p class="a">Get a system for notice when contract renewal (e.g. maintenance) are coming up.</p> -<p class="a">MG to send August rota to HST</p> -<p class="a">HST to send staff rota to RF</p> -<p class="a">RF to arrange contact rota </p> </div> - </div> + <div> + <title>Minor points</title> + <p>September - carpet changeover will need attention from staff, but + they should be up for it</p> + <p>E cares for the wee garden and the plants</p> + <p>K/E will be tasked with checking empty flat(s) regularly to satisfy insurance</p> +<p class="a">MG to notify JN when she cancels the utility contract +for 3F2, take meter reading and send to JN as she leaves.</p> +<p class="a">MG to be sure that new lighting invoice from Gunn is addressed +to Area Meeting and goes to JN</p></div> </div> <div> <title> Practical matters during Fringe</title> <div> - <title> On-call rota for 7 weeks</title> - <p class="a">HST, RF, KM to agree</p> - <p>In case of illness/family urgency, staff will contact us if - can't sort out between themselves.</p> + <title> On-call rota for 7 weeks</title> +<p class="a">RF to arrange contact rota with HST, RF</p> <p class="a">MG to get HST, RF, KM access to TeamUps</p> </div> <div> - <title> Staff rota for 7 weeks</title> - <p class="a">MG, HST to circulate</p> + <title> Staff rota for 7 weeks</title> + <p>In case of illness/family urgency, staff will contact us if + can't sort out between themselves.</p> +<p class="a">MG to send August staff rota to HST</p> +<p class="a">HST to send staff rota to RF, KM</p> </div> <div> <title> Staff tasks during their weeks</title> - <p class="a">HST to ask staff to think about this at all-hands on 25/6</p> + <p class="a">HST to ask staff to think about this at all-hands on 25/6 <name>DONE</name></p> </div> </div> <div> <title> Time without staff</title> - <p>[MG: MS was not the AMHM that MG needed -- outstanding MHA, but + <p>We have had time without staff, which was taken up with a good threshing session.</p> + <p>Job Description is simple to update, key + part of expectation management for new hire(s) is getting the Aims and Objectives right. + Calling this a 'Manager' post carries an expectation of e.g. a 5-year + plan and a budget.</p> + <p>[The following will be removed before uploading/circulating outside MHMC]</p> + <p>[MG: MS was not the Assistant Meeting House Manager that MG needed -- +outstanding Meeting House Assistant, but resisted attempts to get him to step up sooner.]</p> - <p>[good threshing period -- Job Description is simple to update, key - part of expectation management is getting the Aims and Objectives - Calling this a Manager post carries an expectation of e.g. a 5-year - plan and a budget.]</p> </div> <div> <title>Date of next meeting</title>