Desired Outcomes

Primary

1. A collective can indicate using some kind of geolocation where they are active.
2. A collective can indicate where they are based using a precise mailing-address structure (this requirements seems at the moment to apply more for Europe then for the USA).
3. Migrating the (tag-based) implementation in Discvoer to use "where do you operate" geolocation information.

Secondary

1. Events and Projects can also be assigned a geolocation (which will add a layer of complexity to Discover, one collective can have numerous budgeted projects in different locations).

Considerations

1. What UI component(s) do we want to use for entering geolocation and specific address information?
2. Changing location input effects:
   • Collective creation
   • Collective settings
   • Collective profile
   • Notifying existing collectives (this should probably be done by fiscal hosts) they can update their information.
3. What is involved in the trasition process from the tag-based discover solution to geolocation (changing discover, converting tag-based information to geolocation, removing tags).
4. How do location choices effect open-source collectives?
5. If we choose to work with Google does that have any security implications (such as collectives making themselves unconsciously known to Google).
6. There is a potential (though hypothetical at this point) that spam collectives can abuse any potential to input multiple addresses.
7. Is there a good reason to consider creating a table for storing multiple addresses.