GitLab says it makes information public by default because transparency is one of its values, while some unsafe or limited-access information can remain nonpublic.

Google

GitLab says it demonstrates transparency by being open with as many things as possible, reducing the threshold to contribution, and making collaboration easier.

Transparency in GitLab's CREDIT Competencies

GitLab public handbook values page describing CREDIT values, public values, reinforcement mechanisms, remote-work culture, transparency, collaboration, iteration, diversity, inclusion, belonging, and results for customers. https://handbook.gitlab.com/handbook/values/

GitLab Handbook: Values

GitLab identifies intentional transparency as part of its culture and notes that it can be unintuitive to outsiders and new team members. It encourages people to invest in open dialogue, share problems, ask for help, be forthcoming with information, and speak up.

Transparency in GitLab's Stated Values

GitLab cites the public repository of its handbook website, GitLab CE and EE issue trackers, marketing, and infrastructure as examples of transparency.

Public Handbook and Trackers as GitLab Transparency Examples

GitLab says transparency creates awareness, helps recruit people who care about its values, produces more and faster external feedback, and makes external collaboration easier.

External Feedback and Collaboration Benefits of GitLab Transparency

Public by Default at GitLab

GitLab says transparent changes should clearly lay out the reasons for the change alongside the change itself so people understand the decision and institutional memory is preserved.

Learn Before

Related