In this month’s release of GitLab 10.3 we’ve added new ways to ensure that your code changes are both secure and fast, enhanced your planning and collaboration workflow, and improved your ability to build and ship.
GitLab is a remote-only organization and just like our team, our users are spread across the globe. Conducting remote UX research allows us to quickly connect with GitLab users anywhere in the world. It provides us with the opportunity to gather insight into users’ behaviors, motivations and goals when using GitLab. This helps us to determine what features should be built and how they should behave. But how do we do all this remotely?
GitLab recently switched from PhantomJS to headless Chrome for both our frontend tests and our RSpec feature tests. In this post we will detail the reasons we made this transition, the challenges we faced, and the solutions we developed. We hope this will benefit others making the switch.
We recently switched from a Contributor License Agreement (CLA) to a Developer's Certificate of Origin (DCO) to make it easier for everyone to contribute to GitLab. Now, we're taking our commitment to our core tenet, "everyone can contribute," a step further. We're amending our Proprietary Information and Assignment Agreement (PIAA) and putting clarifying processes in place to help our contributors maintain their ability to work on projects that are unrelated to GitLab's business, including other open source projects.
With an idea and a name, I was ready to start working more seriously on UnscrewMe, a simple wine tasting scheduler app. Well, almost ready – to avoid ending up with a mess of files and folders and stuff scattered across different devices, and certainly never where I need them, my next objective was to set up a central location where I could store and organize everything flexibly.
Scaling design within an application is a struggle. Design systems help alleviate problems that arise with scaling by making it easier to find inconsistent interactions or conflicting messaging. However, it can be extremely difficult to introduce a new system to teams that are already functioning without one. Here's how we got started.
Build better software, faster, with test and release automation. Check out our recent webcast to discover why it's critical to your software development process.
Today we are releasing versions 10.2.4, 10.1.5, and 10.0.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain several security fixes, including a fix for a difficult to exploit Cross-Site Scripting (XSS) vulnerability, a fix for an API bug that could leak the names of private projects, a fix for a private email disclosure vulnerability, and a fix for a bug that could allow users without access to a project to create issues in that project.
We recommend that all GitLab installations be upgraded to one of these versions.
Please read on for more details.
In our 10.0 release, we introduced a new navigation complete with a redesigned color palette and icon set. We replaced Font Awesome with our own, SVG based, icon system, and we’ve also been hard at work on a series of illustrations to provide consistent visual language and improve our onboarding experience. Read on to find out more about how the UX team goes about creating new icons and illustrations.