News for hackers. Stuff that matters.
Re:GitLab acquires Gitter, will open-source the code by connorshea on Wednesday March 15, 2017 @01:09PM (#13877756)
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.
Re:GitLab acquires Gitter, will open-source the code by ocdtrekkie on Wednesday March 15, 2017 @02:05PM (#13878317)
This just makes me hope you guys buy more things.
Re:GitLab acquires Gitter, will open-source the code by connorshea on Wednesday March 15, 2017 @02:11PM (#13878373)
Ha! Any suggestions? ;)
Re:GitLab acquires Gitter, will open-source the code by kstenerud on Wednesday March 15, 2017 @02:40PM (#13878613)
A cross platform GUI git client that doesn't suck!
Re:GitLab acquires Gitter, will open-source the code by ocdtrekkie on Wednesday March 15, 2017 @03:29PM (#13879018)
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.

Re:GitLab acquires Gitter, will open-source the code by ylk on Wednesday March 15, 2017 @03:55PM (#13879226)
> (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?)

Re:GitLab acquires Gitter, will open-source the code by j_koreth on Wednesday March 15, 2017 @11:52PM (#13882351)
Have you tried smartgit?
Re:GitLab acquires Gitter, will open-source the code by mullsork on Wednesday March 15, 2017 @05:13PM (#13879835)
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)
Re:GitLab acquires Gitter, will open-source the code by tajen on Wednesday March 15, 2017 @05:34PM (#13880014)
> 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.

Re:GitLab acquires Gitter, will open-source the code by connorshea on Wednesday March 15, 2017 @06:20PM (#13880405)
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.
Re:GitLab acquires Gitter, will open-source the code by jhasse on Wednesday March 15, 2017 @02:51PM (#13878689)
https://typora.io/ (a WYSIWYG Markdown editor)
Re:GitLab acquires Gitter, will open-source the code by jensvdh on Wednesday March 15, 2017 @02:39PM (#13878605)
waffle.io
Re:GitLab acquires Gitter, will open-source the code by ferentchak on Wednesday March 15, 2017 @03:09PM (#13878853)
I doubt CA will let it go. Now poaching Homeyer might be possible. ;)
Re:GitLab acquires Gitter, will open-source the code by rabbitfang48 on Wednesday March 15, 2017 @04:42PM (#13879580)
> All our source code is publicly viewable

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

Re:GitLab acquires Gitter, will open-source the code by connorshea on Wednesday March 15, 2017 @05:00PM (#13879730)
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.

Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @05:02PM (#13879743)
I reopened the issue.