Start Group Report 2011-07 - Revision history

Jacky at 01:38, 3 December 2019

2019-12-03T01:38:16Z

← Older revision		Revision as of 01:38, 3 December 2019
Line 13:		Line 13:
	<br>		<br>
	====Area Guidelines====		====Area Guidelines====
	The ongoing discussion on area guidelines highlighted the difficulties that [[Freegle Start~~\|Start]]~~ have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start~~\|Start]]~~ to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start~~\|Start]]~~ will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.		The ongoing discussion on area guidelines highlighted the difficulties that Freegle Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for Freegle Start to identify the issues that are problematic for the Group Affiliation Team. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the Group Affiliation Team to cite more details in a small number of individual cases. The outcome of discussions held on Freegle Start will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.
	Discussion now continues on the specific case that prompted this change.		Discussion now continues on the specific case that prompted this change.
	<br><br>		<br><br>
Line 25:		Line 25:
	<br><br>		<br><br>
	====Disaffiliation Process====		====Disaffiliation Process====
	At the request of ~~the [[~~Freegle Structure~~\|Structure Working Group]]~~ the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the [https://spreadsheets.google.com/pub?key=tqddy50ztdbWKFn-53cHTJw Task List].		At the request of Freegle Structure the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the [https://spreadsheets.google.com/pub?key=tqddy50ztdbWKFn-53cHTJw Task List].
	<br><br>		<br><br>

	====Affiliation Requirements====		====Affiliation Requirements====
	In October 2009 volunteers ~~[[polls\|~~voted]] that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers ~~[[polls\|~~voted]] that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. The [[Group Affiliation Team]] have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. The details of this task are being considered.		In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the Group Affiliation Team can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. The Group Affiliation Team have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. The details of this task are being considered.
	<br><br>		<br><br>

	====Wiki====		====Wiki====
	The information on the Wiki relating to the [[Freegle Start~~\|Start Working Group]]~~ and the [[Group Affiliation Team]] procedures and policies is being revised.		The information on the Wiki relating to the Freegle Start and the Group Affiliation Team procedures and policies is being revised.

	<br><br>		<br><br>

	Back to [[Freegle Start]] or go to next report [[Start Group Report 2011-08]]		Back to Freegle Start or go to next report [[Start Group Report 2011-08]]

Alison at 11:49, 3 August 2011

2011-08-03T11:49:30Z

← Older revision		Revision as of 11:49, 3 August 2011
Line 20:		Line 20:
	Previous discussion on groups with low message numbers had resulted in a general agreement that thought should be given on how to support groups to grow. There had been support for a buddy/mentor scheme. Suggestions were made on how this and other ideas could be implemented and at what point it is appropriate to offer help.		Previous discussion on groups with low message numbers had resulted in a general agreement that thought should be given on how to support groups to grow. There had been support for a buddy/mentor scheme. Suggestions were made on how this and other ideas could be implemented and at what point it is appropriate to offer help.
	<br>		<br>
	Issues surrounding owners who do not respond to communications from Freegle were discussed. The task of writing a procedure for declaring groups defunct was added to the ~~task list~~		Issues surrounding owners who do not respond to communications from Freegle were discussed. The task of writing a procedure for declaring groups defunct was added to the [https://spreadsheets.google.com/pub?key=tqddy50ztdbWKFn-53cHTJw Task List].
	<br>		<br>
	It was emphasised that providing support for groups is the preferred way of dealing with groups with low message numbers.		It was emphasised that providing support for groups is the preferred way of dealing with groups with low message numbers.

Alison: /* Disaffiliation Process */

2011-08-03T11:36:15Z

Disaffiliation Process

← Older revision		Revision as of 11:36, 3 August 2011
Line 25:		Line 25:
	<br><br>		<br><br>
	====Disaffiliation Process====		====Disaffiliation Process====
	At the request of the [[Freegle Structure\|Structure Working Group]] the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the Task List.		At the request of the [[Freegle Structure\|Structure Working Group]] the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the [https://spreadsheets.google.com/pub?key=tqddy50ztdbWKFn-53cHTJw Task List].
	<br><br>		<br><br>

Alison: /* Area Guidelines */

2011-08-03T11:31:37Z

Area Guidelines

← Older revision		Revision as of 11:31, 3 August 2011
Line 13:		Line 13:
	<br>		<br>
	====Area Guidelines====		====Area Guidelines====
	The ongoing discussion on area guidelines highlighted the difficulties that Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start\|Start]] to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start\|Start]] will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.		The ongoing discussion on area guidelines highlighted the difficulties that [[Freegle Start\|Start]] have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start\|Start]] to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start\|Start]] will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.
	Discussion now continues on the specific case that prompted this change.		Discussion now continues on the specific case that prompted this change.
	<br><br>		<br><br>

Alison: /* Wiki */

2011-08-03T11:29:58Z

Wiki

