btasovac

Hey efiecho, Community Advocate from GitLab here! I'm sorry to hear that you are not a fan of our actions and/or decisions.

Can you please dive into specifics a little bit and explain what parts of GitLab could be improved and what are some high-level things that you don't particularly like?

Thank you for the explanation! I just opened an issue proposing this [1]. Please add a comment with any additional feedback that you might have or feel free to ping me if I didn't fully understand what you are proposing.

[1] - https://gitlab.com/gitlab-org/gitlab/-/issues/216573

Community Advocate from GitLab here! If I understand you correctly, you are looking for a way to aggregate analytics across GitLab, so that users can view information across multiple projects and groups in one place.

We have the Analytics feature designed for that [1]. Please be aware of the distinction between Group-level and Project-level analytics described there.

If you have any feedback on how we can improve this feature, or if you have other ideas, please open an issue [2] and share as many details and examples as possible. We'd love to look into it!

[1] - https://docs.gitlab.com/ee/user/analytics/index.html.

[2] - https://gitlab.com/groups/gitlab-org/-/issues

Just wanted to chime in and add following links from our documentation:

Get the diff of a commit - https://docs.gitlab.com/ee/api/commits.html#get-the-diff-of-...

List repository tree - https://docs.gitlab.com/ee/api/repositories.html#list-reposi...

Repository files API - https://docs.gitlab.com/ee/api/repository_files.html

Hello all, GitLabber here!

We opened an issue for gathering feedback at https://gitlab.com/gitlab-org/growth/product/issues/164 and you can find the most up to date information regarding this topic there. Please join the discussion and let us know what you think.

Hello, GitLabber here! We’re currently writing an issue explaining the situation, once it’s public I will link it here.

Please see how did we start paying team members according to the location in the first place and why we did it here: https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

The Debian migration is actually finished.

We are offering our top tiers (Ultimate or Gold) for free to open source projects [1]. You can see the complete list in our repo [2]. Some of the most recent projects that received our free license are Arch Linux, the Tor Project, edX (currently migrating). Just to add a few more: Drupal, Haskell, VLC, Kali Linux, Lineage OS, and more on this comment [3].

[1] - https://about.gitlab.com/solutions/open-source/program/

[2] - https://gitlab.com/gitlab-com/marketing/community-relations/...

[3] - https://news.ycombinator.com/item?id=18724015

This was often a hot topic on HackerNews, so we decided to write a blog post explaining why we pay local rates. Please find more information here [1].

[1] - https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

> Anyhow, I'm looking forward to see a similar feature implemented by Gitlab, even without the matching donations.

You can check out this issue [1]. Please upvote it if you want to see this implemented, or join the discussion if you have any additional ideas.

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/43468

Thank you for pointing this out - we'll try to fix this as soon as possible.

You can read why GitLab pays local rates on our blog post [1]

[1] - https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

Hello, Community Advocate from GitLab here.

GitLab.com was originally announced with free private repos. When you’re starting to program and aren't ready to share your code with the world yet, you don't have to have a paid account to keep it private.

Now, we're focusing on making a single application for the entire DevOps lifecycle that can replace a lot of other tools[1]. So instead of a version control system that lets people try out different integrations, GitLab provides an opinionated (yet flexible with key integrations and the option to opt out of anything you don't want) way to run the entire software development and deployment lifecycle.

Or, as Stavros Korokithakis phrased it: "My move to GitLab was basically 'Come for the free repos, stay for the rest of the amazing features.' I will not be moving off it, and my new repos will keep being on GitLab."

[1] - https://about.gitlab.com/stages-devops-lifecycle/

Hello, Community Advocate from GitLab here.

We are an open core company. We ship two editions - Community Edition and Enterprise Edition. CE is completely open source and licensed under MIT license. EE is proprietary, closed source code but we try to work in a way similar to GitLab CE: the issue tracker is publicly viewable and the EE license allows modifications.

In conclusion (TLDR), GitLab has an open core business model and ships both open and closed source software.

Overview of the three main improvements in this release:

1. Detect secrets and credentials in the repository

A recurring problem when developing applications is that developers may unintentionally commit secrets and credentials to their remote repositories. If other people have access to the source, or if the project is public, the sensitive information is then exposed and can be leveraged by malicious users to gain access to resources like deployment environments. GitLab 11.9 includes a new check called Secret Detection. It scans the content of the repository to find API keys and other information that should not be there. GitLab displays results in the SAST report in the merge request widget, pipelines reports, and the security dashboards.

2. Merge request approval rules

