Merge pull request #264 from nschonni/markdownlint-whitespace

fix: Markdownlint rules for whitespace

Author: lenucksi

.markdownlint.json

@@ -2,17 +2,13 @@
     "default": true,
     "MD004": false,
     "MD007": false,
-    "MD009": false,
-    "MD012": false,
     "MD013": false,
     "MD014": false,
-    "MD022": false,
     "MD024": false,
     "MD025": false,
     "MD026": false,
     "MD029": false,
     "MD030": false,
-    "MD032": false,
     "MD033": false,
     "MD034": false,
     "MD036": false,

CONTRIBUTING.md

@@ -4,7 +4,6 @@ The goal of the InnerSource patterns working group is to collect, document, and
 
 For this working group to strive, we welcome your contribution - be it small or huge.
 
-
 ## How to Contribute?
 
 Please consider contributing in the following ways:
@@ -19,7 +18,6 @@ Please consider contributing in the following ways:
 
 5. **Be a patterns advocate.** The patterns will become better and cover more topics the more people contribute their perspective and experience. A colleague told you about a novel InnerSource best practice? Please invite her/him to contribute to this repository!
 
-
 ## How to get in touch?
 
 We are happy to support you in contributing to the InnerSource patterns or to just chat with you. You can reach out to us in the following ways:
@@ -28,12 +26,10 @@ We are happy to support you in contributing to the InnerSource patterns or to ju
 
 2. **During the patterns office hours.** We established a regular cadence of office hours for you to ask questions. Find the date of the next patterns office hours [in this calendar](https://innersourcecommons.org/patterns-officehours).
 
-
 ## License of Contributions
 
 The contents of this repository are licensed under [CC-BY-SA-4.0](LICENSE.txt). By contributing to this repository, you grant us (and everyone else for that matter) the right to use your contribution in accordance with that license.
 
-
 ## Code of Conduct
 
 We do not yet have a fully formalized code of conduct yet. We expect all contributors to treat each other respectfully and help us to keep this community free of harassment and discrimination.

README.md

@@ -11,6 +11,7 @@ You are already using InnerSource in your company and want to share your ideas a
 ## Mission Statement
 
 Our mission in this working group
+
 - Collect and document agreed upon best practices of how to do InnerSource - in the form of patterns
 - Continuously publish the most mature patterns as an ebook
 

meta/FAQ.md

@@ -1,14 +1,18 @@
 This is a list of frequently asked questions about InnerSource Patterns
 
 ## What are the different parts of a pattern? What do they mean?
+
 * See the [pattern template](pattern-template.md) (in the *meta* subdirectory)
 
 ## Why use a patterns approach to InnerSource?
+
 * It abstracts information from known instances of proven solutions so that other people/companies can understand not only what was done by why it worked and how to adapt it to their own situations.
 
 ## How do you use the pattern?
+
 * Each organization has its own history (*context*) and culture (a source of *forces*) and even goals, so using a pattern to solve their problems will generally require adaptation of that pattern. Try to identify things about your situation that are unique and apply those as makes sense to the *Context* and *Forces* identified in the pattern. See if these additional constraints might require changes to the *Solution* to ensure that the pattern will work.
 * Patterns can also be used as a short-hand when discussing InnerSource programs across organizational boundaries.
 
 ## I'd like to consult with the IS Patterns community; do I need to have participating members sign NDAs?
+
 * You could do that, but be aware that the vast majority of IS Patterns meetings are held under the [Chatham House Rule](https://www.chathamhouse.org/chatham-house-rule) that should provide sufficient protection to enable a productive discussion.

meta/boardreports/2020-10-details.md

@@ -1,7 +1,7 @@
 # InnerSource Patterns WG - Report for governance meeting 2020-10
 
 **Details Section**
- 
+
 ## Project Activity - Describe the overall activity in the project over the past quarter.
 
 Here are some more detailed numbers as mentioned in short-form.
@@ -10,10 +10,10 @@ Here are some more detailed numbers as mentioned in short-form.
 
 #### Entirely new & merged: 5
 
-- RFCs #204 @tsadler1988 @spier @mainec 
+- RFCs #204 @tsadler1988 @spier @mainec
 - InnerSource Activity Score @michadelic SAP #189 @newmexicokid @spier
 - InnerSource License #147
-- Pattern Overview Mindmap: @feiwan2000 (very popular!) 
+- Pattern Overview Mindmap: @feiwan2000 (very popular!)
 - Europace sponsored: Mechanics and tooling recommendations #124, #123 #121 @mainec @rrutledge @martinklewitz @newmexicokid @sjn
 
 #### Entirely new & open: 2
@@ -29,7 +29,7 @@ Here are some more detailed numbers as mentioned in short-form.
 
 #### Progress on existing PRs: 8
 
-- #95 (almost done, @gruetter), #46 (#216, @gruetter) #120 #84 #78 #74 #71 #64 
+- #95 (almost done, @gruetter), #46 (#216, @gruetter) #120 #84 #78 #74 #71 #64
 
 ### Technical contributions: about 8
 
@@ -39,7 +39,7 @@ Here are some more detailed numbers as mentioned in short-form.
 
 ### Cleanup, Fixing & Migration: a lot
 
-- Fixing countless typos, broken links and inconsistent templates/documentation: @spier 
+- Fixing countless typos, broken links and inconsistent templates/documentation: @spier
 - Spelling, typos, examples #176, #175 @jpatrao
 - Typos, small improvements @stingrayza, @michadelic @funzinator
 

meta/boardreports/2020-10.md

@@ -15,9 +15,9 @@
 ## Project Activity - Describe the overall activity in the project over the past quarter.
 
 - New process proposal by @maxcapraro, discussion (@spier @mainec @newmexicokid @lenucksi) and successful adoption (initial, structured, validated, goal: faster first contribution, see contributor handbook)
-- Processing of existing content from wiki and existing PRs into publishable repo content, large scale cleanup, migration and fixing, all ongoing for the foreseeable future. 
+- Processing of existing content from wiki and existing PRs into publishable repo content, large scale cleanup, migration and fixing, all ongoing for the foreseeable future.
 - Great work towards content rendering (e.g. website, initial PDFs) in progress @spier @dizquerdo (https://innersourcecommons.gitbook.io/innersource-patterns-staging/v/book/)
-- Conference activity, more, interesting pattern activity on Slack leading to new patterns 
+- Conference activity, more, interesting pattern activity on Slack leading to new patterns
 - Patterns office-hours concept try out, some success, dual time-zone meeting concept successfully in use in marketing wg
 
 ### Pattern-work

meta/boardreports/2020-11.md

@@ -17,7 +17,7 @@
 
 - 1 new contributor in the reporting period (@WillemJiang)
 - Challenges:
-  - 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) 
+  - 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.)
 

meta/boardreports/2020-12.md

@@ -17,7 +17,7 @@
 
 - 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) 
