Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab acquires Gitter, will open-source the code

venturebeat.com

Post reply on HN
Print view View original

91–100 of 333 posts

Re: GitLab acquires Gitter, will open-source the code

#91

Post by suprememoocow »

scrollaway wrote: post #74
suprememoocow wrote: post #43

Earlier quoted context omitted.

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.

Re: GitLab acquires Gitter, will open-source the code

#92

Post by connorshea »

ocdtrekkie wrote: post #89
connorshea wrote: post #41

Earlier quoted context omitted.

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? ;)

Re: GitLab acquires Gitter, will open-source the code

#93

Post by scrollaway »

suprememoocow wrote: post #91
scrollaway wrote: post #74

Earlier quoted context omitted.

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.

Re: GitLab acquires Gitter, will open-source the code

#94

Post by pietroalbini »

dewiz wrote: post #25

next, I hope to see some "content" offer attached to gitlab's ecosystem, for instance a strong collaboration with stackoverflow/OSQA

I guess you can remove OSQA from that list. It's now abandoned, with no new commits and the developers strongly encouraging to use their commercial offering...

I'm currently in the processor of migrating an OSQA site to AskBot, which seems currently maintained.

Re: GitLab acquires Gitter, will open-source the code

#95

Post by scrollaway »

suprememoocow wrote: post #84
dewiz wrote: post #25

next, I hope to see some "content" offer attached to gitlab's ecosystem, for instance a strong collaboration with stackoverflow/OSQA

Gitter has been working on a content system called Topics. https://gitter.im/gitterHQ/topics . It's still in Beta, but Q&A and structured content is definitely something that - in addition to chat - we think is important. (edit: typo)

That's really awesome! Does it run like a mailing list system? One of the #1 pain points in running FOSS projects is creating and managing a mailing list, with archive browsing that doesn't look atrocious.

Re: GitLab acquires Gitter, will open-source the code

#96

Post by jobvandervoort »

ohstopitu wrote: post #90
jobvandervoort wrote: post #82

Earlier quoted context omitted.

Let us know what projects you miss seeing integrated with GitLab and we'll try our best to convince them, help them in any way to make sure it happens! As other point out, you should be able to use GitLab CI instead of Travis, they configure very similarly. That said, I'd welcome them integrating fully with us as well.

I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it). As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)

> I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it).

Ah interesting! You can't do this now with GitLab, but we're working on supporting merge requests as special cases [0].

> As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)

Clubhouse sure looks nice! GitLab Issues is getting better every release and in 9.0 (March 22nd), we have some big changes for Issue Boards.

I've asked our PM on Issues (Victor) to check out Clubhouse and hopefully we can convince them to integrate with us in some way.

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23902

Re: GitLab acquires Gitter, will open-source the code

#97

Post by therealmarv »

ohstopitu wrote: post #67

I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind), generally don't integrate with Gitlab It's one of the few reasons why I am still using Github :( .

Generally I have the opinion that the CI of gitlab is much more powerful because of real Docker usage (and also works on private repos for free). Speaking about the gitlab CI... why is there no status or statistics page about it on status.gitlab.com and why is a new build pending over 30 minutes currently (now) ?

Re: GitLab acquires Gitter, will open-source the code

#98

Post by yuhong »

sytse wrote: post #47
orb_yt wrote: post #42

Earlier quoted context omitted.

Looks like they will open source the whole thing. I'd be very interested in learning how much Gitlab paid for this acquisition.

I'm sorry but we don't comment on acquisitions prices. Being transparent about it is not common in the industry and us doing this by default might make future acquisitions harder since the company being acquired might not like it. Also see https://about.gitlab.com/handbook/general-guidelines/ "Most things are public unless there is a reason not to. Not public by default are: financial and legal information"

I think even public companies often disclose the prices though, especially for major ones. This being said, I have been thinking about the GitLab IPO, including things like fixing Reg FD for a while now.

Re: GitLab acquires Gitter, will open-source the code

#100

Post by FooBarWidget »

LyndsySimon wrote: post #72
ohstopitu wrote: post #67

I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind), generally don't integrate with Gitlab It's one of the few reasons why I am still using Github :( .

I've yet to find something I needed that wasn't supported - or that there wasn't a better option available that did support it. TravisCI for instance, is easily replaced in all of my projects with Gitlab's integrated CI.

I feel this way too. Not specifically about travis but about providing github integration as the only option Git is supposed to be distributed! How hard is it to ask people to provide a git url and tell them to push events to a webhook?
Post reply on HN