==== Background/Goal
Now that T305705 is complete and a [[ https://docs.google.com/document/d/1c4Wh-BA_Ahl2syG64EPjCPcj4uEhT6K-0pjH00J9tEs/edit#heading=h.be7f5qt8jr2x | proposal ]] has been drafted, we will solicit review from:
- Legal
- Trust & safety policy
- Security
Out of scope for this task:
- Budget approval & any necessary contracting with geolocation provider
- Implementation of the geolocation API
===== User stories
- As a Campaigns team member, I want to ensure that our recommended approach of setting up a proxy to [[ https://github.com/pelias/pelias | Pelias ]] web service has been reviewed & commented on by Legal, Trust & Safety Policy, and Security so that I have a more complete understanding of risks & recommended next steps.
- As a campaign organizer, I would like to be able to easily enter the address of my in-person event.
- As a campaign participant, I would like to be able to quickly know where the in-person event is taking place.
===== Considerations
- Once we start using a geocoding library, there may be backwards compatibility issues with existing events (e.g. someone entered an invalid address or country, or in a format that the library does not recognize), and this could be very problematic. Therefore, we should decide on a geolocation API provider in parallel with our V0 build, even though it will not actually be implemented until V1 (target: October 2022).
===== Development considerations
MUST HAVE
- Being able to filter events by country, city, and region.
- Show only relevant info in the event page bar; e.g., the building name
NICE TO HAVE
- Provide address autocompletion when creating/updating a registration
- Show events happening nearby
- Show where the event is happening on a map
===== Acceptance criteria
[] Reviews are complete:
[] Legal
[] T&S Policy
[] Security
===== Test scenarios
n/a
===== Open questions
- What timeline should we expect for reviews?
- Just curious what the technical reasons are for choosing Pelias over MaxMind, for which the WMF already has a license.