dsumenkovic

Hello, Community Advocate from GitLab here.

Thank you for sharing your feedback and comments with everyone, we really appreciate that. It's great to hear how you are handling your self-hosted GitLab instance, that's awesome!

Thanks for the suggestions. It would be great to have more details about it. Could you please open a feature proposal about that over at https://gitlab.com/gitlab-org/gitlab-ce/issues? We'd love to follow up on it.

At GitLab we really care about transparency and it's one of our core values. Here you can find out more about Cookies policy https://docs.gitlab.com/cookies-policy/

Thanks for mentioning GitLab, Community Advocate here.

WIP is really used, and we even have documentation about it https://docs.gitlab.com/ee/user/project/merge_requests/work_...

That's right. Here's more info about it https://docs.gitlab.com/ee/user/project/integrations/jira.ht...

Hello, Community Advocate from GitLab here.

We are glad to hear that you like using GitLab!

Regarding the documentation, have you checked out the following doc? https://docs.gitlab.com/ee/user/project/clusters/index.html#...

Hello, thank you for mentioning GitLab.

Speaking of >making programmer's job easier<, we could say that GitLab Auto DevOps eliminates the complexities of getting going with automated software delivery by automatically setting up the pipeline and necessary integrations, freeing up yourself to focus on the culture part. That means everyone can skip the manual work of configuration, and focus on the creative and human aspects of software creation.

Here's more about it https://docs.gitlab.com/ee/topics/autodevops/

Hello, Community Advocate from GitLab here. Thanks for mentioning our CI and other features.

Since we always care about transparency, everyone can read more about it here https://about.gitlab.com/features/gitlab-ci-cd/. Also to mention the documentation where you can read about the first steps towards your GitLab CI/CD journey https://docs.gitlab.com/ee/ci/

Hello, Community Advocate at GitLab here. Have you checked out this position? https://about.gitlab.com/jobs/apply/?gh_jid=4101613002. Feel free to read more on https://about.gitlab.com/jobs/

Hello, Community Advocate from GitLab here. Thanks for mentioning our Auto DevOps.

One of it's main functionalities is to eliminate the complexities of getting going with automated software delivery by automatically setting up the pipeline and necessary integrations, freeing up yourself to focus on the culture part. That means everyone can skip the manual work of configuration, and focus on the creative and human aspects of software creation.

Here's the doc with more info about it https://docs.gitlab.com/ee/topics/autodevops/

Thank you for writing about GitLab. You can read more about creating the new wiki page here https://docs.gitlab.com/ee/user/project/wiki/

Thank you for your feedback, we really appreciate your words. Here's the brief doc explaining how to easily import your project to GitLab if you missed it https://docs.gitlab.com/ee/user/project/import/github.html.

PRs are related to MRs (Merge Requests), howver MRs have some additional features. Here you can read more about it https://about.gitlab.com/comparison/gitlab-merge-request-vs-...

Thanks for your comment, we really appreciate the feedback. Our team is working hard on improving the availability and stability of the platform. Our goal is currently to achieve 99.95% availability on GitLab.com.

According to Pingdom, over the last year our availability has been 99.81%, although this includes the large (multi-hour) maintenance window on 11 August 2018 when we migrated GitLab.com from Microsoft Azure cloud to Google Cloud Platform (GCP).

Since the migration, our availability has improved greatly (caveat: we obviously have much less data than from Azure).

Using the data publicly available from Pingdom, here are some interesting stats:

Mean-time between outages in Azure (September 2017 through August 11 2018): 1.3 days

Mean-time between outages in GCP (September 2017 through August 12 2018): 7.3 days (if you ignore some problems we experienced on the first day after the migration, this rises to 12 days!)

Since, migrating to GCP, our overall availability, according to Pingdom, has risen to 99.92%. Again, if you exclude the few hiccups that we experienced on the Monday immediately following the migration, this rises to 99.97%.

There are multiple reasons for this improvement. We chose Google Cloud Platform because we believe that they offer the most reliable cloud platform for our workload, particularly as we move towards running GitLab.com in Kubernetes. It is worth pointing out that we also used the migration as an opportunity to improve our infrastructure, simplify some components and otherwise make things more stable and more observable. Finally, we've also been focusing on building the infrastructure team up, having hired many new team members over the past few months. This means that the team has been better able to balance the job of running GitLab.com with making it more stable.

There are plenty of reasons why people are picking GitLab. You can read more about it here https://about.gitlab.com/2017/07/19/git-wars-switching-to-gi....

However, that's an old blog-post, today GitLab is the only single product for the complete DevOps lifecycle. Here you can find out more references about GitLab DevOps https://about.gitlab.com/devops/.

You are right about the open-core. However, in that blog-post, Sid mentioned that we are an open-source company and remarked that open-core is the more accurate term.

Thanks for your feedback. You explained that really well using the word "popular". Here are more details why people are picking GitLab https://about.gitlab.com/2017/07/19/git-wars-switching-to-gi...

Here are more details about Series C round of investment https://about.gitlab.com/2017/10/09/gitlab-raises-20-million....

That's correct, here are more details about that. https://about.gitlab.com/2017/10/09/gitlab-raises-20-million...

Hey, thank you for the feedback. We are heavily focusing on performance improvements - both in the product (so that features run better)[1] and in our GitLab.com infrastructure team (so that GitLab.com runs more reliably)[2]. We stayed transparent about the database incident and people really appreciated that.

[1] - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label....

[2] - https://gitlab.com/gitlab-com/infrastructure/issues

Awesome, thank you for your kind support. We really appreciate that.

At GitLab we are always trying to iterate and we learned a lot from our incident with the database.

The one thing we are proud of is our transparency. The community really appreciates our openness and we are happy about it.

Here's the one example https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...

Thanks for the feedback, it's great to hear that our product is that easy to use.

Glad to hear that. We'd love to hear your feedback about GitLab CI/CD.

If you are interested in GitLab pages, this would be the best place to start: https://about.gitlab.com/features/pages/.

You can use GitLab WebIDE as well. Here you can read more about it https://docs.gitlab.com/ee/user/project/web_ide/.

Glad to hear that, if you need any help, feel free to reach out to community@gitlab.com.

Our team is actively working on improving the performance of GitLab.com. If you are referring to the merge requests, we're close to converting the merge request view to Vue, this should speed it up considerably.

To add to sytse's answer

Environments currently can't be deleted from the UI. We have an issue open about it at - https://gitlab.com/gitlab-org/gitlab-ce/issues/25388

The issue gained a lot of traction. It's scheduled for 11.1.