← Older revision		Revision as of 11:29, 3 August 2011
Line 33:		Line 33:

	====Wiki====		====Wiki====
	The information on the Wiki relating to the Start Working Group and the [[Group Affiliation Team]] procedures and policies is being revised.		The information on the Wiki relating to the [[Freegle Start\|Start Working Group]] and the [[Group Affiliation Team]] procedures and policies is being revised.

	<br><br>		<br><br>

Alison: /* Affiliation Requirements */

2011-08-03T11:28:00Z

Affiliation Requirements

← Older revision		Revision as of 11:28, 3 August 2011
Line 29:		Line 29:

	====Affiliation Requirements====		====Affiliation Requirements====
	In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. The [[Group Affiliation Team]] have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. ~~and the~~ details of this task are being considered.		In October 2009 volunteers [[polls\|voted]] that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers [[polls\|voted]] that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. The [[Group Affiliation Team]] have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. The details of this task are being considered.
	<br><br>		<br><br>

Alison: /* Affiliation Requirements */

2011-08-03T11:20:27Z

Affiliation Requirements

← Older revision		Revision as of 11:20, 3 August 2011
Line 29:		Line 29:

	====Affiliation Requirements====		====Affiliation Requirements====
	In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. ~~GAT~~ have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. and the details of this task are being considered.		In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. The [[Group Affiliation Team]] have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. and the details of this task are being considered.
	<br><br>		<br><br>

	====Wiki====		====Wiki====
	The information on the Wiki relating to the Start Working Group and the [[Group Affiliation Team]] procedures and policies is being revised.		The information on the Wiki relating to the Start Working Group and the [[Group Affiliation Team]] procedures and policies is being revised.

Alison: /* Disaffiliation Process */

2011-08-03T11:18:26Z

Disaffiliation Process

← Older revision		Revision as of 11:18, 3 August 2011
Line 25:		Line 25:
	<br><br>		<br><br>
	====Disaffiliation Process====		====Disaffiliation Process====
	At the request of the Structure Working Group the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the Task List.		At the request of the [[Freegle Structure\|Structure Working Group]] the task of writing a procedure for groups that do not adhere to the mandatory affiliation requirements has been added to the Task List.
	<br><br>		<br><br>

	====Affiliation Requirements====		====Affiliation Requirements====
	In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. GAT have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. and the details of this task are being considered.		In October 2009 volunteers voted that it should be a mandatory requirement that only one group per area should be affiliated. In January 2010 volunteers voted that operating in a geographic area agreed with Freegle should only be highly recommended (not mandatory). This means that the [[Group Affiliation Team]] can only affiliate one group per area but it is not mandatory for them to agree a geographic area with new group owners. GAT have dealt with this by establishing core areas and catchment areas for new groups. There was discussion as to whether the core area covers the one group per area requirement and the catchment area meets the highly recommended requirement to operate in a geographic area agreed with Freegle. It was felt that it would be useful for the core areas of all Freegle groups to be recorded. and the details of this task are being considered.

Alison: /* Area Guidelines */

2011-08-03T11:16:33Z

Area Guidelines

← Older revision		Revision as of 11:16, 3 August 2011
Line 13:		Line 13:
	<br>		<br>
	====Area Guidelines====		====Area Guidelines====
	The ongoing discussion on area guidelines highlighted the difficulties that Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start\|Start]] to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start\|Start] will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.		The ongoing discussion on area guidelines highlighted the difficulties that Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start\|Start]] to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start\|Start]] will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.
	Discussion now continues on the specific case that prompted this change.		Discussion now continues on the specific case that prompted this change.
	<br><br>		<br><br>

Alison: /* Area Guidelines */

2011-08-03T11:15:30Z

Area Guidelines

← Older revision		Revision as of 11:15, 3 August 2011
Line 13:		Line 13:
	<br>		<br>
	====Area Guidelines====		====Area Guidelines====
	The ongoing discussion on area guidelines highlighted the difficulties that Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for Start to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on Start will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.		The ongoing discussion on area guidelines highlighted the difficulties that Start have in discussing and formulating policy based on generalised/anonymised information about a current application. It is difficult for [[Freegle Start\|Start]] to identify the issues that are problematic for the [[Group Affiliation Team]]. It was therefore agreed to amend the guidelines that they use by adding a paragraph to allow for the [[Group Affiliation Team]] to cite more details in a small number of individual cases. The outcome of discussions held on [[Freegle Start\|Start] will then set a precedent for future new applications.. The amended guidelines were agreed by a majority poll.
	Discussion now continues on the specific case that prompted this change.		Discussion now continues on the specific case that prompted this change.
	<br><br>		<br><br>

	====New Group Support====		====New Group Support====
	Previous discussion on groups with low message numbers had resulted in a general agreement that thought should be given on how to support groups to grow. There had been support for a buddy/mentor scheme. Suggestions were made on how this and other ideas could be implemented and at what point it is appropriate to offer help.		Previous discussion on groups with low message numbers had resulted in a general agreement that thought should be given on how to support groups to grow. There had been support for a buddy/mentor scheme. Suggestions were made on how this and other ideas could be implemented and at what point it is appropriate to offer help.