Live data from Hacker News

GitLab 8.5 released

about.gitlab.com

181–190 of 246 posts

Re: GitLab 8.5 released

#181
post #174

Earlier quoted context omitted.

Want any help? I don't have any interesting answers for your hiring filters. The culture you've built is very rare. I realized that if I felt that way, then I should try to help it become the norm.

We always want help, you can contribute directly or apply to work via http://doc.gitlab.com/ee/project_services/jira.html We take all applications seriously but if you feel you got rejected for a bad reason feel free to contact me directly.

I think your link may be an errant copy paste :)

I guess you meant to paste: https://about.gitlab.com/jobs/

Re: GitLab 8.5 released

#182

Earlier quoted context omitted.

Hey, Kelvin from Atlassian here. We are pretty flat out ourselves improving both Bitbucket Cloud and Server. I can see how SSO isn't terribly important if Bitbucket is the only one of our products you use, but it's critical for our customers who co-own Bitbucket and JIRA (or Confluence, or HipChat, etc.). It was a fairly massive undertaking: retrofitting auth across our portfolio of products took some serious enginee…

Hi Kelvin, Any chance BitBucket has a public roadmap? I'm a user because of your free private repos, I hope to grow into a paid user this year. Thanks for all that you do!

Great to hear! Not quite, but we try to keep relevant feature requests on jira.atlassian.com (for Server) and https://bitbucket.org/site/master/issues (for Cloud) as up to date with progress as we can.

Re: GitLab 8.5 released

#183
post #82

Earlier quoted context omitted.

No, unfortunately not. We recommend 2GB of memory to run GitLab https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst... If 512MB is a requirement for you please consider using Gogs. Glad you like the Todos feature!

I just wanted to say how awesome it is that you mention Gogs, a competing platform. It shows that you're focused on your domain, not closed-mindly discounting every competitor, and are open about any shortcomings in Gitlab.

It also makes sense from a business point of view. The three strong points that I've taken from business school are:

1) You can overtake an incumbent if you can offer twice the value at half the price. If you can produce a drill that works two times better than existing drills at half the price, you'll overtake the drill market.

2) You can't compete with "as good as". Winning here is more marketing than anything and this is where companies like Apple and Coco-Cola shine. You can't beat Coke with point one, since it is impossible to produce something that is better than Coke. You can measure the performance differences between drills, but you can't measure the psychological value of Coke and Apple

3) You can't compete by price, unless you are dealing with a commodity product, which brings me to my point for posting.

Turning "Git hosting" into a commodity product is not a bad situation for GitLab and I honestly think this is where it's heading. In a year or two, we'll probably see less tangible/understood things become the main selling point. Such as intelligent code reviews, better code management metrics, defect predictions and so forth.

Edit:

Forgot to mention that point 3 is also where Atlassian deserves a lot of credit. They are leveraging point 3 and trying to parlay it into point 1.

Re: GitLab 8.5 released

#184
post #123

We're super excited with GitLab 8.5. It's much faster, no matter the size of your instance (but especially for larger instances). The Todos, ability to revert commits and CNAME support for Pages, are things that have been much requested and we're happy to have now. As always, we're here if anyone has any questions about anything.

Pages are an EE feature, but one which is useful for open source projects. Would you accept a pull request for a community implementation of Pages? or would a fork be needed in this case? How do you see this sort of issue playing out?

This is a very good question and something I'm always concerned about when it comes to open core products.

Re: GitLab 8.5 released

#185
post #181
post #174

Earlier quoted context omitted.

We always want help, you can contribute directly or apply to work via http://doc.gitlab.com/ee/project_services/jira.html We take all applications seriously but if you feel you got rejected for a bad reason feel free to contact me directly.

I think your link may be an errant copy paste :) I guess you meant to paste: https://about.gitlab.com/jobs/

Yeah, that was the page that convinced me I should try to join. But,

"A note on the technical interview: As part of our interviewing process, you may be asked to pick an issue from the GitLab CE issue tracker, and code ‘live’ with the interviewer there to talk with and collaborate with. We do this because we believe that it is the best way for you to see what the work is really like, and for our interviewer to see how you think, code, and collaborate." Actually, it's the opposite of how to find out how I think and code.

Do you have a profile on GitLab.com, GitHub or Bitbucket?

No.

What (open source) project that you built or contributed to are you particularly proud of / passionate about?

None.

Were you referred by a current GitLab team member?

No.

I once discovered that one of the most effective developers in the world would've had similar answers.

Re: GitLab 8.5 released

#186

Earlier quoted context omitted.

Atlassian is going after the enterprise market. They don't care about free software developers.

That's a poor strategy. All developers start out as free software developers, then gain employment. I persuaded my work to purchase Gitlab EE licenses, due to ease of use and it's excellent features & support. I can't imagine I'd say the same of Atlassian products. Capture awareness / interest early.

I agree there is something to be said for bottom-up marketing, but asserting that "all developers start out as free software developers" is completely untrue. In fact, I'd guess that people who actually develop free/OSS software are far outnumbered by those who don't.

Re: GitLab 8.5 released

#187

Earlier quoted context omitted.

That's a poor strategy. All developers start out as free software developers, then gain employment. I persuaded my work to purchase Gitlab EE licenses, due to ease of use and it's excellent features & support. I can't imagine I'd say the same of Atlassian products. Capture awareness / interest early.

> All developers start out as free software developers, then gain employment. I don't think that's true. Some people never get involved in free software even as a hobby. Some people get apprenticeships and learn to program from scratch on the job.

Or, strange as it may seem, they learn how to write software from a four-year college degree. And colleges are notoriously bad at teaching so much as source control, let alone what source control options are there, how to use a bug tracker, etc. (Which makes sense, because you don't strictly need source control if you aren't collaborating heavily, and you don't need a bug tracker if you have a single development week-by-week.)

Re: GitLab 8.5 released

#188
post #181

Earlier quoted context omitted.

I think your link may be an errant copy paste :) I guess you meant to paste: https://about.gitlab.com/jobs/

Yeah, that was the page that convinced me I should try to join. But, "A note on the technical interview: As part of our interviewing process, you may be asked to pick an issue from the GitLab CE issue tracker, and code ‘live’ with the interviewer there to talk with and collaborate with. We do this because we believe that it is the best way for you to see what the work is really like, and for our interviewer to see ho…

Is there an extension to hide downvotes, ungray all comments, and hide karma count? If not, I'm going to write one.

I know it's just an errant downvote, and people can feel however they want. But the information is no longer useful.

Re: GitLab 8.5 released

#189
post #181
post #174

Earlier quoted context omitted.

We always want help, you can contribute directly or apply to work via http://doc.gitlab.com/ee/project_services/jira.html We take all applications seriously but if you feel you got rejected for a bad reason feel free to contact me directly.

I think your link may be an errant copy paste :) I guess you meant to paste: https://about.gitlab.com/jobs/

Yes, thanks for correcting me!

Re: GitLab 8.5 released

#190

Earlier quoted context omitted.

Having used both there's more than enough in either that's bad to justify a switch to the other if you really want to. I personally prefer github's warts to gitlab's. In particular, I find that general site navigation on gitlab is quite tedious and it rarely centres useful information first. But that is very much a qualitative and not a quantitative complaint. The main thing I find extra useful on gitlab is the abili…

That would be nice. In GitLab today, we end up deleting and re-creating merge requests, or waiting until comments "@ ready for merge".

Why do you need to do that? Have you looked at the merge request approvals feature https://about.gitlab.com/2015/07/29/feature-highlight-merge-... (EE/.com only)?
Post reply on HN