Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pattern Idea: Truth and Reconcilliation pattern

Open
#370 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

No file, test, or entry point is identified. Read the issue body and the linked Truth and Reconciliation Commission reference first; the issue describes a policy-oriented pattern, but does not define the required document structure or a concrete completion criterion.

Written by the indexing model from the issue text.

Description

:book: Type - Content Work 1-initial

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.

Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InnerSourceCommons/InnerSourcePatterns

All issues in InnerSourceCommons/InnerSourcePatterns

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.