#286 We need to be able to get, and update, location information from hubs users
Opened 4 years ago by wispfox. Modified 4 years ago

If we are to be able to suggest nearby hubs and people, we need to know where people are. Because of this, I have created some basic mockups to get and confirm this information from people with existing FAS accounts, people who are creating new accounts, and allow them to update that info.


Subscribing to a hub when not logged in should be very similar to the sign up process, except when asking to use the GPS, we should explain why we want to know differently (eg: "We need to know where you are located so we can be sure you are near this group.").

A few more steps in the subscription/join process:

joining_a_regional_hub.png

Subscribing to a hub when not logged in should be very similar to the sign up process, except when asking to use the GPS, we should explain why we want to know differently (eg: "We need to know where you are located so we can be sure you are near this group.").

A few more steps in the subscription/join process:

joining_a_regional_hub.png

So it might be useful to have the new account creation mockups handy for the integration here:
https://pagure.io/fedora-hubs/issue/289

More feedback to follow.

I've updated stuff according to conversation with @duffy about handling the complication inherent in location information (https://meetbot.fedoraproject.org/fedora-hubs/2017-01-19/hubs-devel.2017-01-19-19.02.log.html)

This will appear after someone selects 'create account'
Who_are_you_modal.png

The remaining mockups are overlays to take the place of the one in the above mockup.

I've updated stuff according to conversation with @duffy about handling the complication inherent in location information (https://meetbot.fedoraproject.org/fedora-hubs/2017-01-19/hubs-devel.2017-01-19-19.02.log.html)

This will appear after someone selects 'create account'
Who_are_you_modal.png

The remaining mockups are overlays to take the place of the one in the above mockup.

When you press continue above, we want to know what to call you. Currently this includes only first name field and nickname field.

Questions: Should it also include lastname? Or let them choose something else entirely, given that some people will have multiple first names and it could get unwieldy?

name_preference.png

When you press continue above, we want to know what to call you. Currently this includes only first name field and nickname field.

Questions: Should it also include lastname? Or let them choose something else entirely, given that some people will have multiple first names and it could get unwieldy?

name_preference.png

Now we want to know where someone is.

Question: I'm not sure if we should let people refuse to say where they are, at least at the country level. This mockup doesn't let people entirely remove the city at the moment.

Where_are_you.png

edited to add:
I changed 'GPS info' to 'location info' in my local mockup because it seemed better that way.

Now we want to know where someone is.

Question: I'm not sure if we should let people refuse to say where they are, at least at the country level. This mockup doesn't let people entirely remove the city at the moment.

Where_are_you.png

edited to add:
I changed 'GPS info' to 'location info' in my local mockup because it seemed better that way.

We now show a map of where we think they are, based on their GPS info (for the first option). If they want to change their city, they can start typing in the box and it will use type-ahead to suggest things. This gets around the need to have them specify a state/province/or similar concept.

To Do: The map will need to be checked for a11y compatibility.
To Do: We need to make sure that our type-ahead has good a11y compatibility, both for people who cannot see the type-ahead suggestions and those who are not using the mouse to select them.

Found_you_GPS_map.png

We now show a map of where we think they are, based on their GPS info (for the first option). If they want to change their city, they can start typing in the box and it will use type-ahead to suggest things. This gets around the need to have them specify a state/province/or similar concept.

To Do: The map will need to be checked for a11y compatibility.
To Do: We need to make sure that our type-ahead has good a11y compatibility, both for people who cannot see the type-ahead suggestions and those who are not using the mouse to select them.

Found_you_GPS_map.png

Finally, what happens if we can't tell where you are (connection failure or something). I note that in my original mockup, the white box containing the lack of the map wasn't actually invisible. wry

not_sure_map.png

Finally, what happens if we can't tell where you are (connection failure or something). I note that in my original mockup, the white box containing the lack of the map wasn't actually invisible. wry

not_sure_map.png

