GitHub + Chat = :D
Instead of reinventing the wheel, Hub adds on to every developer's favorite tool, GitHub. When you login with Hub, you are presented with a list of the organizations you have access to and each of their repos (which act as rooms). This allows devs to seamlessly communicate with other members of their team in an organized fashion. Hub also allows open-source projects to easily provide chatrooms for their maintainers. This greatly simplifies the process and lowers the barrier to entry for new users significantly. Project maintainers no longer have to worry about explaining IRC rooms to new members.
It also takes it's integration with GitHub to the extreme and automatically adds commit messages, issues, pull requests, and more into each repo's chat. You no longer have to worry about telling the team that there's a new pull request, it's automatically displayed for all.
Hub allows you to get back to what really matters, coding, and communicating with your team, by working with the tools you already know and love.
Our MVP is a very simple web app that uses websockets for rooms, but in the future, we plan to create a full API and native OSX, Windows, iOS, and Android clients. Because of Hub's modular nature, we're able to allow developers to tap into rooms to create IRC-like integrations with other platforms.
Sign up with GitHub and click one of the rooms that you're a member of on the left. In order for this to work, you need to be a member of at least one GitHub organization. The magic happens if you can get someone else from that organization to hop on so you can chat.
Voting is now closed.
Arizona School for the Arts (student)
Unfortunately, GitHub doesn't give us enough control over the permissions we ask for for us to be more specific. :(
I believe the Github rate limit has reset, so you should be able to try again :)
Thanks Kevin - I'm flattered!
The GitHub rate limits might have reset now. Hope you get a chance to try again!
I went back to the site, but this is all I see:
Are you in any GitHub organizations?
Hmmm, ok. Chances are this is due to the fact that we have exceeded another rate limit :(
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.
Let's break this down, shall we?
It's pretty clear that this has nothing to do with the actual app, and is instead an attempt to sabotage our ratings in order to boost yours.
That's a shitty thing to do.
Frankly, I could care less about the prizes/title, but I do care that you're needlessly assaulting our app for your personal gain. Remember that hackathons are about having fun, not cutthroat competitions.
Sorry guys, I didn't want to make you upset. Votes are editable and I just did not found any other way to send you a message. My plan was that if I get a reasoned answer for my question then I try it and give a reasonable vote for you. Actually, I didn't get an answer for my question, Of course I understand why you need the API permissions, but still.....I think giving WRITE permission for PRIVATE repos is unacceptable. But let's pretend that as if it were my first comments, right? I've created a new github account to sign up your app. First strange thing is http://hub.2013.nodeknockout.com url redirets me to http://team-name-goes-here.2013.nodeknockout.com. I clicked to Sign Up button, I got Internal Server Error. I tried it again, granted access to your app which followed by endless loading.... Am I doing something wrong? I've edited my last vote based on the video and the frontpage. I'm gonna edit it again if I managed to use the app. And please, forgive me about my previous vote, not meant to be final.
Yeah, we sometimes get an Internal Server Error because of GitHub rate limits.
Unfortunately, GitHub doesn't give us enough control over the permissions we ask for. We think they're a bit excessive too.
If no rooms are showing up for you, it's possible that your new account isn't in any organisations - currently, only rooms for organisation repos are displayed.
Hope this helps! :)
The URL redirect is simply because we did not have time to specify our team name before the subdomains were set up, so Node Knockout set up a DNS mapping for us.
GitHub rate limits :(
Automattic (formerly Cloudup)
We keep running into rate limiting issues with GitHub... trying to work with them to get whitelisted
The Node Firm
Private repo access seems to have put off a lot of people. We didn't realise people would have an issue with this, but we would definitely consider making it optional in future.