+  - 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.)
 

meta/contributor-handbook.md

@@ -14,39 +14,36 @@ We have defined three maturity levels for patterns: The higher a pattern's matur
 | 2 | Structured | Contains a complete pattern that it is not properly validated yet (e.g. because it only synthesizes an idea or the experiences from one instead of three organizations). | A few days / weeks |
 | 3 | Validated | The pattern is validated (e.g. because three or more instances exists and are synthesized by the pattern) and its writing is of high quality. | A few months |
 
-For the first pattern you contribute, you should aim for maturity levels `1: Initial` or `2: Structured`. 
+For the first pattern you contribute, you should aim for maturity levels `1: Initial` or `2: Structured`.
 
 If you want to help promoting a pattern one maturity level up, we suggest to first create an issue to discuss the matter and see if someone else is working on that already. After that, you can create a pull request with the necessary changes.
 
 To achieve a given maturity level a pattern has to satisfy the requirements for that given maturity level and lower levels. The following sections lay out the requirements per maturity level in detail.
 
-
 ### Requirements: Level 1 - Initial
 
 Patterns (or other documents) of level 1 are stored in the directory `/patterns/1-initial`.
 
 - Validation requirements:
   - N/A
- 
+
 - Content requirements:
   - The document is readible & comprehensible for other parties (not just for the author(s))
   - The author(s) contribute the contents according to the [license](../LICENSE.txt) & are allowed to do so
   - Thoughts and contents by third parties are quoted / referenced explicitly
 
- 
 ### Requirements: Level 2 - Structured
 
 Patterns of level 2 are stored in the directory `/patterns/2-structured`.
 
 - Validation requirements:
-  - Is validated by at least one known instance 
+  - Is validated by at least one known instance
     - Alternatively: key elements of the pattern have been validated in separate contexts and, in consequence, it is justified to believe the full solution will function
- 
+
 - Content requirements:
   - Complies with the [patterns format](pattern-template.md)
   - Complies with *basic style guide*(#) - *Oops! We have not yet developed this*
- 
- 
+
 ### Requirements: Level 3 - Validated
 
 Patterns of level 3 are stored in the directory `/patterns/3-validated`.
@@ -55,7 +52,7 @@ Patterns of level 3 are stored in the directory `/patterns/3-validated`.
   - Is validated by at least three known instances
   - Considers all known instances to the best of working group members' knowledge
   - Community agreement (via lazy consensus of trusted committers) on correctness of contents
- 
+
 - Content requirements:
   - Uses & has no conflicts with working group terminology (defined by glossary / implicit usage) - *Oops! We have not yet developed this.*
   - Fits & has no conflicts with existing patterns (of this maturity level or higher)

meta/innersource-spelling.md

@@ -10,7 +10,7 @@ We encourage you to use the word as a proper noun (like “We use InnerSource in
 
 We favor the spelling **InnerSource**, for the following reasons:
 
-1. That’s the way Tim O’Reilly [spelled it in 2000][opengl_1200] (he was into Perl and camel-case was a thing). Also see the [Foreword of the Adopting InnerSource book][foreword_AdoptingInnerSource] for more of Tim O’Reilly's own words on the topic. 
+1. That’s the way Tim O’Reilly [spelled it in 2000][opengl_1200] (he was into Perl and camel-case was a thing). Also see the [Foreword of the Adopting InnerSource book][foreword_AdoptingInnerSource] for more of Tim O’Reilly's own words on the topic.
 2. If you set up side-by-side Google searches for “Inner Source” and “InnerSource” you will find that you get more hits on the former term, by only 1% of them have anything to do with what we call InnerSource. The latter term will be 100% cogent to your inquiry.
 3. The OSI was [denied trademark on the term “open source”][no-open-source-trademark] because it was made up of two common and unrelated terms. “InnerSource” on the other hand is a new word.