(Edit: I initially thought this was _from_ GitHub. Apparently it's not, so please disregard the nagging below. It is a cool idea, but if GitHub did this, I'd have different expectations.)
I'd be all over this if it was an IRC server. Most big projects already have an IRC channel on FreeNode, so this'd be a natural fit: Provide an IRC server with a channel for each project, provide a free web client for this server with the GitHub-goodies.
But alas, apparently it's just another proprietary chat network.
Actually, FreeNode integration is something we've discussed quite a bit and could well end up in the product if there is enough interest in us putting it in. FreeNode is an incredible source of information and it would be a pity not to use it.
This would be the killer feature to add. Users should be able to communicate to freenode, and vice versa, while being able to do all of the management functions.
failed to fetch user profile (status: 403 data: {"message":"Maximum number of login attempts exceeded","documentation_url":"http://developer.github.com/v3"})
at Strategy.userProfile (/opt/gitter/landing-app/node_modules/passport-github/lib/passport-github/strategy.js:90:28)
at passBackControl (/opt/gitter/landing-app/node_modules/passport-github/node_modules/passport-oauth/node_modules/oauth/lib/oauth2.js:105:9)
at IncomingMessage.exports.OAuth2._executeRequest.request.on.callbackCalled (/opt/gitter/landing-app/node_modules/passport-github/node_modules/passport-oauth/node_modules/oauth/lib/oauth2.js:124:7)
at IncomingMessage.EventEmitter.emit (events.js:126:20)
at IncomingMessage._emitEnd (http.js:366:10)
at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
at CleartextStream.socketOnData [as ondata] (http.js:1472:20)
at CleartextStream.CryptoStream._push (tls.js:544:27)
at SecurePair.cycle (tls.js:898:20)
at EncryptedStream.CryptoStream.write (tls.js:285:13)
at Socket.ondata (stream.js:38:26)
Guess it's built with node ;)
After pressing the button again, it gave me the confirmation message.
Yup, they should log / e-mail themselves the error messages when in production rather than displaying them, sensitive info might leak plus stacktrace aren't very friendly.
You guys should offer this for github enterprise. Any form of integration would also be nice (an IRC or XMPP bridge) because I don't want yet another chat client on my desktop, and alerts from web clients don't cut it...
...slightly offtopic, on the alerts: chrome's rich notifications pop under apple's desktop notifications, and neither let me capture the notification and have the system voice read it to me rather than flash up in a corner that I'm not looking at. But campfire's in-browser notifications are the worst of all, some random tab beeping when I have 100 open.
Yeah, github enterprise definitely makes sense, and it is something that we will look into.
Chrome's notifications since v28 kinda suck. Browser notifications have always been difficult, and in fact our www.trou.pe native app was originally just a toolbar app to solve this problem.
Looks pretty neat. I went to signup, but then noticed that they require commit access to my public repos. Why do you need this permission to integrate links to the code and similar features? I don't like giving out commit access unless absolutely necessary.
Not the parent, but I'm reluctant to give a website access to an account I care about just for a trial. If I know that I want to use your service, sure, but not if I just want to casually evaluate it.
Email and password. It's not really better to be fair
I can give a new service a disposable email address, I don't have a disposable Github/Facebook/Twitter/etc account. Not even a shred of a chance of me testing something if you're requesting anything other than the most basic of read-only permissions too
The landing page looks really slick. I was wondering, how did you create the design for it?
I'm a programmer and my web design skills are limited to installing bootstrap, and I'm always fascinated, how would you come up with right color/font/layout matching
I do everything "in the browser" these days. No Photoshop, just straight HTML/CSS/JS in Sublime Text. That way the site starts to feel alive pretty quickly and then I just tweak stuff around until I'm happy with it.
Colours...
Sometimes I use http://flatuicolors.com/ as a starting point and then tweak it from there.
Hello, Would you mind sharing about front end libraries (js, css) you've used. The interface is beautiful and efficient. I'd love to hear a bit more about it.
Thanks for much for the compliment, you made my day.
There's not much to say really. It's just pretty vanilla jQuery and then I code the CSS/HTML by hand. I use a few Bootstrap components, but where possibly I try to craft everything myself. I think that helps to keep it simple, if you start throwing a lot of components together you end up with a mess rather than having to put the effort in yourself and, as your time is a precious resource, you think more about what's important and what's not.
I was looking at the source and found your rick astley. It looked really weird in chrome's dev tools :P. Your CSS/HTML is way better than mine, time to polish my skills..
This looks like it was influenced by the Hub, a Node Knockout project with a landing page created by high school students that's been picking up steam on Twitter since last weekend.
Sorry to hear that :( I'm also one of the devs. If you are still having issues with authenticating you can check out a video and description about our service at http://nodeknockout.com/teams/team-name-goes-here
Hi! I'm one of the developers of Hub. We've been having some issues with GitHub rate limiting, but that should have reset now, so if you still want to try it out, it should work for you now. :)
Very interesting, I'm looking forward to checking out the product! We use GitHub exclusively for everything; even our non-technical team-members leverage GitHub for sales, HR, marketing, blog post writing.. You name it. We did have to build a product to make this easier on ourselves [1], into which we've been resisting integrating chat. Chat is the only non-GitHub piece of our workflow, Gitter looks promising!
Signed up immediately. Very promising, especially if the history stays up there for anyone who joins the "repo" discussion later on.
This could be really important for bigger projects where new/significant features should be discussed openly. This way the information stays attached to the repo and others can refer to it later on.
Dev here! Yeah, we've been making www.trou.pe for while and have just added some github hooks after some user requests. We are just curious to see how far people want github integration to go...
After signing up for Gitter I checked out Trou.pe. But even without signing up for Trou.pe it already knew my gravatar & was able to suggest me usernames (including my full name) when going to http://trou.pe.
When you perform the OAuth signup via GitHub, GitHub provides us with your name username, etc. Then, if you click the link to signup with Troupe, we create a Troupe account for you, pre-populated with your details, so that you don't need to enter them again.
Please make it so we can delete our accounts. I signed in for gitter because I like what I read and wanted to be on the waiting list, but when I got the message saying about Trou.pe I was curious to see what it was, not sign up. That's not cool, and now I'm signed up for some site I don't even know what does... I looked around after being force signed up and STILL don't know what it is. Now I can't delete it without going to Github and de-authorizing the actual account I did want. ಠ_ಠ
We used that to build GitTogether (https://gittogether.com), which is a similar concept to this: text chat and video chat with people you follow plus members of your teams and organizations.
Hm, "signing up" by providing read-only OAuth access to my GitHub account is... fascinating. :-)
Very clever way to make signups easy, relevant to the interest you're trying to gauge, and gather far more information about me than just my e-mail address (eg. my activity level on GitHub, the type of projects I'm involved in).
A lot of comments here are saying things like "I wouldn't be able to persuade my team/non-technical colleagues to use this instead of HipChat". Surely one the most exciting uses for Gitter is discussion on open-source repos, where you aren't already communicating with repo collaborators?
true, but it would be fantastic to merge those two cultures together. Having non technical people involved in open source projects is a good thing, and it is something that we are trying to encourage.
Just tried signing up with github and got the message -
"Gitter isn't ready yet. If we get enough support, we will launch this in a few months. Help spread the word by Tweeting about us and follow @GitChat for updates."
From the other comments here, it looks like people are able to try out a demo or something. What am I missing?
Not directly related to your product, but I always wonder why, with soft launches like this where you gauge interest, why not make the "interest" count public? How many people have you captured?
That being said, I've wanted this idea for a while, so I signed up straight away.
I want to pay money for this. A chat service with built-in GitHub integration including issue and file referencing sounds like a fantastic tool for teams building using GitHub.
Any chance you can use an actual Kickstarter instead so I can throw money at you? :)
As long as it's not Pound coins. Those things are heavy!
Thanks for the feedback. Our Clickstarter (tm?) is doing quite nicely. I don't think we'll need to Kickstarter it, we've actually built a lot of the tech anyway and could put this together pretty quickly and start charging too.
Funny enough, I had just sent an email to GitHub support yesterday with similar comment. Using chatrooms internally as much as they do, I can't believe GH doesn't have builtin chat with deep integration and decent API. Heck, even make trivial to add your Hubot's.
Another immediate signup. Would like to echo @davman's comment about showing the interest count. It would be interesting to watch the needle, so to speak. A +1 for Hubot integration as well.
Hey there. We'll absolutely consider how non-technical folks can engage with this. Our current product, Troupe (http://trou.pe) is more along these lines, with GitHub webhooks integration.
We may look to fuse the concepts so that it works brilliantly for both the developers and the rest of the company too.
Yeah, that barrier is a tough one to overcome. We've found that having an easy entry point (nothing to install, one click signup etc.) lowers the barrier a bit.
Also having some kind of free tier could always be an advantage over hipchat...
Good point. The problem with a tier limited by the number of people is that you take away one of the best parts of a free chat service. Being able to freely invite _anyone_ into a conversation really opens up what you can do.
At the moment we have node + express + faye for rest api/streaming. The web front end is currently built with backbone, less and a sprinkling of bootstrap.
Take a look at our current product, it's not directly tied to GitHub, but has webhook integration (with BitBucket, Travis, Jenkins too).
www.trou.pe
We'll need to sweat some details on Gitter, so hard to say on the timing. We may fuse the two concepts together, so it will be more about product-related decisions than development time as we have a lot of the code already.
Feel free to give us feedback on Troupe so we can loop that into the future direction of this product.
Looks really interesting, you guys should take a look at www.surfly.com. With Surfly in the mix you would not just be able to chat about things but also show people around.
We're using a huge amount of open source components ourselves and are actively contributing back to those projects. James Coglan's Faye is a great example of this where we've been working with James to get it to V1.
The approach we'll take for our own work is certainly to open source some of the components rather than the entire system. We're big believers in giving back, but at the same time we ned to protect our own business.
Chat apps come and go... and there I am on IRC. I hang out with lots of people on github there.
Why would I use this over IRC with the client of my choice? Build an IRC client that integrates with GitHub, or extensions for Adium to handle github URL's. Or maybe GitHub could offer authorization through XMPP.
Why should I have to use a separate client when I already have Facebook, IRC, XMPP, etc. all managed from the same place?
I'd be all over this if it was an IRC server. Most big projects already have an IRC channel on FreeNode, so this'd be a natural fit: Provide an IRC server with a channel for each project, provide a free web client for this server with the GitHub-goodies.
But alas, apparently it's just another proprietary chat network.