ehzhang/helpq

💁 an extensible real-time queue application, for mentorship @ hackathons and classrooms

helpq's Issues

spacing for mentor leaderboard gets messy in the double digits.

If there are 10+ mentors, the spacing between names and numbers in the leaderboard gets a little small.

See # 10 in the attached image.

Thanks!

Still uses "hunter2" as admin password

Even after changing the admin password in config.json, the application still requires "hunter2" as the password for the admin account.

[Feature] Add Slack integration

Here's a wishlist for Slack integration:

• A webhook to Slack that will post into a "mentor feed" channel on ticket updates.
• A route that users in Slack can use via a slash command to create, cancel, and get their tickets.

[Feature] Password Change

Ability for a user to change their own password.

[Feature] Request specific mentor

Would be helpful for cases where people get help with someone, but then later have a follow up question on the same issue.

We could either sort tickets differently (e.g. show tickets directed to a given mentor first for that mentor) or have an extra tag on the tickets with the requested mentor name.

Save "How can we help you?" input and display while waiting

(context: at Hack@Brown)
It would potentially be a nicer user experience for the requestee to be able to view the form submission while waiting for a mentor – just to have a reference to what he/she requested help on.

If you agree, I could implement it if you don't want to.

Add a chat feature

I recently used this as a mentor for Hack OHI/O and noticed that a large, important feature this is lacking is the ability to chat directly with the hackathon participants submitting tickets. This was an issue because there were almost a thousand participants and it was sometimes hard to find the people that submitted the ticket.

Deploy to Heroku button

Do you think it would be helpful to have a deploy to heroku button (e.g. {link})?

To make this not a pain to use, we'd need to add support for using environment variables in addition to the config.json (should be fairly straightforward), because ideally people should be able to set this up using only the Heroku web UI. Besides that, we'd probably want to do something with how the admin account works so people can change the password via config file (so people don't have issues like #1).

I had already written some config code to make this work on Heroku (for 6.S191), though I haven't done the envvar stuff.

If you think this is a good idea, I can start working on a PR.

Facebook login doesn't work

The meteor version is so old that it is using an outdated version of the FB Oath API. Potential quick fix here: https://github.com/fede-rodes/facebook-accounts-patched

request to update quick-deploy link to not use mlab

MLab is deprecated

How do hackers access the portal?

While I'm using this application to sign up mentors, Im conceded about how hackers could sign up for the application and post questions. Because it seems like Users can only either be an admin or a mentor. Is it there no implementation for hackers login? Or they have to use facebook / GitHub?

Problems getting Github oAuth to return to the user's page.

This is my first time using Github oAuth and I'm having a bit of a problem.

I have assigned Github OAuth's client ID and User Secret to config.json, and "enable" is set to true. But when I sign in with Github using the "Login With Github" button, it takes me back to the HELPq's login page instead of the homepage.

In my Oauth applications, I am setting the homepage URL to:

http://nameofwebsite.com

and I am setting the Authorization callback URL to:

http://nameofwebsite.com:3000 <-- the application runs on port 3000

I should also mention that when it returns to the login page, I see this in the url:
nameofwebsite.com:3000/error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application

Am I not properly assigning these URLs? Please let me know what you guys think.

Suggestion: Trim username at the login page before attempting to log in

Currently logging into Helpq requires you avoid spaces before and after typing in your username. So this input will not work:
username: " admin "
password: "hunter2"

My fork has made changes so that the above input works. Of course, only the username is trimmed, not the password. If you would like to implement this change, I've included the modified code block. This change is made in client/components/login/login.js :

  Meteor.loginWithPassword(
      $(t.findAll('#username')).val().trim(),
      $(t.findAll('#password')).val(),
      function(error){
        if (error){
          $(t.findAll('#password')).val("");
          t.error.set(error.reason);
        }
      }
  )
}

Setup and running

How do I set up this and run on localhost ?

Proposed Feature List v0.3

• Show user ticket content after submit (Easy)
• Ticket Categories and Mentor Filtering

Quickstart Errors

When following Quickstart instructions for Mac/Linux (./create_config && meteor):

It appears ./create_config completes fine, giving back the following output:

Server side config created.
Edit it in private/config.json to add Facebook or GitHub integration.

However, program spits back these errors when meteor runs with no edits to any files on a fresh install of Meteor:

=> Started proxy.

=> Meteor 1.3: ES2015 modules, npm integration, app testing, mobile
improvements, and more.

This release is being downloaded in the background. Update your app to
Meteor 1.3 by running 'meteor update'.

=> Started MongoDB.
=> Errors prevented startup:

While downloading [email protected]...:
error: getaddrinfo ENOTFOUND

While downloading [email protected]...:
error: getaddrinfo ENOTFOUND

=> Your application has errors. Waiting for file change.

Github OAuth Broken

Like #31 , the OAuth for logging in with Github doesn't seem to work and instead brings up a 404. Can I expect this to be resolved soon? I'm working on deploying HELPq for a hackathon.

Outdated version of iron:middleware-stack

iron:middleware-stack version listed in .meteor/versions is outdated and causes the error specified in this stackoverflow thread.