Not done (based on what I see here: https://pagure.io/fedora-hubs/issue/289):

Security question/answer.
Age verification
Captcha

I also haven't included:
time zone (but maybe that can be figured out from what we learn, unless we have no info?)

Selecting regions/hubs.

I don't think that phone number needs to be requested on first account creation.

The rest of the location things I did (existing FAS account ones, privacy, updating location) still remain to adjust.

Comments from discussion with @sayanchowdhury:

Regions: rather than cities, moving to a bigger group to have more people in a hub = region?

The current thought is that Hubs can notice that a certain people are near each other, and suggest that they create a hub. If they are all in the same city, we'd suggest the city as the name. I'm not sure what we'd suggest as the name in the area bigger than a city case, as I'm not sure that there's any way to know what regions people have names for. Maybe we make a generic name and people can change it to what makes sense to them?

[11:07] @sayan hmm, that's a tough problem

Possible regional hubs would be automatically suggested to the people in them.
[11:09] <shillman> Someone in that list would need to take on the task of creating that hub and being the admin for it.,
[11:10] <shillman> Someone or someones.
[11:10] @sayan well then the issue is who would be the admin
[11:10] @sayan this will need a more detailed discussion, let's skip this for now
[11:10] <shillman> ok.

See issue #298

Do we let people select 'none' for country? I know that in FAS2, it's not required. It might be required in FAS3, and it certainly is relevant for reasons of embargos, I think?

Updated existing FAS, no info. Note, I'm uncertain about this because we're not asking about info, we're just pulling it from IP or GPS or browser location info. This doesn't easily support refusing to provide info, unless the detection fails. I could add a 'none' option to the country list, but that will be hard to realize is there. I have another alternative in the next one, where we are creating a new account. I will talk more there.

Step one a: We detect their location

First_login_without_FAS_info_-_step_one_a.png

Step one b: We fail to detect their location (because of a bad connection, who knows)

First_login_without_FAS_info_-_step_one_b.png

Step two, verify email (I think email is required in FAS? So we will have this, if nothing else?)

First_login_without_FAS_info_-_step_two.png

Step three, select regional hubs:

First_login_without_FAS_info_-_step_three.png

Updated existing FAS, no info. Note, I'm uncertain about this because we're not asking about info, we're just pulling it from IP or GPS or browser location info. This doesn't easily support refusing to provide info, unless the detection fails. I could add a 'none' option to the country list, but that will be hard to realize is there. I have another alternative in the next one, where we are creating a new account. I will talk more there.

Step one a: We detect their location

First_login_without_FAS_info_-_step_one_a.png

Step one b: We fail to detect their location (because of a bad connection, who knows)

First_login_without_FAS_info_-_step_one_b.png

Step two, verify email (I think email is required in FAS? So we will have this, if nothing else?)

First_login_without_FAS_info_-_step_two.png

Step three, select regional hubs:

First_login_without_FAS_info_-_step_three.png

Ah, but the terms should not be 'add these groups', but 'follow these groups'. Fixing in original mockup.

Update to the location-related settings page. I was wondering if we need a tab in here for the hubs one is following/a member of, as well. I'm not entirely clear how one gets this list otherwise.

Location_Settings_Page.png

Update to the location-related settings page. I was wondering if we need a tab in here for the hubs one is following/a member of, as well. I'm not entirely clear how one gets this list otherwise.

Location_Settings_Page.png

Do we let people select 'none' for country? I know that in FAS2, it's not required. It might be required in FAS3, and it certainly is relevant for reasons of embargos, I think?

For lots of reasons, I think you should not allow the selection of a country not listed in FAS. This will ensure that we don't run afoul of anything.

Also, can we get data pushed back to FAS so it remains usable by other components?

Yes, if possible the data would be pushed to FAS. This is true for other widgets too that pull data and update them if required.

Yes, if possible the data would be pushed to FAS. This is true for other widgets too that pull data and update them if required.

Have you engaged with @pingou (who I think is doing a FAS rewrite) to ensure that we will have landing places for the new data?

@bex: ok, thanks. I will definitely adjust things so that we aren't potentially allowing people to select no country.

@bex: ok, thanks. I will definitely adjust things so that we aren't potentially allowing people to select no country.

Selecting both "none/do not wish to disclose" and "other" are, I believe, both supported by FAS. What I mean is that there should be no country in the list of available countries that is not also in the FAS list.

Login to comment on this ticket.

Metadata
Attachments 52
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment
Attached 4 years ago View Comment