sytse

95 ms·

1. 931.▲
   by sytse 9y ago

   Yay! Thanks for using GitLab. Every month we're trying hard to make the installation, the performance, the security, and the interface better. Still a lot of work to do but we've come a long way from our beginnings being based on
2. 932.▲
   by sytse 9y ago

   Yeah, I felt it was pretty good at the time. BTW my comment here has 110 upvotes, many more people on HN then in 2012.
3. 933.▲
   by sytse 9y ago

   We did that. Thanks for using GitLab!
4. 934.▲
   by sytse 9y ago

   It gave me a job, a company, and a sense of purpose. In 2012 I did a Show HN for GitLab.com https://news.ycombinator.com/item?id=4428278 Today we are 1800 contributors and a company of 220 on a mission to ensure that everyo
5. 935.▲
   by sytse 9y ago

   Debian is running a GitLab server in beta at https://salsa.debian.org/public
6. 936.▲
   by sytse 9y ago

   Love your consideration in order to get us to reflection.
7. 937.▲
   by sytse 9y ago

   We're fully remote and regularly hire people with remote work experience. However, it is important that our team members are self managing and we do ask questions about that during the interview.
8. 938.▲
   by sytse 9y ago

   Do you have a suggestion to make our UX work better for you?
9. 939.▲
   by sytse 9y ago

   Agree, you need a whole set of tools to go from continuous delivery to continuous deployment. The most important are reducing the blast radius, early detection, and reducing the mean time to repair. In GitLab we offer incremental rollouts,
10. 940.▲
    by sytse 9y ago

    We have extensive support for Jira, see https://about.gitlab.com/features/jira/ for an overview and please let m Us know if you miss anything.
11. 941.▲
    by sytse 9y ago

    I agree that most startups should work at a Heroku level of abstraction. You mention 18 microsevices, I think that small teams are better off with a monolith. I would see Kubernetes as a new machine level. We're moving from bare metal,
12. 942.▲
    by sytse 9y ago

    We're trying to do complete DevOps with GitLab https://about.gitlab.com/2017/10/11/from-dev-to-devops/ What part of the Atlassian stack are you missing in GitLab?
13. 943.▲
    by sytse 9y ago

    Conversation moved to https://news.ycombinator.com/item?id=16269631
14. 944.▲
    by sytse 9y ago

    Thanks Mr Mondo!
15. 945.▲
    by sytse 9y ago

    Also on TechCrunch https://techcrunch.com/2018/01/30/gitlab-acquires-gemnasium-...
16. 946.▲
    by sytse 9y ago

    Everything is a microphone?
17. 947.▲
    by sytse 9y ago

    Apart from having it in a document we found it useful to also have it in slide decks https://about.gitlab.com/2017/10/11/from-dev-to-devops/ slideware with prototype screenshots https://docs.
18. 948.▲
    by sytse 9y ago

    Exactly, if people start multitasking at meetings giving the meeting their full attention is probably not a good way to spend their time. Trust people to assign their attention as they please and measure results, not hours.
19. 949.▲
    by sytse 9y ago

    I'm at GitLab but not on the Gitaly team. I think we are using libgit2 but that it doesn't contain all the calls we need.
20. 950.▲
    by sytse 9y ago

    According to Google Trends https://www.dropbox.com/s/ldyvpxa0vbvelie/Screenshot%202018-... Gitosis reached 4% of GitLab's popularity in 2011 and is now at 0%. If course Google Trends is not equal to installed
21. 951.▲
    by sytse 9y ago

    No data is perfect, we consider the data reliable. As promised I changed the wording of our CI/CD claims https://gitlab.com/gitlab-com/www-gitlab-com/commit/64ce89fd...
22. 952.▲
    by sytse 9y ago

    The conversation is happening in https://news.ycombinator.com/item?id=16212234
23. 953.▲
    by sytse 9y ago

    buddybuild and bitrise data probably has a bias in it. But we didn't find much else to go on. If you of anyone else knows of something we should use instead please let me know. I think that since the blue ocean update to Jenkins they h
24. 954.▲
    by sytse 9y ago

    GitLab Ultimate does not restrict the number of targets you can test. What are the funky problems you encountered?
25. 955.▲
    by sytse 9y ago

    Interesting. If you want to integrate it there are instructions in the docs https://docs.gitlab.com/ee/user/project/merge_requests/dast.... (use gl-dast-report.json to send results back). If your product
26. 956.▲
    by sytse 9y ago

    Thanks. We do think it got a lot better last year https://about.gitlab.com/2017/07/17/redesigning-gitlabs-navi...
27. 957.▲
    by sytse 9y ago

    One big thing that we would love to do is moving to a multithreaded application server https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 That would save a ton of memory but last time we tried we got burned
28. 958.▲
    by sytse 9y ago

    I'll try to very politely disagree :) We tried charging for services: donations, paid feature development, and paying for support. None of them scaled and we moved to open core which allowed us to spend much more time on performance, s
29. 959.▲
    by sytse 9y ago

    Thanks! There is a place for web editors (quick edits, new projects) and local editors (working on the same codebase for a longer time). As warned against we don't want to fall in a rabbit hole of spending all our time on this instead
30. 960.▲
    by sytse 9y ago

    I stand by the claim we have 2/3 market share in the self-hosted git market. The claim is now linked to a page that contains the details https://about.gitlab.com/is-it-any-good/