Transparency

Be open about as many things as possible. By making information public, we can reduce the threshold to contribution and make collaboration easier. Use public issue trackers, projects, and repositories when possible.

Back to the universal principles

Calibration

Under, just right, over.

Situation	Under	Just Right	Over
A decision in a private chat	Leaves the decision in the private thread and wonders why others redo it.	Moves the decision to a place the people who need it can read, and links the reason.	Pastes a private conversation, including asides that were never meant to be shared.
A project only the team can see	Defaults to a private project because that is easier.	Makes it public unless there is a concrete reason not to, and writes that reason down.	Makes public a project that contains customer data or a personnel matter.
Lowering the cost of helping	Asks for contributions and keeps the context in your head.	Publishes the goal, the status, and how to propose a change.	Publishes so much unfinished noise that contributing is harder than asking you.
A real reason to stay private	Uses privacy as the habit, not as a reason.	Keeps private what would hurt a customer, a person, or an unannounced commitment, and makes the rest public.	Announces that everything is public and then hides the actual decision anyway.
An issue others could fix	Files it where only your team will see it.	Files it in the public tracker with enough detail that someone outside the team could help.	Files a vague public issue and then ignores the people who show up.
Public and wrong	Leaves a public doc you know is stale because correcting it is awkward.	Corrects it in public and says what changed.	Deletes the history so the mistake is harder to see than the fix.

Further reading

Sources and essays on this principle.

GitLab Values
The published CREDIT values this principle belongs to.
gitlab.com
Transparency, GitLab Values
The Transparency value, last in CREDIT.
gitlab.com