Some cleanup in the 'meta' folder (#274)

Cleanup in the 'meta' folder. Improve FAQ, meta/README and git commandline steps.
Deleted unused images.

Author: spier

assets/img/patterns-steps-and-maturities.png

@@ -1,8 +1,10 @@
-This is a list of frequently asked questions about InnerSource Patterns
+# InnerSource Patterns FAQ
+
+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)
+* See the [pattern template](pattern-template.md)
 
 ## Why use a patterns approach to InnerSource?
 
@@ -13,6 +15,7 @@ This is a list of frequently asked questions about InnerSource Patterns
 * 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?
+## I'd like to consult with the InnerSource 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.
+* The vast majority of InnerSource Patterns meetings and all conversations in the InnerSource Commons [Slack](https://isc-inviter.herokuapp.com/) are held under the [Chatham House Rule](https://www.chathamhouse.org/chatham-house-rule) that should provide sufficient protection to enable a productive discussion.
+* To answer the question directly: No, you don't have to get NDAs signed :)

meta/FAQ.md

@@ -2,13 +2,16 @@
 
 The topics below cover information about how we define, operate, and upkeep this collection of patterns.
 
-* [Pattern Template](./pattern-template.md) - Start a new pattern with a copy of this
+* [Contributing](../CONTRIBUTING.md) - How to interact with our group, create your own patterns, or take part in our review-process; GitHub / Web centric instructions
+  * [Alternate Command-line steps](./technical-git-howto.md) - Contribute a pattern using `git` from the command-line
 * [Contributor Handbook](./contributor-handbook.md) - Lays out a basic guideline of how to write and contribute a new pattern, including the 3 maturity levels for patterns.
-* **(draft)** [Pattern System](./pattern-system.md) - For a human reader it is not easy to digest a long list of patterns. We are working on labeling and classifying the patterns further.
+* [Pattern Template](./pattern-template.md) - Start a new pattern with a copy of this
+* [FAQ](./FAQ.md) - Frequently asked questions about InnerSource Patterns
 * [Trusted Committers](../TRUSTED-COMMITTERS.md) - Who these people are, what elevated rights they get, and how you can become one
 * [Markdown Info](./markdown-info.md) - Markdown is the ascii text format our patterns are written in; this document briefly defines how we use it
-* [Contributing](../CONTRIBUTING.md) - How to interact with our group, create your own patterns, or take part in our review-process; Github / Web centric instructions
-  * [Alternate Command-line steps](./technical-git-howto.md) - If you want to contribute a pattern using `git` from the command-line, this is your document
+
+## Unfinished documentation
+
 * **(incomplete) Writing Guidelines** - To make the writing for our patterns more consistent, we provide some guidelines to help the various authors to keep a consistent voice.
   * [InnerSource Spelling](./innersource-spelling.md) - Clarifies the mystery around how to spell this. Spoiler: It is **InnerSource**.
-* [FAQ](./FAQ.md) - Frequently asked questions about InnerSource Patterns
+* **(draft)** [Pattern System](./pattern-system.md) - For a human reader it is not easy to digest a long list of patterns. We are working on labeling and classifying the patterns further.

meta/README.md

@@ -1,16 +1,19 @@
 # Command-line git steps for creating a new Pattern
 
-If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/InnerSourceCommons/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern.
+If you want to contribute a new pattern, the workflow is support by these important concepts:
 
-There are indeed multiple ways to start a discussion:
+* [Branches](https://github.com/InnerSourceCommons/InnerSourcePatterns/branches/all) are meant to separate content, so that multiple people can work all at once.
+* [Pull Requests](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls) (PR's) are used for discussion/review of a specific InnerSource pattern.
 
-* Send a Pull Request for your branch and the maintainers will receive a notification.
-* Create an Issue and ask for comments from some of the maintainers. You can mention them using the '@' symbol prior to their github nickname.
-* Add reviewers to the Pull Request on the website - this sends requests to review your work
+There are multiple ways to start a discussion:
 
-New patterns should use, as their base, the [pattern template file](pattern-template.md).
+* Fork the repo, create a branch, and then send a Pull Request for your branch. The maintainers will receive a notification about this automatically.
+* Create an [Issue](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues) and ask for comments from some of the [Trusted Committers](../TRUSTED-COMMITTERS.md). You can mention them using the '@' symbol prior to their GitHub username.
+* Add reviewers to your Pull Request in GitHub - this sends requests to review your work
 
-Please, when starting a new pattern, make sure that it does not already exist. Take a look at some of the [existing patterns in this repository](/README.md#reviewed-patterns-proven-and-reviewed).
+New patterns should use the [pattern template file](pattern-template.md) as their starting point.
+
+When starting a new pattern, make sure that it does not already exist. Take a look at the [existing patterns in this repository](/README.md#list-of-patterns).
 
 ## Overview of steps
 
@@ -20,10 +23,14 @@ The basic steps below can be thought of as *branch*, *commit*, *pull request*, a
 
 ## How do you create a branch?
 
-First you need to create a branch (no need to ask for permission!). For this, let's clone the repository:
+First you need to create a branch (no need to ask for permission!).
+
+For this, [create a fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) of this repository.
+
+Then create a [local clone of your fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#step-2-create-a-local-clone-of-your-fork).
 
 ```
-$ git clone https://github.com/InnerSourceCommons/InnerSourcePatterns.git
+$ git clone https://github.com/YOUR-USERNAME/InnerSourcePatterns.git
 ```
 
 Then you should see a message similar to the following one:
@@ -86,7 +93,7 @@ $ git checkout -b pattern/ewoks-do-not-hunt
 $ touch patterns/1-initial/ewoks-do-not-hunt.md
 ```
 
-You can fill your [markdown](markdown-info.md) file with the [pattern template text](pattern-template.md) and begin to fill it in with your pattern.
+We then fill our [markdown](markdown-info.md) file with the [pattern template text](pattern-template.md) and start to write our pattern.
 
 Once our pattern file is ready to go, we need to add the file to the repo and
 commit that change to our new branch.
@@ -96,7 +103,7 @@ $ git add patterns/1-initial/ewoks-do-not-hunt.md
 $ git commit -m "InnerSource Pattern to deal with Ewoks that do not hunt"
 ```
 
-And we should finally upload that branch and file to the server.
+And finally we upload that branch and file to the server.
 
 ```
 $ git push origin pattern/ewoks-do-not-hunt