Code review is an essential practice of every successful project, but who should review the changes is not always clear. It is often desirable to have a variety of reviewers from different teams like Engineering, UX, and Product. Approval Rules allow you to better communicate who should participate in code reviews by specifying the eligible approvers and the minimum number of approvals for each. Approval rules are shown in the merge request widget so the next reviewer can quickly be assigned.

3. Move ChatOps to Core

Initially introduced in GitLab Ultimate 10.6, ChatOps has now moved to GitLab Core. GitLab ChatOps provides the ability to trigger GitLab CI jobs from Slack by using the slash commands feature. We are open sourcing this feature in alignment with our buyer-driven tier designation to encourage its use and contribution by the community.

Thank you for the detailed feedback! We love to hear that we're doing something well, but also like to discuss if there is something that can be improved.

> It would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed

That sounds reasonable, and it doesn't seem to be an issue only with your institution. We already have an issue for automating the application process for the educational license. [1] The proposed solution would resolve all concerns described here.

> I originally though the Education licensing would cover usage for our IT Department staff as well

The primary goal of this program is to help students catch up with the latest technology in software development as early as possible, and we think that we managed to do this with the current setup. However, we would love to discuss other options regarding this program's limitations. Please open an issue [2] - we would love to hear your suggestions.

> Is there any work towards building/including some sort of Confluence alternative

Can you please tell us more about what part of Confluence do you think is missing in GitLab? You can use this page as a reference - there are all stages of development that are covered by GitLab. [3]

Thank you again on your feedback, it is greatly appreciated.

[1] - https://gitlab.com/gitlab-com/marketing/community-relations/...

[2] - https://gitlab.com/gitlab-com/marketing/community-relations/...

[3] - https://about.gitlab.com/product/

Regarding acquisition, our goal is to go public on Wednesday November 18, 2020. You can read more about our goals and in which order we want to achieve them on our Strategy page [1].

[1] - https://about.gitlab.com/company/strategy/#sequence

Thanks for sharing this! Yes, instead of a version control system that lets people try out different integrations, GitLab provides an opinionated (yet flexible with key integrations and the option to opt out of anything you don't want) way to run the entire software development and deployment lifecycle.

You can learn more about the different stages of the DevOps lifecycle on our Product page [1].

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

GitLab is an open core company [1], meaning that we ship GitLab CE which is open source and GitLab EE that is closed source. We try to be a good steward of the open source project. GitLab EE is proprietary, closed source code but we try to work in a way similar to GitLab CE: the issue tracker is publicly viewable and the EE license allows modifications.

In conclusion (TLDR), GitLab has an open core business model and ships both open and closed source software.

[1] - https://about.gitlab.com/2016/07/20/gitlab-is-open-core-gith...

Thank you for sharing this! We think that Hacker News community is really important and try to engage as much as possible.

Since one of our core values is transparency, we love to share our open issues, blog posts and links to different parts of our handbook[1].

This helps members of our community get more context on certain topics and allows them to continue the discussion in the right place. Furthermore, when our community knows where to express their feedback, we can use it to improve GitLab.

[1] - https://about.gitlab.com/handbook/

You can see a comment from our CEO related to this here: https://news.ycombinator.com/item?id=18443014

We're happy to hear that GitLab helped you improve your code-review experience! We documented some of the advice and best practices that might be useful when performing code review or having your code reviewed [0].

[0] https://docs.gitlab.com/ee/development/code_review.html#best...

Hello, Community Advocate from GitLab here! I'm happy to hear that your former employer is happy with our product!

If you have more feedback on the things that could be better, we would love to hear more!

Thanks for sharing this! I'd love to hear if you have more feedback on how is GitLab's UX different. Particularly, what do you think GitLab could do better here?

Hello Mike! Can you please reference the Sourcegraph example in the issue? Maybe this will initiate further discussion and convince someone to reconsider your proposal. Thank you!

We're really excited to hear your experiences with GitLab in terms of development strategies for velocity. Please let us know when your blog post is live; we'd love to hear more from you!

Thanks for sharing this idea! We have a similar issue regarding this [1], so please feel free to engage in the discussion there and bring some attention to it. We'd love to hear more from you on this matter!

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/18037

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]. Thank you for sharing your thoughts candidly.

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

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

Hello everyone, GitLabber here! We had a similar issue about this [1], and we raised another one when deciding to further clarify our documentation regarding this question [2]. You can find out more about our motives behind this decision there.

[1] - here https://gitlab.com/gitlab-org/gitlab-ce/issues/36754 [2] - https://gitlab.com/gitlab-org/gitlab-ce/issues/43436