From 38559f97e85fc2378e6dace0137ce567092a31eb Mon Sep 17 00:00:00 2001 From: Tom Sadler Date: Fri, 3 Jan 2025 22:50:27 +0000 Subject: [PATCH] [Pattern Draft] Managing capacity for reviewing contributions (#692) New pattern: Managing capacity for reviewing contributions --------- Co-authored-by: Tom Sadler Co-authored-by: Sebastian Spier --- README.md | 1 + .../1-initial/capacity-for-contributions.md | 76 +++++++++++++++++++ 2 files changed, 77 insertions(+) create mode 100644 patterns/1-initial/capacity-for-contributions.md diff --git a/README.md b/README.md index 6e1900727..5c81085ea 100644 --- a/README.md +++ b/README.md @@ -87,6 +87,7 @@ Our mission * [Code of Conduct](/patterns/1-initial/code-of-conduct.md) - *Communications and interactions between collaborators are rude, not inclusive or offensive, harming and increasing the discussions without any value added. A Code of Conduct provides guidelines for establishing rules and expectations regarding behavior and interactions within the community to build stronger levels of collaboration.* * [Trusted Committer and Contributor Retrospectives](/patterns/1-initial/cross-team-retrospectives.md) - *A host team working with contributors outside of their own line of management constantly runs into misunderstandings. As a result collaboration becomes brittle and frustrating. Setting aside time for regular retrospectives for the InnerSource team consisting of trusted committers and contributors can help make communication smooth.* * [InnerSource Hackathon](/patterns/1-initial/innersource-hackathon.md) - *In a company, initially only InnerSource enthusiasts are interested and practicing InnerSource during the early stages of InnerSource adoption; not all engineering teams are willing or have enough time and resources to adopt InnerSource. In this scenario, it is good to provide a safe space to try and adopt InnerSource through an InnerSource Hackathon event within the company.* +* [Managing Capacity for Reviewing Contributions](/patterns/1-initial/capacity-for-contributions.md) - *Reviewing InnerSource contributions takes time and effort. This should be reflected in capacity planning, especially for larger contributions. Expectations and available capacity should be transparent so that contributors understand when their contributions will be reviewed and, if accepted, released.*