martinhowarth/melinda

Melinda is a match-making service for informal mentoring and pastoral support.

melinda's Issues

Create a help page describing how the service works

Remember which nested tab the user was on so it's consistent between navigating away and back again

Make the settings page actually do something

Make the "Location" settings field work

Blocked by #19

Mentors/mentees should be able to optionally filter matches by location

Make swipe to accept/reject matches work on touch screens

Requires some javascript voodoo!

Needs testing on multiple browsers. Also testing on desktop browsers (the first try at implementing this broke desktop drag-and-drop).

Add a "skip match" button

If you don't want to decide on a match immediately, a skip button might be useful.

Make postgres database addon in circle CI actually work - tests appear to time out trying to connect to it

Don't allow/show matches with yourself

Login/authentiaction hits problems

400. That’s an error.

Error: redirect_uri_mismatch

The redirect URI in the request, http://metaswitch-tinder.herokuapp.com/oauth2_callback, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/228552424448-cq22tllg54gfa966eacro1p7sj8jk96i.apps.googleusercontent.com?project=228552424448

Learn more

Request Details
response_type=code
client_id=228552424448-cq22tllg54gfa966eacro1p7sj8jk96i.apps.googleusercontent.com
redirect_uri=http://metaswitch-tinder.herokuapp.com/oauth2_callback
scope=email
That’s all we know.

Allow users to specify their own image.

Easy solution: Allow users to give a url to the image.

Hard solution: Allow users to upload an image. Dash has file upload functionality, but we need to find a way to store it. Look into heroku addons? (worried about just base64 encoding it and store in the existing database - might be too much data?)

The custom image should then be shown to users on the match screen, and the setting screen.

Allow mentees to delete outstanding requests

Include details about the request in the mentee match page

When a mentee sees a match, they should see which request that match is for - they may have made multiple requests.

Make hitting the Enter key work (for submitting forms)

Most pages have an obvious "main button" that the Enter key should hit - this issue covers making this app do that.

Improve signin / signup experience

There are a few problems here, they are closely related so might be solved by one solution (rather than having multiple github issues)

Authentication:

I don't like the user experience of either of the examples here: https://dash.plot.ly/authentication

The reason for that is that users have the signin before getting into using the app. I think that signin/signup should happen as late as possible to streamline the process.

Feedback when a signin/singup request fails

This one is pretty obvious. Currently if these fail then the user is taken to the next page without warning and the UX is weird.

Wait for signin/signup to return before loading the next page

[This is resolved very hackily right now - consider improving alongside a wider fix here]
Slightly tangential to the previous point. Even on successful login, the session['username'] variable is not set before the next page loads, which can impact on its content. We should instead wait for signin to complete before loading the next page.

Create instructions for setting up a test postgres database on [windows|linux]

And add it to the README.

This should include a simple way to populate that test database with sample data - this is one step towards supporting integration tests.

Split out matches by mentor/mentee type

A user can be both a mentor and a mentee. They need to be able to see matches for those two things separately and clearly distinct from each other

Add ability for mentees to view/edit/delete the requests they have made

Make cursor auto-focus into the first input box on each page

E.g. when on the sign-in page, it should place the cursor in the username field to save the user having to click on it, or tab to it.

Feedback when signin/signup fails

Currently, if signin or signup is rejected, the user is taken to the next page anyway with no notice other than they are silently not logged in.

Might overlap with #6

Make the delete account button work

Need to:

• purge user from the database
  • That includes from all requests they're part of
• force logout

Cache matches so the pages load faster

Will need to add a refresh button as well.

Work out how to do database migrations (e.g. for changing the db models)

And add code/docs that helps the next person do it!

Come up with suggestions that a matched pair can take to get started

This does not cover actually implementing any of these, just coming up with ideas, discussing them and opening issues for implementing them. (Though, feel free to implement them as well!)

For example:

• steps to include in an email to them
• Calendar integration
• Links to resources for mentors to learn how to mentor

"i have an account" button doesn't work

Make the "report" button useful

• Make sure the emails actually go somewhere
• Bit more text on the page to explain how to use and what will happen
• Link to github
• Ack page after submission.

Add usage metrics/statistics

This issue covers getting usage data/metrics out of the app. For example:

• Typical workflows that users take (so we can optimise for those?)
• Number of matches
• What tags matches have been for
• ???

Add ability for users to specify their own tags

There is currently a hard-coded list of tags. Probably want to store the tags in the database instead to enable submission of new ones