Initial Questions: Project/Feature Name: True geolocation fields in Mozillians Tracking ID:920651 Description: Mozillians.org currently stores location data in user profiles in strings. This means we can't do some of the most interesting, most requested things that geographic data allows. For example, we can't really plot Mozillians on a map, or produce accurate metrics, since all we have is a bunch of string data. In particular, we might have people living in any/all of these places: Newyork New York City NYC NY City etc. This project will simply replace those string fields with true geographic data fields, which will normalize the data and make possible some features that users have long requested (like being able to indicate on a map that all of those people live in the same place). The only reason I'm filing this bug is to alert the privacy team to this change and field any questions they have. Additional Information: Key Initiative: 10x increase in contributors Release Date: 2014-03-31 Project Status: development Mozilla Data: Yes Mozilla Related: Mozillians.org Separate Party: No
Bug 976342 - Security Review: True geolocation fields in Mozillians Bug 976343 - Legal Review: True geolocation fields in Mozillians Bug 976344 - Privacy-Technical Review: True geolocation fields in Mozillians Bug 976345 - Privacy-Policy Review: True geolocation fields in Mozillians
Summary: True geolocation fields in Mozillians → Project Review: True geolocation fields in Mozillians
This code has been PR'd and will be merged sometime in the next week, and thereafter will be on the dev/staging servers for a week or so to test. Please reach out with any questions/concerns. Thanks!  https://github.com/mozilla/mozillians/pull/909/files
We released the true geolocation fields in June and it's been well received! http://dailycavalier.com/2014/06/better-location-information-on-mozillians-org-profiles/ Marking as resolved.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.