We're hoping to stump you…and we stumped ourselves on some of these questions for sure. There are just 10 questions, so dive in, and you'll see your score at the end.
from GitLab https://ift.tt/s3tFMme #GitLab #DevSecOps
This blog post is Unfiltered I’ve been at GitLab five months now - with every merge request committed and milestone met, GitLab team members collaborate on innovative and efficient methods of delivering some of the world's best software. Besides this, I’ve also noticed that GitLab team members do a superb job of creating an environment that allows each of our peers to contribute, be heard, and bring their whole selves to work. Once you’ve gotten a taste of being part of that kind of community you get to see how much it matters in writing good code - talented and inclusive teams are more creative, efficient, and happier in the workplace. The Gitlab Handbook offers amazing explanations about our values and resources for living them to your best ability. One of our values ‘Diversity, Inclusion, and Belonging’ has the following note on this value that I really appreciate: “… Diversity is having a seat at the table, Inclusion is having a voice and feeling empow...
When you think about security you probably imagine locks, gates, and closed systems. This is the more traditional approach to security but modern security is much more open and collaborative. If you want to build the most secure systems, there is nothing better than building those systems in the open. Open security practices allow you to get fast feedback from a broad audience with diverse perspectives, helping you build better more holistic solutions. That's our approach to building GitLab Secure at GitLab. We're leveraging amazing open source security projects, the collective contribution of the wider community, and providing an open integration system for anyone to build on top of GitLab security scanners. Shifting left Traditional security approaches are opaque and late in the development life cycle. Security scans are performed by isolated security experts long after developers write code, often after it's deployed to production. GitLab aims to make security an inte...
This blog post is Unfiltered At GitLab, everyone can contribute . This has been our mission from day one, since GitLab started as –and is still– an open-source project. We believe that, when consumers become contributors, it benefits everyone: GitLab the product, GitLab the company, GitLab the community as well as all GitLab users all around the world. We already merged more than 7,700 “community contribution” merge requests from our wider community (at the gitlab-org group level). Merge requests from community members not employed by GitLab (aka from the GitLab wider community) Contributing tracks Now, it's your turn to contribute and improve GitLab! Since not everyone share the same interests nor competencies, we have multiple tracks to ensure everyone can contribute: Development (new features, bug fixes, performance improvements) Documentation addition, improvements, and fixes Translations UX design Project templates When you're ready, simp...
Comments
Post a Comment