Board Report 2023/02

meta/boardreports/2023-02.md

@@ -0,0 +1,77 @@
+# InnerSource Patterns WG - Report for Board Meeting 2023-02
+
+## Meta
+
+* Reporting Period: November 1st, 2022 - January 31st, 2022
+* [merged PRs](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls?q=is%3Apr+closed%3A2022-11-01..2023-01-31+is%3Amerged)
+* [opened issues](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues?q=is%3Aissue+created%3A2022-11-01..2023-01-31+is%3Aopen)
+
+## Engagement
+
+The [patterns book] is the way InnerSource practices are captured and shared. Recent web analytics:
+
+* stable traffic on the patterns book (tracking_id: `G-QL1S8MW5D9`)
+  * 12,143 page views total (previous report was 12,627)
+  * ~135 per day
+* Most popular patterns:
+  * InnerSource Portal
+  * Core Team
+  * 30 Day Warranty
+  * Maturity Model
+  * Common Requirements
+* traffic for translations:
+    * Japanese - No significant traffic yet.
+    * Chinese - No stats yet.
+
+## Changes
+
+Changes are contributed via the [InnerSourcePatterns] repository:
+
+* [Chinese book](https://patterns.innersourcecommons.org/v/zh/) release in 2023/01
+* Issues with getting Japanese content indexed by Google and other search engines has been fixed (by gitbook)
+* New **Structured** patterns:
+    * [Extensions to Manage Contributions at Scale](https://patterns.innersourcecommons.org/p/extensions-for-sustainable-growth) - great work @Ssukriti
+* New **Initial** patterns:
+    * [Incubator Pipeline](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/incubator-pipeline.md) - thanks @robtuley for moving this long-standing PR along and getting the content into our repo for greater visibility of the ISC community
+    * [InnerSource Customer Interview Questions](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/innersource-customer-interview-questions.md) - contributed by @kschueths as part of the last Summit. Thank you!
+* Adding Known Instances to various patterns e.g. WellSky, Dazn, and Mercado Libre. Special thanks to @privero-meli from our community in Brazil for adding Mercado Libre.
+* We are trying out GitHub Releases ([example](https://github.com/InnerSourceCommons/InnerSourcePatterns/releases/tag/v1.4)) to highlight all contributors to our book. We hope that they will appreciate that acknowledgement, and continue their contributions.
+* Various minor updates to existing patterns.
+
+## Next Goals (same as previous Board report)
+
+The overall goals of this group are:
+
+1. Increase number of people consuming the patterns. ("easier to discover", pattern of month, categories)
+2. Increase the number and quality of patterns.
+   1. Increase the number of people thinking to contribute. ("patterns in wild", "known instances")
+   2. Increase probability of successful contribution. ("reduce review time", "lower barrier of entry")
+   3. Optimise the existing content. (level-up more patterns, "known instances" again)
+
+All goals will be progressed but we are prioritising effort towards 2.iii.
+
+Specifically we want to get existing **Initial (L1)** patterns improved to **Structured (L2)**, so that we can publish them in the book.
+
+We had a [discussion](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/486#discussion_r1029921121) about this and created a short-list of those patterns (details below).
+
+### Shortlisted Patterns
+
+Here you find more detail about the possible execution of this approach.
+It is more information than what the Board needs. It may however help you to understand how we are reasoning about our patterns.
+
+We identified these patterns as "low-hanging fruits", as they contain a **Known Instance** already, and that info is often hard to get.
+
+We believe we can contact the respective authors/organizations, and ask them to review the patterns against the [Structured (L2) Requirements](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/meta/contributor-handbook.md#requirements-level-2---structured). The upside for those orgs is to get their pattern (and brand) published in our book.
+
+We expect that with one round of review (or rather a single PR) we can get these patterns published in our book.
+
+* **(done)** (IBM) [extensions-to-manage-contributions-at-scale.md](https://patterns.innersourcecommons.org/p/extensions-for-sustainable-growth)
+* **(in progress)** (Comcast) [release-process.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/release-process.md) - We kept this pattern in Initial to give the community time to review/harden this pattern before it goes into the book.
+* **(in progress)** (Flutter, Europace) [governance-levels.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/governance-levels.md) - Proposed by Europace (Isabel) but further improved by Rob.
+* (??? Tim Yao, Georg Grütter) [contained-innersource.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/contained-innersource.md) - This pattern has been around for a long time. It can try to contact the two authors and see if they want to bring it over the finish line.
+* (Philips) [source-code-inventory.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/source-code-inventory.md)
+* (Philips, Verizon) [balancing-openness-and-security.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/balancing-openness-and-security.md)
+* (GitHub) [transitioning-contractor-code-to-innersource-model.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/transitioning-contractor-code-to-innersource-model.md)
+
+[patterns book]: https://patterns.innersourcecommons.org/
+[InnerSourcePatterns]: https://github.com/InnerSourceCommons/InnerSourcePatterns/