Freegle Affiliation Policy: Difference between revisions

From Freegle Wiki
Jump to navigationJump to search
m (Protected "Freegle Affiliation Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
This Policy was adopted by the Board at their meeting of 29th October 2014 and subsequently amended in February 2016.
This Policy was adopted by the Board at their meeting of 29th October 2014 and subsequently amended in February 2016 and December 2016.


The Board delegates responsibility to the Group Affiliation Team (GAT) to handle applications and implementation of procedures for new groups that wish to affiliate to Freegle.   
The Board delegates responsibility to the New Groups Team (NGT) to handle applications and implementation of procedures for new communities that wish to affiliate to Freegle.   


===Local Groups===
===Local Communities===
*Applications are considered from individuals who wish to affiliate a group to Freegle and who agree to run their groups to the current [[Group Affiliation Requirements Policy]]. In order to comply with these requirements when considering approval GAT defines:
*Applications are considered from individuals who wish to affiliate a community to Freegle and who agree to run their communities to the current [[Group Affiliation Requirements Policy]]. In order to comply with these requirements when considering approval NGT defines:
**Core Area: Groups will not be approved by GAT in the future within that area (1).
**Core Area: Communities will not be approved by NGT in the future within that area (1).
**Catchment Area: Individual group owners decide their own catchment areas. The catchment area is the geographic area within which a group accepts posts and members.
**Catchment Area: Individual communities owners decide their own catchment areas. The catchment area is the geographic area within which a group accepts posts and members.
*Where there are gaps in provision Freegle can proactively encourage new groups to be set up in line with this policy.
*Where there are gaps in provision Freegle can proactively encourage new communities to be set up in line with this policy.
*Groups should come from a local requirement for them. Our aim is to have locally run and locally promoted groups, but there is no volunteer residency requirement or limit to the number of groups that can volunteers run, as long as the set up of each group is in the best interests of the community, the volunteers and Freegle.
*Communities should come from a local requirement for them. Our aim is to have locally run and locally promoted communitess, but there is no volunteer residency requirement or limit to the number of communities that can volunteers run, as long as the set up of each community is in the best interests of that area, the volunteers and Freegle.
*New groups will not be approved in a core area where there is an active (more than 10 posts per month) Freegle group.
*New communities will not be approved in a core area where there is an active (more than 10 posts per month) Freegle community.
*Freegle affiliated groups are not in competition with each other.
*Freegle affiliated communities are not in competition with each other.




Note(1)
Note(1)


Freegle only affiliates one group per core area and it is highly recommended that an affiliated group operates only in that area.  Freegle may approve a specialist group in the same area as a standard group.
Freegle only affiliates one community per core area and it is highly recommended that an affiliated community operates only in that area.  Freegle may approve a specialist community in the same area as a standard community.


Note (2)  
Note (2)  


Groups will tend to be more resilient and thrive better when they are rooted in the community and it should be the aim of every group to have at least one person on the volunteer team who is part of that community.  
Communities will tend to be more resilient and thrive better when they are rooted in the area/community and it should be the aim of every community to have at least one person on the volunteer team who is part of that area.  


Note (3)
Note (3)


The [[Freegle Volunteer Agreement]] outlines the expectations of Freegle and Volunteers.
[[Our Aims]] outlines the expectations of Freegle and Volunteers.




====Links:====  
====Links:====  
*[[Group Affiliation Team - GAT]]
*[[New Groups Team - NGT]]
*[[Affiliation Procedure]]
*[[Document Approval Policy]]
*[[Document Approval Policy]]
*[[Glossary]]
*[[Glossary]]
*Previous Freegle UK document - [[Group Affiliation Team Freegle Affiliation Policy]]
*Previous Freegle UK document - Group Affiliation Team Freegle Affiliation Policy


[[category:Policies, Procedures, Remits]][[category:Group Affiliation Team]]
[[category:Policies, Procedures, Remits]][[category:New Groups Team]]

Latest revision as of 12:33, 14 November 2024

This Policy was adopted by the Board at their meeting of 29th October 2014 and subsequently amended in February 2016 and December 2016.

The Board delegates responsibility to the New Groups Team (NGT) to handle applications and implementation of procedures for new communities that wish to affiliate to Freegle.

Local Communities

  • Applications are considered from individuals who wish to affiliate a community to Freegle and who agree to run their communities to the current Group Affiliation Requirements Policy. In order to comply with these requirements when considering approval NGT defines:
    • Core Area: Communities will not be approved by NGT in the future within that area (1).
    • Catchment Area: Individual communities owners decide their own catchment areas. The catchment area is the geographic area within which a group accepts posts and members.
  • Where there are gaps in provision Freegle can proactively encourage new communities to be set up in line with this policy.
  • Communities should come from a local requirement for them. Our aim is to have locally run and locally promoted communitess, but there is no volunteer residency requirement or limit to the number of communities that can volunteers run, as long as the set up of each community is in the best interests of that area, the volunteers and Freegle.
  • New communities will not be approved in a core area where there is an active (more than 10 posts per month) Freegle community.
  • Freegle affiliated communities are not in competition with each other.


Note(1)

Freegle only affiliates one community per core area and it is highly recommended that an affiliated community operates only in that area. Freegle may approve a specialist community in the same area as a standard community.

Note (2)

Communities will tend to be more resilient and thrive better when they are rooted in the area/community and it should be the aim of every community to have at least one person on the volunteer team who is part of that area.

Note (3)

Our Aims outlines the expectations of Freegle and Volunteers.


Links:

Retrieved from "https://wiki.ilovefreegle.org/index.php?title=Freegle_Affiliation_Policy&oldid=54528"