http://wiki.norwichhackspace.org/api.php?action=feedcontributions&feedformat=atom&user=Mario+CatlinNorwich Hackspace - User contributions [en-gb]2026-04-29T11:37:17ZUser contributionsMediaWiki 1.33.1http://wiki.norwichhackspace.org/index.php?title=Guidelines&diff=829Guidelines2020-12-07T16:08:06Z<p>Mario Catlin: </p>
<hr />
<div>The main points:<br />
<br />
The space is open on a limited basis for members who need to use equipment<br />
* Stay away if you can<br />
* No group activity please, generally one person per area, two in the main room <br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel)<br />
* Please announce arrival and departure in the #who-is-in-the-space channel<br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can)<br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders<br />
* It is your responsibility to remain within the legal guidelines<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
* Clean and sanitise equipment, door handles and switches when you when you arrive <br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Clean and sanitise equipment, door handles and switches again when you when you leave<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can.<br />
* There are sealed milk portions in the fridge<br />
* If you want to use your own mug, please bring one with you (or water bottle)<br />
* Wash and sanitise your hands more often than usual<br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
*</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=828Main Page2020-12-07T15:14:55Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''77<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release. Please read via the link<br />
<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Guidelines&diff=827Guidelines2020-12-07T15:13:59Z<p>Mario Catlin: </p>
<hr />
<div>The main points:<br />
<br />
The space is open on a limited basis for members who need to use equipment<br />
* Stay away if you can<br />
* No group activity please, generally one person per area, two in the main room <br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel)<br />
* Please announce arrival and departure in the #who-is-in-the-space channel<br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can)<br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders<br />
* It is your responsibility to remain within the legal guidelines<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can.<br />
* There are sealed milk portions in the fridge<br />
* If you want to use your own mug, please bring one with you (or water bottle)<br />
* Wash and sanitise your hands more often than usual<br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
*</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Guidelines&diff=825Guidelines2020-12-07T15:08:55Z<p>Mario Catlin: </p>
<hr />
<div>The main points:<br />
<br />
The space is open on a limited basis for members who need to use equipment<br />
* Stay away if you can<br />
* No socialising is allowed, one person per area, two in the main room<br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel)<br />
* Please announce arrival and departure in the #who-is-in-the-space channel<br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can)<br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders<br />
* It is your responsibility to remain within the legal guidelines<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can.<br />
* There are sealed milk portions in the fridge<br />
* If you want to use your own mug, please bring one with you (or water bottle)<br />
* Wash and sanitise your hands more often than usual<br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
*</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=824Main Page2020-12-07T15:03:15Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''77<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release. Please read<br />
<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=823Main Page2020-12-07T15:02:32Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''77<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release. Please read/555521110111<br />
<br />
<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=822Main Page2020-12-07T15:01:18Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''77<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
////////////////999-<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release. Please read/555521110111<br />
<br />
<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Guidelines&diff=821Guidelines2020-12-07T14:48:46Z<p>Mario Catlin: </p>
<hr />
<div>The main points:<br />
<br />
The space is open on a limited basis for members who need to use equipment<br />
* Stay away if you can<br />
* No socialising is allowed, one person per area, two in the main room<br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel<br />
* Please announce arrival and departure in the#who-is-in-the-space channel<br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can)<br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders<br />
* It is your responsibility to remain within the legal guidelines<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can.<br />
* There are sealed milk portions in the fridge<br />
* If you want to use your own mug, please bring one with you (or water bottle)<br />
* Wash and sanitise your hands more often than usual<br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
*</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=820Main Page2020-12-07T14:47:16Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release<br />
<br />
<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Guidelines&diff=819Guidelines2020-12-07T14:46:40Z<p>Mario Catlin: Created page with "The main points: The space is open on a limited basis for members who need to use equipment Stay away if you can No socialising is allowed, one person per area, two in the ma..."</p>
<hr />
<div>The main points:<br />
<br />
The space is open on a limited basis for members who need to use equipment<br />
Stay away if you can<br />
No socialising is allowed, one person per area, two in the main room<br />
Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel<br />
Please announce arrival and departure in the#who-is-in-the-space channel<br />
We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can)<br />
Limited access (up to 6 people) on Monday evenings for non-keyholders<br />
It is your responsibility to remain within the legal guidelines<br />
Keep safe, keep legal, stay at home if you can<br />
Only consider coming if you are not showing any Covid 19 symptoms.<br />
If you have just come back from holiday or a trip you must quarantine for two weeks<br />
Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
Please bring a mask – re useable masks on sale at £1<br />
Wear your mask when moving around in the space<br />
On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
Sign in on list on clipboard (government requirement)<br />
Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
The main desk should be clear - sanitise the area you are going to work in<br />
Make sure other members are happy with the distance you keep.<br />
When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
Make sure you leave enough time to clear up<br />
If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
Things to consider:- <br />
<br />
The tuck shop is low-stock so bring your own food if you can.<br />
There are sealed milk portions in the fridge<br />
If you want to use your own mug, please bring one with you (or water bottle)<br />
Wash and sanitise your hands more often than usual<br />
We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch<br />
If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
Any questions please contact Admin Team @mario, @alan_scrase @james_m</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=818Main Page2020-12-07T14:45:57Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
We have adjusted the [[guidelines]] in the light of the latest lockdown release<br />
<br />
The main points:<br />
* The space is open on a limited basis for members who need to use equipment <br />
* Stay away if you can <br />
* No socialising is allowed, one person per area, two in the main room <br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel <br />
* Please announce arrival and departure in the#who-is-in-the-space channel <br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can) <br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders <br />
* It is your responsibility to remain within the legal guidelines <br />
<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
<br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
'''Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can. <br />
* There are sealed milk portions in the fridge <br />
* If you want to use your own mug, please bring one with you (or water bottle) <br />
* Wash and sanitise your hands more often than usual <br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch <br />
<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=817Main Page2020-12-07T00:32:25Z<p>Mario Catlin: </p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
'''''Welcome new members please read the [[Induction]]<br />
'''''<br />
Updated access policy post Covid Lockdown 2<br />
[[File:Hackspace Covid Access.png|thumb|Covid access]]<br />
<br />
'''NH Covid Revised Protocol post-Lockdown<br />
<br />
Effective from Monday 7 December 2020 '''<br />
<br />
We have adjusted the guidelines in the light of the latest lockdown release<br />
<br />
The main points:<br />
* The space is open on a limited basis for members who need to use equipment <br />
* Stay away if you can <br />
* No socialising is allowed, one person per area, two in the main room <br />
* Please book via the calendar (type book equipment into the #who-is-in-the-space Slack channel <br />
* Please announce arrival and departure in the#who-is-in-the-space channel <br />
* We will not have group meetings on Mondays but Zoom Show and Tells instead (please offer to do one if you can) <br />
* Limited access (up to 6 people) on Monday evenings for non-keyholders <br />
* It is your responsibility to remain within the legal guidelines <br />
<br />
* Keep safe, keep legal, stay at home if you can<br />
* Only consider coming if you are not showing any Covid 19 symptoms.<br />
* If you have just come back from holiday or a trip you must quarantine for two weeks<br />
* Post in #who-is-in-the-space that you are intending to come and when you arrive and leave - max 6 persons in the main space at any given time, 3 people in Metalspace - this will be revised as we see how it works out<br />
* Please bring a mask – re useable masks on sale at £1<br />
* Wear your mask when moving around in the space<br />
* On arrival scan test and trace QR code (Download NHS Covid 19 app)<br />
* Sign in on list on clipboard (government requirement)<br />
* Wash and/or sanitise hands frequently (pencil will be handled by everyone)<br />
* The main desk should be clear - sanitise the area you are going to work in<br />
<br />
* Make sure other members are happy with the distance you keep.<br />
* When you leave please remove all your stuff and clear away your rubbish - this means other people do not have to touch it.<br />
* Make sure you leave enough time to clear up<br />
* If anyone feels uncomfortable, they must feel able to say so – let’s have culture of consideration for the most vulnerable or worried<br />
<br />
'''Things to consider:- <br />
* The tuck shop is low-stock so bring your own food if you can. <br />
* There are sealed milk portions in the fridge <br />
* If you want to use your own mug, please bring one with you (or water bottle) <br />
* Wash and sanitise your hands more often than usual <br />
* We cannot sanitise the whole space, however the virus dies on most surfaces after 72 hours so please keep visits spaced and clean anything you touch <br />
<br />
* If you are extra vulnerable, please stay away to protect yourself, unless essential<br />
* If there is an increased outbreak in Norwich, we will revise the plan and we may be required to close completely. We review the plan in line with government and local guidance <br />
* Please check into Slack regularly and especially #notices and #virus-chat for updates<br />
* Any questions please contact Admin Team @mario, @alan_scrase @james_m<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
* [[Metal workshop improvements mk1]]<br />
* [[Lion house decorating]]<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== Permanent Store of Information ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
* [[list of discussion or chat pages]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=File:Hackspace_Covid_Access.png&diff=816File:Hackspace Covid Access.png2020-12-07T00:27:21Z<p>Mario Catlin: </p>
<hr />
<div>Quick reference for current access under government guidelines</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72505/202020-10-29T17:10:05Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie ''Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?''<br />
<br />
My answer was: ''Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: ''For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. <br />
<br />
There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work''. <br />
<br />
I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.''<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72405/202020-10-29T17:09:43Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?<br />
<br />
My answer was: ''Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: ''For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. <br />
<br />
There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work''. <br />
<br />
I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.''<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72305/202020-10-29T17:09:23Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?<br />
<br />
My answer was: ''Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. <br />
<br />
There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work''. <br />
<br />
I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72205/202020-10-29T16:57:33Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?<br />
<br />
My answer was: Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. <br />
<br />
There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work. <br />
<br />
I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72105/202020-10-29T16:57:10Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?<br />
<br />
My answer was: Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work. I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=72005/202020-10-29T16:56:44Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was available for approx 10 days for members to read and absorb beforehand. Several members (co-proposers) were in agreement and said so.<br />
<br />
There were a couple of people who asked questions in Slack decision-making channel. Brian asked about the Constitution ie Can I ask - 1. Does the constitution still hold as our constitution? - if not then a new constitution needs to be written and taken to an AGM to be ratified. 2. If we are sticking with the constitution as written - then is the core team (Management committee), as in the constitution, the the core team as in your new document?<br />
<br />
My answer was: Yes the constitution stands and the core team is the core team as stated in the constitution with the role description as specified in my document. That is they are brought together for specific decision making situations and are a strategic and problem solving resource rather than a day to day management mechanism. A bit more like a Board might relate to a charity's exec team<br />
<br />
I posted this: For the record, I have tried to take on board what people have fed back over the last few weeks, without tipping the whole hackspace management over as by and large, it has grown and run successfully for 6 years now, and 3 and half of those in the current premises. Also we don’t want it to be over-bureaucratic as it is a lot of work as it is, but I think we all agreed that some things needed to change and be tightened up. The proposition includes enacting the constitution inc a named core team, admin team, leads and regular meetings, better transparency and clarity of decision-making, a proposal recording system, better documentation and access (wiki), more evident access to Metalspace for members, grievance and who to talk to. There is a lot of leeway to fine tune as we go forward, and add detail - this proposal is a basis to work from. If anyone has any other suggestions then please feed them in with some detail about how they would work.<br />
I have done my best to be even-handed - it isn’t easy keeping everyone happy and probably we won’t achieve that but hopefully we can work together to improve.<br />
<br />
At the meeting, James T focussed on slide 21 as a sticking point for him - ie how a core team is selected and accountability to the membership in the long term ie how the club would get rid of a core team member. This was the aspect that we agreed to postpone subject to further thinking and discussion, whilst we also trial the whole system as it is, as no-one had any objections to the proposed names put forward (who had all agreed to occupy the role)<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=71905/202020-10-29T16:44:31Z<p>Mario Catlin: /* Outcome */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was a<br />
<br />
== Outcome ==<br />
<br />
This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=71805/202020-10-29T16:43:31Z<p>Mario Catlin: /* Comments */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
The presentation was a<br />
<br />
== Outcome ==<br />
<br />
<!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=71705/202020-10-29T16:29:40Z<p>Mario Catlin: /* Outcome */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=71605/202020-10-29T16:27:21Z<p>Mario Catlin: /* Outcome */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Taylor, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=71505/202020-10-29T01:53:12Z<p>Mario Catlin: /* Outcome */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.<br />
<br />
Attendees were Marion Catlin, Alan Scrase, Ben Norcutt, Brian Norman, Alan (Percy) Childs, James Thornton, Peter Hibbit, Karl Ablitt with apologies from Toby Catlin, Tim Parnell, James Mason, Andy Saunders, Dan Robertson<br />
<br />
The proposal was generally accepted and some of the suggestions have already been put into practice on a trial basis. There was general agreement that the proposed structure should be adopted although there was one major sticking point which formed the majority of the discussion, which was the means of appointing the Core Team. After a lengthy but constructive discussion it was agreed to start with the Core Team as proposed for this year and to resolve the means of appointment/election before an AGM in September 2021.<br />
There was an agreement to the proposed Admin Team of Marion, Alan and James who are responsible for the day-to-day running of the Hackspace and general decisions, and first point of contact for members and external communications.<br />
<br />
A Core Team was proposed and accepted: the Admin Team - Marion, Alan and James M - Ben, Toby, Brian, Tim, Percy, Dan R.<br />
<br />
We have a draft list of Lead roles and people to take them on. This is a renamed version of the Tsars = people who step forward to look after aspects of the space - either areas, equipment or activities. One of the first actions is to confirm and communicate this list so we will be looking for volunteers.<br />
<br />
The overall proposal was accepted with some of the solutions to issues as trials such as the proposal system, the Wiki and decision-making which can all be reviewed and adjusted over the forthcoming year. There will be regular member meetings via Zoom as well as a minimum of two Core Team meetings and an AGM.<br />
<br />
There is more detail which is available and will be adapted and added to as we go along based on feedback when we use the systems such as communications, proposals and decision-making.<br />
<br />
<br />
--><br />
<!-- Agreed - Completed<br />
Agreed - Actions to be implemented, Marion to lead implementation</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65905/202020-10-19T01:40:54Z<p>Mario Catlin: /* What is being asked for */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
I have also made suggestions about who should make up each team based on what people have offered to do. We will need to bring together volunteers for Lead Maintainer roles as there are a number of areas not yet covered but this can be fluid and develop over time.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65805/202020-10-19T01:38:30Z<p>Mario Catlin: </p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal which can be downloaded here <br />
https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65705/202020-10-19T01:27:15Z<p>Mario Catlin: /* What is being asked for */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
Please find the presentation posted here as a pdf https://norwichhackspaceadmin.weebly.com/proposal-for-hackspace-20.html<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal.<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65605/202020-10-19T00:48:43Z<p>Mario Catlin: /* What is being asked for */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on '''Tuesday 27 October, 8.30pm''' we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, the majority of members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal.<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65505/202020-10-19T00:47:31Z<p>Mario Catlin: /* Who is for it */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on Tuesday 27 October, 8.30pm we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, most members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I '''(Marion)''' have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie '''Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin''' has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal.<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65405/202020-10-19T00:46:37Z<p>Mario Catlin: /* Who is for it */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on Tuesday 27 October, 8.30pm we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, most members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
I (Marion) have put the proposal together after speaking with a number of members over the last few weeks. I have tried to be as fair as I can in taking on board other people's views whilst remaining true to my own. <br />
<br />
I have a lot of experience with setting up and running non-profit organisations of all kinds and feel qualified to offer this option as a realistic and manageable way forward that builds on what we have already achieved, will address our issues and will not cause disruption. I have read, studied observed and researched community-led initiatives over many years. I am on several governance Boards and professionally, I advise creative businesses and organisations on the pros and cons of various structures and ways of operating. I ran Norwich Fringe Festival for 9 years on a similar model, which included managing a wide range of activities, 100s of artists and occupying a massive shoe factory as a base for artists, with no significant issues and great achievements. <br />
<br />
I have reality-checked the proposal with a small team of members who offered to be my working party and who have agreed to out their names to the proposal ie Ben Norcutt, Alan Scrase, Barny Relph and James Mason. Toby Catlin has also said that he is for it.<br />
<br />
As it is a major proposal, I would like to present it at a meeting so that it can be discussed and adopted. This meeting will be open to all members and take place via Zoom on Tuesday 27 October 8.30pm. This gives members just over a week to read the proposal.<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65305/202020-10-19T00:33:36Z<p>Mario Catlin: /* Why/how this will be good to have */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on Tuesday 27 October, 8.30pm we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, most members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
== Why/how this will be good to have ==<br />
It will be good to have a comprehensive document which lays out the basic structure of the space, who to talk to and how to make things happen within Norwich Hackspace. It offers a starting-point against which to assess how we work as a group.<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65205/202020-10-19T00:31:45Z<p>Mario Catlin: /* What is being asked for */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
That, following a Zoom meeting on Tuesday 27 October, 8.30pm we trial this structure (details laid out in pdf document) which is essentially a formalisation and clarification of the way we have successfully built and run the Hackspace over the last 6 years but with modifications and adjustments to address issues that were raised during the review, as a result of the Hackspace membership increasing, more space and activities and the strains of Covid, which means we can't see each other face to face so easily. Also, over time, our processes lapsed and need re-stating.<br />
<br />
Through this proposal, we are addressing decision-making, transparency, an AGM and clear lines of communication - that is an '''Admin Team''' to take care of day-to-day management and decisions, a team of '''Lead Maintainers''' to look after equipment tools and areas and a strategic '''Core Team''' to sort out issues, make bigger decisions that affect the whole Hackspace and membership, sort out grievances and be a final arbiter.<br />
<br />
The model generally is one where the members run the space for the members (legal status - an Unincorporated Association) which operates in an open-source way with all members having the choice to be involved (or not) in the running of the space by being proactive, making suggestions, offering opinions and taking on roles. Other hackspace such as London Hackspace operate a Do-Ocracy where if members want to do or buy something, they make a reasoned request and if there is not significant objection, it is considered approved and they are able to take forward an action. This is a more agile way of running the space than waiting for committee meetings and approval for changes and purchases.<br />
<br />
This is a valid and tested alternative to a more traditional elected committee system, which would take more work to set up and operate and is not preferred by many members, although some members are in favour.<br />
<br />
It should be noted that whilst the review uncovered some clear lapses and failings, most members are happy with the way the Hackspace is currently run. Some necessary improvements have been put in place already and will be reviewed and modified as we see how they work - eg this proposal form, the Wiki, better communications etc<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65105/202020-10-19T00:12:46Z<p>Mario Catlin: /* Cost */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
no cost involved<br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=65005/202020-10-19T00:12:28Z<p>Mario Catlin: /* Date for Decision */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Tuesday 27 October via Zoom meeting after clarification<br />
<br />
== Cost ==<br />
<!-- this should include purchase cost prefrably with an internet link, cost of consumables, --><br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=64905/202020-10-19T00:11:44Z<p>Mario Catlin: /* Date proposed */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed == 19 October 2020<br />
<br />
== Date for Decision ==<br />
Usually one week after posting <br />
<br />
== Cost ==<br />
<!-- this should include purchase cost prefrably with an internet link, cost of consumables, --><br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=64805/202020-10-19T00:11:27Z<p>Mario Catlin: /* Proposer */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer == Marion Catlin @mario<br />
<br />
== Date proposed ==<br />
<br />
<br />
== Date for Decision ==<br />
Usually one week after posting <br />
<br />
== Cost ==<br />
<!-- this should include purchase cost prefrably with an internet link, cost of consumables, --><br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=05/20&diff=64705/202020-10-19T00:11:05Z<p>Mario Catlin: /* Title */</p>
<hr />
<div>== Title == Hackspace structure and management<br />
<br />
== Proposer ==<br />
<br />
<br />
== Date proposed ==<br />
<br />
<br />
== Date for Decision ==<br />
Usually one week after posting <br />
<br />
== Cost ==<br />
<!-- this should include purchase cost prefrably with an internet link, cost of consumables, --><br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Comments ==<br />
<br />
== Outcome ==<br />
<br />
<!-- This can be used to update the progress of the proposal --><br />
<!-- Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold --></div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Office&diff=464Office2020-09-29T23:50:43Z<p>Mario Catlin: </p>
<hr />
<div>=== Maintainer Marion @mario ===<br />
<br />
'''In the office'''<br />
<br />
* First aid kit and accident book - please record accidents, even if minor<br />
please alert @mario on Slack if anything is low stock or missing<br />
<br />
* The fridge - drinks and anything that needs keeping cold<br />
<br />
* Backup stock for tuck shop<br />
<br />
* Labels, fliers, stationery in the desk drawer<br />
<br />
* Stock of toilet rolls and paper towels<br />
<br />
* In the deep drawer, Hackspace tee-shirts, label gun<br />
<br />
'''Heating controls'''<br />
<br />
Above the desk is a control for the heating which is adjusted via a broom handle - please ask @alan_scrase for operating instructions<br />
You will learn about this at a key induction<br />
<br />
'''Networking and communications equipment'''<br />
<br />
Please leave this to the Network Maintainer @plexer - don't tamper</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=463Tuck & Tech Shop2020-09-29T23:49:40Z<p>Mario Catlin: </p>
<hr />
<div>'''Tuck Shop'''<br />
We normally keep a stock of chocolate, snacks and crisps (currently suspended for Covid reasons) in the Main Space on the grey cupboard<br />
<br><br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br><br />
<br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way<br />
<br />
<br />
'''Tech Shop'''<br />
We also keep a stock of electronic bits and pieces for sale to members - in the grey sliding door cupboard in the main space<br />
<br />
@alan_scrase knows what we have and can order items as required - please pay in same way as Tuck shop<br />
<br />
<br />
'''Consumables stock'''<br />
* We keep stocks of plywood and acrylic for use with the laser cutter and filament and resin for th 3D printers. <br />
* <br />
* Lasercutter stocks are kept on the shelves in the laser room<br />
* <br />
* Filament and resin in the fridge in the 3D print room<br />
<br />
For any requirements, please let the Admin Team know<br />
<br />
Prices and payment via IZettle please - a tablet and card reader are located on a pillar in the main space</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=462Tuck & Tech Shop2020-09-29T23:48:42Z<p>Mario Catlin: </p>
<hr />
<div>'''Tuck Shop'''<br />
We normally keep a stock of chocolate, snacks and crisps (currently suspended for Covid reasons) in the Main Space on the grey cupboard<br />
<br><br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br><br />
<br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way<br />
<br />
<br />
'''Tech Shop'''<br />
We also keep a stock of electronic bits and pieces for sale to members - in the grey sliding door cupboard in the main space<br />
<br />
@alan_scrase knows what we have and can order items as required - please pay in same way as Tuck shop<br />
<br />
<br />
'''Consumables stock'''<br />
* We keep stocks of plywood and acrylic for use with the laser cutter and filament and resin for th 3D printers. <br />
* <br />
* Lasercutter stocks are kept on the shelves in the laser room<br />
* <br />
* Filament and resin in the fridge in the 3D print room<br />
<br />
For any requirements, please let the Admin Team know<br />
<br />
Payment via IZettle please</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=461Tuck & Tech Shop2020-09-29T23:48:23Z<p>Mario Catlin: </p>
<hr />
<div>'''Tuck Shop'''<br />
We normally keep a stock of chocolate, snacks and crisps (currently suspended for Covid reasons) in the Main Space on the grey cupboard<br />
<br><br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br><br />
<br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way<br />
<br />
<br />
'''Tech Shop'''<br />
We also keep a stock of electronic bits and pieces for sale to members - in the grey sliding door cupboard in the main space<br />
<br />
@alan_scrase knows what we have and can order items as required - please pay in same way as Tuck shop<br />
<br />
<br />
'''Consumables stock'''<br />
We keep stocks of plywood and acrylic for use with the laser cutter and filament and resin for th 3D printers. <br />
<br />
Lasercutter stocks are kept on the shelves in the laser room<br />
<br />
Filament and resin in the fridge in the 3D print room<br />
<br />
For any requirements, please let the Admin Team know<br />
<br />
Payment via IZettle please</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=460Tuck & Tech Shop2020-09-29T23:47:54Z<p>Mario Catlin: </p>
<hr />
<div>'''Tuck Shop'''<br />
We normally keep a stock of chocolate, snacks and crisps (currently suspended for Covid reasons) in the Main Space on the grey cupboard<br />
<br><br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br><br />
<br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way<br />
<br />
<br />
'''Tech Shop'''<br />
We also keep a stock of electronic bits and pieces for sale to members - in the grey sliding door cupboard in the main space<br />
<br />
@alan_scrase knows what we have and can order items as required - please pay in same way as Tuck shop<br />
<br />
<br />
'''Consumables stock'''<br />
We keep stocks of plywood and acrylic for use with the laser cutter and filament and resin for th 3D printers. <br />
<br />
Lasercutter stocks are kept on the shelves in the laser room<br />
Filament and resin in the fridge in the 3D print room<br />
For any requirements, please let the Admin Team know<br />
<br />
Payment via IZettle please</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=459Tuck & Tech Shop2020-09-29T23:47:27Z<p>Mario Catlin: </p>
<hr />
<div>'''Tuck Shop'''<br />
We normally keep a stock of chocolate, snacks and crisps (currently suspended for Covid reasons) in the Main Space on the grey cupboard<br />
<br><br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br><br />
<br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way<br />
<br />
'''Tech Shop'''<br />
We also keep a stock of electronic bits and pieces for sale to members - in the grey sliding door cupboard in the main space<br />
<br />
@alan_scrase knows what we have and can order items as required - please pay in same way as Tuck shop<br />
<br />
'''Consumables stock'''<br />
We keep stocks of plywood and acrylic for use with the laser cutter and filament and resin for th 3D printers. <br />
<br />
Lasercutter stocks are kept on the shelves in the laser room<br />
Filament and resin in the fridge in the 3D print room<br />
For any requirements, please let the Admin Team know<br />
<br />
Payment via IZettle please</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Tuck_%26_Tech_Shop&diff=458Tuck & Tech Shop2020-09-29T23:41:50Z<p>Mario Catlin: Created page with "We normally keep a stock of chocolate, snacks and crisps (suspended for Covid reasons) @mario buys the stock (usually at Makro) so any requests to her on Slack please<br> Ite..."</p>
<hr />
<div>We normally keep a stock of chocolate, snacks and crisps (suspended for Covid reasons)<br />
@mario buys the stock (usually at Makro) so any requests to her on Slack please<br><br />
<br />
Items are paid for via IZettle and most are listed. It is an honesty system - and honesty keeps us going<br />
<br><br />
You can pay by cash (in the donations tin) or card (via the car reader) but please record the purchase either way</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Office&diff=457Office2020-09-29T23:38:05Z<p>Mario Catlin: </p>
<hr />
<div>Maintainer Marion @mario<br />
<br />
'''In the office'''<br />
<br />
* First aid kit and accident book - please record accidents, even if minor<br />
please alert @mario on Slack if anything is low stock or missing<br />
<br />
* The fridge - drinks and anything that needs keeping cold<br />
<br />
* Backup stock for tuck shop<br />
<br />
* Labels, fliers, stationery in the desk drawer<br />
<br />
* Stock of toilet rolls and paper towels<br />
<br />
* In the deep drawer, Hackspace tee-shirts, label gun<br />
<br />
'''Heating controls'''<br />
<br />
Above the desk is a control for the heating which is adjusted via a broom handle - please ask @alan_scrase for operating instructions<br />
You will learn about this at a key induction<br />
<br />
'''Networking and communications equipment'''<br />
<br />
Please leave this to the Network Maintainer @plexer - don't tamper</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Office&diff=456Office2020-09-29T23:37:27Z<p>Mario Catlin: </p>
<hr />
<div>Maintainer Marion @mario<br />
<br />
'''In the office'''<br />
<br />
* First aid kit and accident book - please record accidents, even if minor<br />
please alert @mario on Slack if anything is low stock or missing<br />
<br />
* The fridge - drinks and anything that needs keeping cold<br />
<br />
* Backup stock for tuck shop<br />
<br />
* Labels, fliers, stationery<br />
<br />
* Stock of toilet rolls and paper towels<br />
<br />
* In the deep drawer, Hackspace tee-shirts, label gun<br />
<br />
'''Heating controls'''<br />
<br />
Above the desk is a control for the heating which is adjusted via a broom handle - please ask @alan_scrase for operating instructions<br />
You will learn about this at a key induction<br />
<br />
'''Networking and communications equipment'''<br />
<br />
Please leave this to the Network Maintainer @plexer - don't tamper</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Office&diff=455Office2020-09-29T23:37:04Z<p>Mario Catlin: Created page with "Maintainer Marion @mario '''In the office''' * First aid kit and accident book pleas record any accidents, even if minor please alert @mario on Slack if anything is low s..."</p>
<hr />
<div>Maintainer Marion @mario<br />
<br />
'''In the office'''<br />
<br />
* First aid kit and accident book pleas record any accidents, even if minor<br />
please alert @mario on Slack if anything is low stock or missing<br />
<br />
* The fridge - drinks and anything that needs keeping cold<br />
<br />
* Backup stock for tuck shop<br />
<br />
* Labels, fliers, stationery<br />
<br />
* Stock of toilet rolls and paper towels<br />
<br />
* In the deep drawer, Hackspace tee-shirts, label gun<br />
<br />
'''Heating controls'''<br />
<br />
Above the desk is a control for the heating which is adjusted via a broom handle - please ask @alan_scrase for operating instructions<br />
You will learn about this at a key induction<br />
<br />
'''Networking and communications equipment'''<br />
<br />
Please leave this to the Network Maintainer @plexer - don't tamper</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Main_Page&diff=454Main Page2020-09-29T23:27:02Z<p>Mario Catlin: /* Hackspace subareas */</p>
<hr />
<div><strong>Norwich Hackspace</strong><br />
<br />
Welcome new members please read the [[Induction]]<br />
<br />
== Hackspace subareas ==<br />
* [[Workshop]]<br />
* [[Metal Workshop]]<br />
* [[Laser room]]<br />
* [[3D print Room]]<br />
* [[HS main room]]<br />
* [[Office]]<br />
* [[Tuck & Tech Shop]]<br />
<br />
== Projects ==<br />
===Hackspace===<br />
<br />
===Personal===<br />
* [[Plasma CNC]]<br />
<br />
== How-To guides ==<br />
* [[list of how-to guides]]<br />
* [[list of software guides]]<br />
* [[how to edit this wiki]]<br />
* [[suppliers for materials]]<br />
* [[useful or interesting links]]<br />
<br />
== Policies ==<br />
<br />
Place for general policies<br><br />
<br />
[[Hackspace Insurance policies]]<br><br />
<br />
[[New member guides]]<br><br />
<br />
== Proposals ==<br />
* [[Proposals and decision making - open]]<br />
* [[Proposals and decision making - closed]]<br />
<br />
== MediaWiki Getting started ==<br />
* Please [[READ ME]] before making changes<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=Workshop&diff=453Workshop2020-09-29T23:24:58Z<p>Mario Catlin: /* Maintainer: Alan */</p>
<hr />
<div>[[Category:Area]]<br />
<br />
==Maintainer: Alan @alan_scrase==<br />
<br />
==Training Requirements==<br />
Whilst all use of Tools and Equipment is at your own risk each one will have a colour code denoting how much knowledge is required to operated it<br />
<br />
* <span style="color:red">'''RED'''</span> - You must be inducted by the maintainer / trainer and signed off as being competent<br />
* <span style="color:orange">'''ORANGE'''</span> - You must read all the provided information and assess yourself as being competent of using the tool safely, if in doubt ask the area maintainer or other member for help<br />
* <span style="color:green">'''GREEN'''</span> - Fill your boots<br />
<BR><br />
<br />
==Equipment List==<br />
* [[Table saw]] - <span style="color:red">RED</span><br />
* [[Pillar Drill]] - <span style="color:orange">ORANGE</span><br />
* [[Sander]] - <span style="color:orange">ORANGE</span><br />
* [[Maslow]] - <span style="color:red">RED</span><br />
* [[Mortiser]] - <span style="color:orange">ORANGE</span><br />
* [[Wood Lathe]] - <span style="color:red">RED</span><br />
* [[Emco Bandsaw]] - <span style="color:orange">ORANGE</span><br />
* [[Milling Machine]] - <span style="color:red">RED</span><br />
<br />
== Power Tools List ==<br />
* Angle Grinders - <span style="color:orange">ORANGE</span><br />
* Jigsaws - <span style="color:orange">ORANGE</span><br />
* Cordless drill and driver (Makita) - <span style="color:orange">ORANGE</span><br />
* Corded drill - <span style="color:orange">ORANGE</span><br />
* Router - <span style="color:orange">ORANGE</span><br />
* Biscuit joiner - <span style="color:orange">ORANGE</span><br />
* Scraper<br />
* Random orbital sander - <span style="color:green">GREEN</span><br />
* 1/3 sheet orbital sander - broken <span style="color:green">GREEN</span><br />
* [[Planer]] - <span style="color:orange">ORANGE</span><br />
* [[Tormek sharpening system]] - <span style="color:red">RED</span><br />
* [[Dust extractor]] - <span style="color:green">GREEN</span><br />
* Vacuum cleaner (silver) - <span style="color:green">GREEN</span><br />
* Hyundai compressor - <span style="color:orange">ORANGE</span><br />
* Fret Saw - <span style="color:orange">ORANGE</span><br />
* [[Chop saw]] - <span style="color:orange">ORANGE</span><br />
* Air line - <span style="color:orange">ORANGE</span><br />
<br />
<br />
[[:Category:Equipment]]<br />
<br />
== Hand Tools List ==<br />
<br />
* Panel saw<br />
* Tenon Saw<br />
* Coping saw<br />
* Fret saw<br />
* Hacksaw<br />
* Junior hacksaw<br />
* Stanley knife<br />
* Tape measure<br />
* Ruler<br />
* Vernier callipers<br />
* Height gauges<br />
* Scribe<br />
* Engineers surface table<br />
* Engineers blue<br />
* Mortice gauge<br />
* Combination square<br />
* Tee square<br />
* wood chisels <br />
* sharpening stone<br />
* Claw hammer<br />
* Ball pain hammer<br />
* Pin Hammer<br />
* Mallet<br />
* Guillotine<br />
* Quick release vice<br />
* Engineers vice<br />
* Quick clamps<br />
* Sash cramps<br />
* Screwdrivers<br />
* Punches<br />
* Centre punches<br />
* Automatic punch<br />
* Drills<br />
* Spade bits<br />
* Hole saw<br />
* Tap and Die set<br />
* Assorted taps and dies<br />
* Engineers files<br />
* Wire brush<br />
* Wood rasp<br />
<br />
==Consumables==<br />
* Hacksaw blades - in the Drawer<br />
* Coping saw blades - in the Drawer<br />
* Craft knife blades - in the Drawer<br />
* Drills - in the Drawer<br />
* Sand paper - in the Drawer<br />
* Random orbital sandpaper- With the sander above the wood lathe<br />
* Bench sander paper - In the office<br />
* Bandsaw blades - Norfolk Saw Services<br />
* Wood glue PVA - Main wood bench<br />
* Gorilla glue - no<br />
* Super glue + activator - no<br />
* Wood stain (in laser room, shelf above blue table)</div>Mario Catlinhttp://wiki.norwichhackspace.org/index.php?title=04/20&diff=45204/202020-09-29T23:22:39Z<p>Mario Catlin: </p>
<hr />
<div>== Title ==<br />
<br />
<br />
== Proposer ==<br />
<br />
<br />
== Date proposed ==<br />
<br />
<br />
== Date for Decision ==<br />
Usually one week after posting <br />
<br />
== Cost ==<br />
<br />
<br />
== What is being asked for ==<br />
<br />
== Why/how this will be good to have ==<br />
<br />
<br />
== Who is for it ==<br />
<br />
<br />
== Who is against it and why ==<br />
<br />
== Outcome ==<br />
Agreed - Completed<br />
Agreed - waiting action<br />
Rejected - <br />
More information required<br />
On hold<br />
<br />
== Actions ==<br />
Who is taking this forward and what will they do?</div>Mario Catlin