Thanks for the feedback, that's definitely means a lot from you
Since we are not able to get whole set of github results at that moment so many results are not predictable. And we are still working on it to make it better.
Thanks for the comments John.
Class room setting was one the several things we had in mind. We started of with an idea of planning poker for sprint planning where everybody would take turns to cast their estimate on a given story. Then we thought this might as well be extended to any discussion or quiz like activity where everybody needs to vote in order to move to next item (item being question, story etc etc). So we thought of doing a backend which would be generic and capable enough to support all of these use cases and build specific UIs on top.
And for NKO, for the UI, we zeroed on to make it specific to quizzing experience which can be used in a classroom like setting as you said or in a quiz game show or someone preparing for an exam can setup some question banks and practice through as a solo owner player.
And you are right, this definitely needs to be polished a lot. This is all conceptualized and implemented in 48 hours during NKO with some challenges around our inexperience with GIT :).
Bare minimum, we are looking to extend and implement following pretty soon. 1. Timeout on server to force move to next question 2. Find someone who can help us design the UI and do some better UI. 3. Fix some stability issues. Sometimes START button is required to be pressed twice for ex. 4. Allow pulling some reports/dashboard. Currently we track very fine level of details in Mongo DB. We are thinking it would be great to build some UI reports around it that can help a teacher in a classroom as well as students gain some insights. 5. ... And we are brainstorming more.
Thanks again for your comments.
Is an honor have some feedback from you, we admire you a lot. Here you can have a taste of the front-end experience of playing faceball. http://cortezcristian.com/facemaze/ Today I've mounted the server on the office and had the chance to see a lot of my coworkers moving their head and fighting for the ball.
Unfortunately GitHub don't give us enough control over the permissions we ask for to not ask for write access.
The main feature of Hub is that it shows GitHub activity in line with the chat messages. In order to do this we need to be able to register for webhooks, so it's possible that write permissions are required for that. (One of my teammates would have to confirm.)
A lot of people have told us that they would rather Hub did not ask for private repo access. We didn't realise this would be a problem, but we would definitely consider making it optional in the future.