Pattern Idea: Truth and Reconcilliation pattern

Often when teams are working in an insular manner, code quality is not up to par, leading to a hesitancy in opening up their code. Other times, there are issues regarding configuration and abstraction, with no clear separation between code and secrets such as deployment keys. There are also sometimes issues regarding compliance which may have been lax in the past.

At times bad code quality, policy, technical decision, and a myriad of other factors could lead to harm. There's a strong incentive in this climate to keep code hidden. This could hinder InnerSource adoption while creating a climate of fear and mistrust in the InnerSource program.

The Truth and Reconciliation pattern aims to help companies draft policies to create a space where past transgressions are declared and dealt with without blame, in order to be able to move towards a more open future.

Truth and Reconcilliation is named after the program organized by the first post-apartheid South African government (information at https://www.sahistory.org.za/article/truth-and-reconciliation-commission-trc-0) in order to address pass grievances.

Aucun fichier, test ou point d’entrée n’est identifié. Lisez d’abord le corps de l’issue et la référence liée de la Truth and Reconciliation Commission ; l’issue décrit un modèle orienté vers les politiques, mais ne définit ni la structure de document requise ni un critère concret d’achèvement.