hackru / helpq Goto Github PK

this one may require some coordination with MnD.

add an endpoint so mobile users can just give they're login token and see helpq inside the app

you have to pay 7$/month for a hobby dyno in order to add https to a heroku app. i may just do that only for the month of the hackathon. or i can get really silly and do ssh tunneling to an ec2 instance or something. then use nginx and lets encrypt to get https. either way the plan is to do lets encrypt to get a free ssl certificate

should phone be the only contact method to keep things simple and have mentors be able to respond.
i believe on desktop it lest you put anything as phone but mobile gives you a dialpad

The text is white lmqo

this is important because blah blah man in the middle blah responsibility

• change the behavior of login to update user role on login.
• forcefully making a user a mentor should not happen from the helpq admin panel.
• also manualy adding users/mentors should not happen from helpq panel, but adding admins should.

it looks a bit drab

currently rooms is fetched server side. this is silly because if the rooms change the server must be restarted. instead the url should be passed to the client, and then the client should fetch rooms.json for itself so that updates just require a page refresh.

alternatively the server could fetch it on login

change colors and assets to make helpq look more like this year's hackru.org.
assets are available in the assets channel (or can just be stolen directly from the website)

when i snap firefox to the right or left some text on the form goes of the page

We want READMEs with todo lists, just so that we and other people know which issues you're prioritizing.

Please add.

(Side-note: the CONTRIBUTING.md is pretty sick, just confirm that it says what you want it to.)

description on ticket
optional add tags

view for volunteers/organizers to log in and see all tickets/see if tickets are getting served

the idea is to do production environment testing or and QA by other teams

copy off of some other login meteor package to hack in lcs integration

Add IP Whitelist to installation instructions

T_T while the login form is waiting for a response from server, show a login bar

once people have one ticket filled show them a link to a feedback survey. also be able to email everyone for feedback after the hackathon.

if a user logs in and they are marked as a mentor in lcs then give them the mentor role in helpq

see HELPQREADME.md, also see constants.js
this will change the text of the application so things say HackRU mentor queue or something

is lcs good enough for mentors to login?

see handbook for details

I think it might be useful for someone requesting help to also be able to pin a location on a map so they don't have to describe their surroundings in a text box. I would imagine that the person requesting help will set the location when submitting a ticket (doesn't have to be their current location, could be just a meeting point). This shouldn't replace the text box though because they provide other details like shirt color or whatever.

Things to consider

• For the CASC, there are 3 floors. Maybe have a tab for each floor like how Google maps handles multicolor buildings
• The map should be zoomable and pan-able, like how Google maps is.

@hariamoor suggested adding an Integration with Stack Exchange to provide extra help while hackers are waiting for a mentor. We thought the best way to implement this was to add a few suggested Stack Exchange threads to the hacker's dashboard (the page the land on to wait for a mentor to pull their ticket).
some other ideas were adding a sidebar with suggestions to the ticket creation form, but that runs into issues, with sending too many api requests from live updating.
another implementation idea was to have an extra dialogue before they submit a ticket that has the suggestions, but it was decided that putting them on the dashboard instead allowed them to ignore the suggestions more easily instead of having an extra dialogue to go through.
another implementation idea was to use NLP to provide better relevancy, but we should probably see how good the relevancy is without NLP first, before we go too overboard.

things to get this implemented

• create a stack overflow suggestions component that fetches the suggestions from the helpq server when it fetches the ticket itself
• add extra logic to the ticket creation method (on server side) that does the api request to Stack Exchange and attaches them to the ticket in the database
• add the suggestions component to the ticket component or add it under the ticket on the hacker's dashboard.