I'd like to share more data on the UX front. There are two efforts underway to establish the experience baselines [1] as well as a common design system [2]
Hopefully these efforts allow us to look at our UX holistically, and to focus on making high-quality components that are used throughout the product.
One thing that bugs me really hard about gitlab.com (and gitlab ce) is the broken flow when I come about an interesting repo and want to star it. I'm logged out, click on "Star", log in and I'm at my profile. I have to navigate back to the repository in question and click "Star" again.
Other than that it's really great software. I wouldn't want to miss running Gitlab CI.
Hi! GitLab employee here. While someone else from the community provides the feedback, I'd like to highlight what our support team can provide.
> GitLab offers a variety of support options for all customers and users on both paid and free tiers. You should be able to find help using the resources linked below, regardless of how you use GitLab.
I am sorry if it sounds like that, as my intention was just to provide some more data while waiting for the real case feedback. Hopefully, some users will provide their personal experiences.
Hi! I'm on Djorde's team, just in case anyone stumbles across this and thinks you're literally talking to a bot (not saying you are OP, just preventative), he is a non-native English speaker but definitely a real person. You're talking to this guy :) https://about.gitlab.com/company/team/#sumenkovic
I think the point they were making (in a mean way) is that it sounded like robotic PR speak, the thing any PR person would say. The support page doesn't say much about the quality of support, so the message was received poorly.
Sometimes the very friendly PR tone is considered out of place and obviously forced. Especially on a developer forum.
[PR for devs must be so much "fun" - you have my sympathies]
Hi, yeah I figured that was the point they were making, I kinda wanted to provide the info (in a round-about way lol) that he specifically is a non-native English speaker, so that's why it comes off as a bit forced-friendly and PR-ish. I do appreciate this feedback from both of you, I will mentor them a bit better about this!
I was hoping for a bot actually. I’m a decent user of GitLab (and GH) and really find the insight from employees commenting on HN helpful in understanding the product roadmap and philosophy of the company.
I was pleasantly amused at the possibility of GL having a chatbot loose on HN but figured you were just a person trying to be helpful.
Comically, your response still could be generated, but I trust you enough that you don’t have to post additional proof you are human. Spend that resource on accurately counting the pets in the office.
Thanks for the feedback. We are working hard to improve performance and memory consumption of GitLab. We have two major projects underway, switching to Puma [1] as well as reducing the overall memory consumption of GitLab [2].
You can follow along on some of the progress we are making in each release post in the "Performance Improvements" section. For 12.2 you can see we had 58 MR's related to performance.
Hello! We haven't been at the capacity employee-wise to have teams dedicated to improve much in these areas, but we tripled our employee count this year and have since spun up a memory team [1] and are able to dedicate more people to performance [2]. So hopefully we won't be saying this for much longer!
I wanted to share the following issues [1] & [2] with you and everyone else since the features you've mentioned are already being discussed. Feel free to leave your thoughts in there:
GitLab Community Advocate here. Thanks for the feedback, I am happy to hear that you like our product. Since you are still evaulating GitLab, please let me know if you need any assistance or help regarding other features.
GitLab review applications are a fantastic tool to enable stakeholders from Operations to QA to business owners to evaluate and approve application changes before production.
In GitLab 12.0, it's easy to provide visual feedback directly from the review app. It’s simple and streamlined, no toggling between different tabs and typing your feedback, helping to shorten review cycles and accelerate delivery. Documentation [1]
2. Project Dependency List
Projects typically include dozens of individual components, which can introduce vulnerabilities. Often, security and compliance teams need to be aware of the specific components included in a project. Documentation [2]
3. Limit access based on IP address
In GitLab 12.0, you can specifically prohibit traffic from outside IP addresses from accessing your GitLab data. Documentation [3]
Hopefully these efforts allow us to look at our UX holistically, and to focus on making high-quality components that are used throughout the product.
[1] - https://about.gitlab.com/handbook/engineering/ux/experience-...
[2] - https://about.gitlab.com/handbook/engineering/ux/pajamas-des...