cleanup and adding some more content

Author: spier

meta/boardreports/2020-12.md

@@ -1,8 +1,8 @@
 # InnerSource Patterns WG - Report for Governance Meeting 2020-12
 
-**Reporting Period:** 11/2020 (since [previous report](2020-11.md))
+**Reporting Period:** 11/2020
 
-**Important Note:** This report does not contain the activity around the APAC Summit yet, as that falls into the next reporting period.
+**Important Note:** This report does not contain the Pattern work at the APAC Summit yet, as that falls into the next reporting period (12/2020).
 
 ## Mission
 
@@ -15,10 +15,8 @@
 
 *Sum up the status and health of your project and community in a few sentences*
 
-**Important Note:** Some interesting activity in the Patterns WG in November 2020, 
-
-- 2 new and new-ish contributor in the reporting period ([@WillemJiang](https://github.com/WillemJiang), [@MelindaMalmgren](https://github.com/MelindaMalmgren))
-- Challenges:
+- 2 new and new-ish contributors in the reporting period ([@WillemJiang](https://github.com/WillemJiang), [@MelindaMalmgren](https://github.com/MelindaMalmgren))
+- Challenges: (same as in the [last report](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/meta/boardreports/2020-11.md#projectcommunity-status-and-health))
 	- PRs with minor changes stay open for extended periods. This prevents quick incremental quality improvements. This might also demotivate contributors, as giving them a sense of success would be a way to keep them engaged in the project. Examples: [#213](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/213), [#222](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/222), [#230](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/230), [#232](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/232) 
 	- Also the longer a PR stays open, the higher the chances that that PR will go stale i.e. the author does not have time anymore to see the PR through. Examples of said risk are [13 PRs](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls?q=is%3Apr+is%3Aopen+created%3A%3C2020) that have been created prior to 2020, many even in 2017. Bringing these PRs to a stage where they can either be discontinued (i.e. closed) or approved+merged has proven difficult.
 - Activity and trusted committer diversity is too low to sustain the project in the long run on a high activity level. (Low activity evolution is sustainable.)
@@ -28,8 +26,8 @@
 *Describe the overall activity in the project over the reporting period.*
 
 - Great work in categorizing patterns according to where they are most impactful within an InnerSource Program (mindmap). This improves the discoverability of the patterns and helps us to understand to what extent the Patterns are already covering all phases of the full InnerSource lifecycle. - @fwan2000
-- Get [InnerSource Patterns book](https://innersourcecommons.gitbook.io/innersource-patterns/v/book/) ready for demo at the ISC 2020 APAC Summit  - @spier
-- Preparing for presentation at the ISC 2020 APAC Summit: *Level up your InnerSource through Patterns* - @fwan2000, @spier
+- Get [InnerSource Patterns book](https://innersourcecommons.gitbook.io/innersource-patterns/v/book/) ready for demo at the ISC 2020 APAC Summit - @spier
+- Preparing presentation for the ISC 2020 APAC Summit: *Level up your InnerSource through Patterns* - @fwan2000, @spier
 - Patterns office-hours concept try out, some success, dual time-zone meeting concept successfully in use in Marketing WG - @lenucksi
 - Continuing to work with the new Maturity levels (initial, structured, validated)
 
@@ -44,22 +42,19 @@
 
 *Describe the current plans of the project. Include goals the project is working towards as well as any announcements that should be published through the marketing group.*
 
-**Status: no changes/updates since last report**
-
 - Publish our [first official ebook](https://innersourcecommons.gitbook.io/innersource-patterns/v/book/) of the InnerSource Patterns. Once we do that, let’s announce that through our Marketing WG.
 - Process existing content from pull requests and Google group into our repository
 - Evaluate ideas to further facilitate collection of pattern content (e.g. through automation), channel ongoing discussions into pattern-work and attract more contributors, e.g. by lowering the barriers of entry for them.
 - Onboard further trusted committers
-- Possibly review the current list of trusted committers. Some of them don’t seem to be active anymore (likely they receive a lot of github/email spam from us today).
+- Review the current list of trusted committers. Some of them don’t seem to be active anymore and likely receive a lot of github notifcations and emails from us that they don't need. (do we have an offboarding process for TCs?)
+- Level up some patterns to higher maturity levels. e.g. the [InnerSource Portal](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/patterns/2-structured/innersource-portal.md) has multiple known instances and even a reference implementation now, so it could be brought to maturity "Validated" relatively easily.
 
 ## Last Committer Addition
 
 *When was the last committer added to the project? A healthy project tends to add new committers regularly. The report should indicate the most recent date on which a committer was added.*
 
-**Status: no changes/updates since last report**
-
-- 24th of April 2020: @lenucksi
 - 11th of December 2020: @spier
+- 24th of April 2020: @lenucksi
 
 ## Committer Diversity