dsumenkovic

Thanks for sharing the feedback with the community. We are glad to hear how GitLab helps you.

That's right. You can read more about it at https://about.gitlab.com/company/culture/all-remote/. There you'll find how remote work is changing the workforce, how it changes the organization, advantages for employees and organizations and what did we learn about remote working.

Thanks for writing about GitLab.

If you are wondering what's the Auto DevOps - GitLab Auto DevOps eliminates the complexities of getting going with automated software delivery by automatically setting up the pipeline and necessary integrations. You can find out more info at the landing page [1] and the documentation [2].

[1] https://about.gitlab.com/product/auto-devops/

[2] https://docs.gitlab.com/ee/topics/autodevops/

Hi, Community Advocate from GitLab here. Could you please reference what issues you are experiencing? We'd love to follow up on it.

Also, if you want to write the details, it would be great to open an issue https://gitlab.com/gitlab-org/gitlab-ce/issues. Thanks in advance.

Thanks for the feedback.

Hey, Community Advocate from GitLab here. Sorry for the confusion with the words. We actually meant "back up" which has a bit different context. Fixing that in https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

Good catch Michael, that's right. We meant the "back up" and we are fixing this typo https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/....

Thank you for pointing this out and sorry for the confusion.

Thanks for sharing this great blog post!

Thanks for your comment, we really appreciate your feedback about GitLab. 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).

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.

At GitLab we really care about our culture and core values [1]. As freddie said below: "Start doing it, celebrate it, reward it". If you are not sure how to make the first move, I would like to say that transparency is what really pushes everyone forward.

Start iterating on transparency, it may be hard but you will see the great results and it will make everyone around collaborate much more.

You probably heard of the event [2] which occurred almost 2 years ago - people are still talking about it and we are really happy and impressed to see everyone, including us, learning from that experience.

I hope this non-technical suggestion will help you to think about a solution to your question. If your team is not used to this kind of openness, eventually they will like the positive feedback from the community (we see that as a small iteration :-)). A comment section at [2] may be the extra source of motivation.

Have a nice day,

Djordje - Community Advocate at GitLab

[1] https://about.gitlab.com/handbook/values/#transparency

[2] https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...

Hey James, thank you for being such an incredible part of the GitLab community! Specifically, for taking the time to write about our product. We really appreciate sharing this with the rest of the community. Could you please reach out to us via community@gitlab.com?

That's a really interesting question. However, I think that's not something regular, so there's no fixed multiplication. It may double or multiply even more, there's no rule :-).

Hey Simone, thank you for the feedback. I really appreciate your thoughts and your advice make sense.

It's amazing to see people from various communities helping each other with simple tips, we call that a small iteration :-).

I never expected this thread will grow this much. At the moment of posting my comment, the thread was almost empty and my intention was to share as much of valuable information to captaindiego. However, it turned into a reaally big thread and the context of my comment probably turned into something else for later viewers.

Anyway, as we always try to stay transparent I left it as it is. Thank you for your great opinion, I'll consider your words when posting a comment next time.

You are welcome!

Hello, Community Advocate from GitLab here. Thanks wjohnsto for sharing a link to our Handbook.

I'd love to share our "All Remote" page as well. https://about.gitlab.com/company/culture/all-remote/.

There you can read how remote work is changing the workforce, how it changes the organization, advantages for employees and organizations and what did we learn about remote working.

Additionally, our blog page is the great place to learn about our culture and remote working at GitLab https://about.gitlab.com/blog/.

Here's the list of our blog posts I would recommend. This may be a really interesting read for you:

[1] https://about.gitlab.com/2018/10/18/the-case-for-all-remote-...

[2] https://about.gitlab.com/2018/05/17/eliminating-distractions...

[3] https://about.gitlab.com/2018/04/27/remote-future-how-remote...

[4] https://about.gitlab.com/2018/04/17/remote-work-facilitates-...

[5] https://about.gitlab.com/2018/03/16/remote-work-done-right/

Some users may had issues connecting to GitLab due to an issue with our upstream provider's IP addresses being routed to other service providers. More info can be found at https://status.cloud.google.com/incident/cloud-networking/18....

Hi, Community Advocate from GitLab here. Thank you for writing about GitLab Wiki, we appreciate your comment.

Could you please let us know what could make your experience more convenient? Are there any suggestions you'd like to share? We'd like to hear what made your hard time using our Wiki.

Feel free to raise an issue or submit a feature proposal over at https://gitlab.com/gitlab-org/gitlab-ce/issues? We'd love to follow up on it. Thanks!

Hello, Community Advocate from GitLab here.

I would love to share this little piece of information about GitLab installation with everyone.

Since there was a little confusion mentioning GitLab installation, I would love to clarify that our installation page [1] offers many different approaches. Before the installation process, please make sure that you read our Installation doc [2].

The Omnibus package may be the best choice installation since it is quicker to install, easier to upgrade, and it contains features to enhance reliability not found in other methods [2].

[1] https://about.gitlab.com/install/

[2] https://docs.gitlab.com/ee/install/

[3] Other official installation methods are via Docker, Kubernetes, Google Cloud Platform etc.

Hello, Community Advocate from GitLab here. Thank you for sharing this info with the community!

We'd love to follow up on your blog post once it's finished. Could you please reach out to us via community@gitlab.com when it's done? Thanks!

We wanted to hear what features you like using the most and how do those features help you with setting up your project. However, you wrote https://news.ycombinator.com/item?id=18384804 which answers a lot of the questions. Thanks!

Hello, Community Advocate from GitLab here. I was reading through your comments and it's great to hear how you use GitLab for your setup. Thanks for sharing your story with the community and we'd love to hear more from you on how GitLab helps you.

Thanks for sharing that. We are glad that you appreciate our transparency which is one of the core values at GitLab.

Hello, Community Advocate from GitLab here. Thanks for sharing your solution with other users, we are happy to hear how you use GitLab to make your work more convenient.

We are glad to hear that using GitLab helps you with your scripts and settings for vim. That's a really great approach.

Hey Caleb, if you are interested in using GitLab webhooks, this documentation may help you https://docs.gitlab.com/ee/user/project/integrations/webhook....

We are glad to hear that you like using GitLab CI. What are your favorite features?

Hey Gregoire, that's a good question. Epics let you manage your portfolio of projects more efficiently and with less effort by tracking groups of issues that share a theme, across projects and milestones. On the other hand milestones are a way to track issues and merge requests created to achieve a broader goal in a certain period of time.

Anyway, please check this documentation for Epics https://docs.gitlab.com/ee/user/group/epics/ and Milestones https://docs.gitlab.com/ee/user/project/milestones/

Thanks for mentioning GitLab. You can find more information about Auto Devops and creating Kubernetes clusters from withing GitLab at this doc https://docs.gitlab.com/ee/topics/autodevops/quick_start_gui...

Thanks for writing about your experience with GitLab.

Can you tell us which are the basic features that are missing? And what could make your experience more convenient? Actually, 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.

Hello, Community Advocate from GitLab here.

Thank you for your comment, we really appreciate your words. It's great to hear your feedback and you can check out the latest data on stability and performance here https://about.gitlab.com/2018/10/11/gitlab-com-stability-pos...