05/20 - Revision history

Mario Catlin: /* Comments */

2020-10-29T17:10:05Z

Comments

Mario Catlin: /* Comments */

2020-10-29T17:09:43Z

Comments

Mario Catlin: /* Comments */

2020-10-29T17:09:23Z

Comments

Mario Catlin: /* Comments */

2020-10-29T16:57:33Z

Comments

Mario Catlin: /* Comments */

2020-10-29T16:57:10Z

Comments

Mario Catlin: /* Comments */

2020-10-29T16:56:44Z

Comments

Mario Catlin: /* Outcome */

2020-10-29T16:44:31Z

Outcome

Mario Catlin: /* Comments */

2020-10-29T16:43:31Z

Comments

Mario Catlin: /* Outcome */

2020-10-29T16:29:40Z

Outcome

Mario Catlin: /* Outcome */

2020-10-29T16:27:21Z

Outcome

@@ Line 42: / Line 42: @@
 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.
-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?
+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?''
 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

@@ Line 46: / Line 46: @@
 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
-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.
+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.
+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.''
 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)

@@ Line 44: / Line 44: @@
 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?
-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
+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
 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.
+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.

@@ Line 46: / Line 46: @@
 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
-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.
+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.
 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)

@@ Line 46: / Line 46: @@
 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
-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 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.
 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)

@@ Line 40: / Line 40: @@
 == Comments ==
-The presentation was a
+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.
 == Outcome ==

@@ Line 44: / Line 44: @@
 == Outcome ==
-<!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.
+This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.
 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

← Older revision		Revision as of 16:43, 29 October 2020
Line 40:		Line 40:

	== Comments ==		== Comments ==
		+	The presentation was a

	== Outcome ==		== Outcome ==

← Older revision		Revision as of 16:29, 29 October 2020
Line 57:		Line 57:

	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.		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.
		+
		+	As immediate actions, we have a Core Team Slack channel and I am amending the New Member Guidelines to reflect the changes

@@ Line 45: / Line 45: @@
 <!-- This proposal was discussed at a Zoom meeting on Tuesday 27 October 2020 based on a structure presentation which also covered addressing issues raised.
-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
+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
 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.