[Design] New hangout flow - homepage

[lpatmo]

[lpatmo]

A couple of notes:

• a user won’t be asked to enter their timezone and general availability again and again, if they’ve already entered it during account signup
• this idea is similar to the CB Connect flow, but the big difference is that we won’t be matching users.
• Design upcoming for what the “I am looking for ___” list of posts looks like.
• After someone fills out their info, they’ll be able to click a button to start a hangout
• The checkbox is meant to allude to a private session vs. a public session 😅 Feedback welcome re: how to word it better

[BethanyG]

For the session "toggle" how about:

or

[lpatmo]

LOVE THAT WORDING

... have never thought of using the proper noun CodeBuddies in that particular way, but I kinda like it, heh, since "open to additional code buddies" (lowercase) strikes me as slightly worse

[lpatmo]

From @tgrrr: "Maybe some code tags rather than a text area for the I hope to pair on"

[BethanyG]

Or a place to put a link to a particular resource/topic!

[lpatmo]

Would it be easier to implement search on a freeform text input field for the MVP?

[BethanyG]

I was imagining something (really roughly) like:

[lpatmo]

"And multi step forms tend to get more people complete them" - @tgrrr

[lpatmo]

"Maybe the city time zone aspect can be moved to an account set up process so they don’t have to enter that in every time" - @angelocordon

[angelocordon]

IMO that's a secondary kind of information (something that you'd hide behind a tooltip or something). I can see it being useful but perhaps not strictly important.

[angelocordon]

Just articulating my thoughts here:

As someone looking for pairs, I want to find pairing events that can match my schedule. Displaying this in their time zone instead of the event owner's time zone would make the user experience smoother as we lessen the mental gymnastics of trying to calculate availability for the user.

As someone creating pairing events, I would want this in my time zone as well; I know what time I'm available but don't necessarily think about what time zone I'm in or other's timezones.

Overall, technically speaking: when we save these events, it should be in UTC time (in the database). When presenting events, it should be in the timezone of the person's viewing it.

Hope that makes sense!

[lpatmo]

Cool! What you described is the behavior we currently we have on codebuddies.org/hangouts, so I agree we'd want to recreate it.

I mainly wanted to confirm whether it'd be helpful for the user to see the timezone from the OP's POV in addition to their own, which is what World Time Buddy has:

[angelocordon]

Rad!

Re:

I mainly wanted to confirm whether it'd be helpful for the user to see the timezone from the OP's POV in addition to their own

🤷🏽‍♂️ Honestly, I don't know. It sounds like not something we need to get out of the gate with; I'd suggest we take note of the idea and implement it if we find a need for it in the future.

[lpatmo]

Thanks, that's good feedback 😉 -- I won't include on a priority list.

[lpatmo]

"I'm generally available...
Maybe some day of the week checkboxes,
And times could be either morning, afternoon, evening, the wee hours, or other.
Or a slider with times.
Or we could use chips inside of the textbox https://material-ui.com/components/chips/
The benefits of slightly more specific days and times is matching with others"

• @tgrrr

[BethanyG]

Yes - and to tag onto what @angelocordon has said above, this should be part of the register/profile flow as well, so that users don't have to enter it every time.

[lpatmo]

"Btw, might be cool when hangouts are closed, that a form pops up where people can put in their TIL and other feedback. But I would be happy to attend a follow up."

"You could even do this in an email format, or give people the profile option to either have it as a pop-up after the session or as an email, or to opt out."

• @bengineerdavis

[angelocordon]

I'd love this as a transactional email asking "how did your session go?" Maybe not just as a TIL but a way for us to collect feedback and maybe as a way to give feedback to others also (perhaps more anonymously).

[bengineerdavis]

It might be good to offer a checkbox that can authorize permission for a username to be supplied or to offer contact info to the dev team if they want to ask them questions. There should also always be an opt-out option. In fact, it would be in the spirit of open source that we always default to an opt-in model, and then send an email out reminding them about this feature, which they can then turn on later.

[BethanyG]

The opt-in opt-out has to be included for GDPR purposes, as I understand. Also for CA privacy laws, if I remember correctly. @billglover - any insights for GDPR? I'll look at the CA laws.

[billglover]

My understanding of GDPR centres on "informed consent" and "user control". I have not read the full regulations. If we wanted to share contact details we'd need to make it clear and receive consent from users that this is what we were going to do. They'd need the ability to withdraw this consent.

It might be good to offer a checkbox that can authorize permission for a username to be supplied or to offer contact info to the dev team if they want to ask them questions.

Is the aim to ensure that attendees on a hangout can continue to have a follow on conversation once the hangout is complete? When this has happened in the past we've just agreed during the hangout how we'll follow up. This is typically Slack. I have questions though:

• Do we mind where the follow up discussion takes place?
• Are the plans for a discussion feature over and above Slack?
• Do we have thoughts on how users might send messages to each other on CodeBuddies?

In the interests of simplicity, I'd favour leaving this functionality out of an initial release and relying on hangout participants to agree an approach for follow up. As we learn more about how hangouts are used we can add additional features to improve the experience.

[BethanyG]

For the CA law (full text here) I think the two biggies are (from a Vox Media summary article):

1. The right of Californians to know what personal information is being collected about them.

   What this means: A business must tell you that it collects personal information about you either before or as that information is collected.

2. The right of Californians to access their personal information.

   What this means: Businesses (and organizations) must offer you ways to request a copy of the personal information they have collected about you, and they must provide it free of charge within 45 days of your request. You have the right to know the types of personal information (for example: name, email, or location) a business has collected, where it came from, why it was collected, the categories of third parties it has shared that information with, and the specific pieces of information it has collected. You can also tell them to delete that information.

In addition, there is the CAN-SPAM law (summary from litmus here) requires that you:

• Include a working unsubscribe link in every promotional email you send
• Honor opt-out requests within 10 business days
• Include a mailing address in every email you send
• Never use misleading or deceptive sender names, subject lines, or email copy
• Never attempt to conceal the organizations identity or the fact that you are sending advertising

GDPR is stronger, in that sense, so following GDPR covers CAN-SPAM and the CA Law (looks like) as well.

I agree with @billglover -- I think maybe we leave the detailed functionality out of the MVP (but obviously consider how we build in systems to honor user privacy and the two laws.).