cmatija

7 ms·

31.
by cmatija 10y ago
Yup, Thanks for taking the interest to check it out. It's an unlisted YT video, so that's why it might be hard to find. Here it is: https://www.youtube.com/watch?v=nc0hPGerSd4
32.
by cmatija 10y ago
Hi Kris, We usually tend to add every single bit of information that we attain to our handbook[0]. Other than that, we try to over-communicate over issues, slack and email. [0] https://about.gitlab.com/handbook/
33.
by cmatija 10y ago
We have separate teams working on frontend and backend. Here's a list of performance issues which we intend to work on: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf... Most of them are sch
34.
by cmatija 10y ago
My bad there. I though you were referring to GitLab.com We're planning a bunch of performance improvements for 9.0, which is intended to make GitLab faster for everyone. https://gitlab.com/gitlab-org/gitlab-ce&#x2F
35.
by cmatija 10y ago
No need to be sorry. We always appreciate honest feedback. We're working really hard on identifying the causes of our performance issues, as well as fixing them. There's a META issue about this here: https://gitlab.com&
36.
by cmatija 10y ago
Definitely. We have lots of ongoing efforts. (Not necessarily moving to a different Ruby implementation, though) You can take a look at an overview of our efforts here: https://gitlab.com/gitlab-com/infrastructure/
37.
by cmatija 10y ago
Hey, thanks for joining in on the conversation. We agree. It's not just the front-end. We had problems with bot the front-end and back-end. But we're working hard on making things better / more performant on all fronts. We ha