12,257 karma · joined December 15, 2009
There is also an iPad / MacBook hybrid listed on later pages. Apple didn't go this route but the new iPad keyboard https://www.apple.com/shop/product/MXQU2LL/A/magic-keyboard-... is heavier and more complex than ever before.
The last GitLab release was 12.10 which was release on April 22 https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-re... with Requirements Management and Autoscaling CI on AWS Fargate
1. GitHub Insights with GitLab Insights, Contribution Analytics, Issues Analytics, Productivity Analytics, Value Stream Analytics, DevOps Score, Code Review Analytics, and CI/CD Analytics.
2. GitHub security features with GitLab Container Scanning, Dependency List, Dependency Scanning, Dynamic Application Security Testing (DAST), Security Dashboard, Static Application Security Testing (SAST), and Secrets Detection.
3. GitHub Codespaces with the GitLab Web IDE, CI/CD Environments, Review apps, and Live Preview.
1. GitHub Insights => GitLab Insights https://docs.gitlab.com/ee/user/project/insights/ Code Review Analytics https://docs.gitlab.com/ee/user/analytics/code_review_analyt... DevOps Score https://docs.gitlab.com/ee/user/instance_statistics/dev_ops_... and Value Stream analytics https://docs.gitlab.com/ee/user/analytics/value_stream_analy...
2. GitHub CodeScanning => GitLab SAST https://docs.gitlab.com/ee/user/application_security/sast/ and Secret Detection https://docs.gitlab.com/ee/user/application_security/sast/#s...
3. GitHub Codespaces => GitLab Live Preview with client side evaluation https://docs.gitlab.com/ee/user/project/web_ide/index.html#c... and upcoming server side evaluation https://gitlab.com/groups/gitlab-org/-/epics/167 which would work both with on-premises Kubernetes clusters and in any cloud.
GitHub Codescanning functionality is best compared to what GitLab has in GitLab SAST https://docs.gitlab.com/ee/user/application_security/sast/ and Secret Detection https://docs.gitlab.com/ee/user/application_security/sast/#s...
Thanks for planning to contribute to GitLab. When your submission passed review consider messaging the reviewer and mention you're interested in working here. We do still accept references from team members.
There is no need for a LinkedIn profile.
If you're currently in your first job a reference can be a peer you trust there, a former teacher, or a manager from a side-job or hobby. OSS maintainers work work as well.
The digital nomads that move to a new room weekly tend to have a hard time focussing on work. People that move every couple of months or that have a camper tend to do better.
We've found amazing people inbound and most of our current team applied for the job themselves. But there is a lot of noise and we had to decline more than 99% of applicants. We've recently switched to sourcing (outbound recruiting) focussed model https://www.businessinsider.com/gitlab-hire-critical-roles-r...
The security curation examples I mentioned are intended to use automated signals so there wouldn’t be an expense for labor. In fact we intend to run them separately on every self managed GitLab installation.
Being the canonical registry for a language (Rubygems) or technology (DockerHub) tends to be a huge expense.
The main expenses are cloud costs (bandwidth and storage) and security (defense and curation).
I've not seen examples of organizations turning this into a great business by itself. For example Rubygems is sponsored by RubyCentral http://rubycentral.org/ who organize the annual RubyConf and RailsConf software conferences.
Please note that running a non-canonical registry is a good business. JFrog does well with Artifactory https://jfrog.com/artifactory/ and we have the GitLab Package Registry https://docs.gitlab.com/ee/user/packages/ that includes a dependency proxy and we're working on a dependency firewall.
The comment you linked says: "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]."
The current state is that Puma is now powering all of GitLab.com and we're working on getting it to be the default in Omnibus https://gitlab.com/gitlab-org/omnibus-gitlab/issues/4698