For us it was natural to open the source code, we prefer to work that way. All our source code is publicly viewable and most of it is open source.

This just makes me hope you guys buy more things.

Ha! Any suggestions? ;)

A cross platform GUI git client that doesn't suck!

This is a pretty great idea. For what I often deal with, the GitHub desktop client is okay (though obviously tied to GitHub), but then I was sad to also realize they don't offer it on Linux. (Maybe they assume Linux nerds don't need GUIs?)

I tried Tower when it was in beta for Windows, but the cost is too steep to justify it for me. But it seemed to be a lot more full featured than the GitHub client which isn't good for more than basic commits. And again, no Linux there either.

I'd definitely go for a solid, open source git client, and it's obviously very relevant to GitLab's business.

> (though obviously tied to GitHub)

You can actually use GitHub Desktop with any repo: https://help.github.com/desktop/faq/articles/do-you-support-... (Although it looks like you have to clone it first?)

Have you tried smartgit?

Spend that money porting GitUp.co to multiple platforms instead. The only git GUI I've used that doesn't suck. Might be lacking in features though 8)

> Any suggestions?

Seriously, SublimeText, which is $70 closed-source.

Less seriously, macOS and iLife. I'd be ok to pay €200/year/user for an OS of that quality, as long as it's open-source.

I'd personally (not speaking on behalf of the company) love to acquire Sublime, but it's probably too expensive at this point. I'm pretty sad to see Atom eclipse Sublime so much recently, Sublime is so much faster and change is hard :( If only it were open source.

https://typora.io/ (a WYSIWYG Markdown editor)

waffle.io

I doubt CA will let it go. Now poaching Homeyer might be possible. ;)

> All our source code is publicly viewable

Not all of it. version.gitlab.com is one of GitLab's closed source IPs.

Yeah, unfortunately that's because we made a mistake, here's the relevant issue if you want more info (PDF because it's a private repo so I can't link directly to it unfortunately):

https://drive.google.com/file/d/0ByoIqX0IDB5scWpJT0JKTHQtTG8...

We do want to open source it when we can.

I reopened the issue.

Do we know what protocol Gitter runs on top of?

Gitter uses a proprietary websocket protocol built on top of the Bayeux protocol: https://docs.cometd.org/current/reference/

More details can be found on the developer site: https://developer.gitter.im/docs/faye-endpoint

We also have an open-source IRC bridge: https://github.com/gitterHQ/irc-bridge

I prefer matterbridge :) Supports more than IRC, and supports multiple gateways at once: https://github.com/42wim/matterbridge/

Depending on the availability of a Bayeux client for Golang, it looks like something that could be integrated quite easily.

I don't know how Gitter support in matterbridge is implemented but it is great! Do try it out. I've been running a three-way discord+gitter+irc gateway for a long time.

And there is a matrix.org/gitter bridge already in use by riot.im

Protocol? I kind of assumed things like Slack, Gitter, etc. were just using websockets that communicate with their backend.

Slack is built on top of IRC. Presumably Gitter is as well

Slack is definitely not built on top of IRC. There is, however, an IRC interface to Slack.

Not on top of IRC. Just similar in that they are both chat like

> Slack is built on top of IRC

Source? First time I hear that, and it seems unlikely, since they have quite a few features that don't fit nicely in stock IRC.

I’m not sure there are any Slack features that don’t fit into stock IRC v3. Basically everything they do is already supported or a draft. (Now just everyone has to implement it)

Now, possibly. But unless I'm totally wrong on the timeline, IRCv3 (not even talking about implementations) wasn't even close to that level when Slack started and thus is unlikely to be the base of their product. And even now, I wouldn't include v3 yet when talking about "stock IRC" in this context.

Any source on that. I don't think it follows any protocols at all. Just implements it's own thing.

I think open sourcing here just shows that the code is irrelevant and is not the money maker. I guarantee you nobody is moving off slack because gitter is "open source". People might move to gitter because is it integrated into gitlab self-hosted though (this is what will happen and mattermost will be phased out despite what they say).