Adjust maturity model to new structure

... plus a few minor formatting fixes in the pattern itself. Also added
co-authors from the original issue.

Author: MaineC

README.md

@@ -35,6 +35,7 @@ The below lists all known patterns. They are grouped into three [maturity levels
 * [Contracted Contributor](patterns/2-structured/contracted-contributor.md) - *Associates wanting to contribute to InnerSource are discouraged from doing so by their line management. Relief is provided by formal contracts and agreements.*
 * [Dedicated Community Leader](patterns/2-structured/dedicated-community-leader.md) - *Select people with both communications and technical skills to lead the communities to ensure success in starting an InnerSource initiative.*
 * [Gig Marketplace](patterns/2-structured/gig-marketplace.md) - *Establish a marketplace by creating an intranet website that lists specific InnerSource project needs as "Gigs" with explicit time and skill requirements. This will enable managers to better understand their employee’s time commitment and professional benefits thereby increasing the likelihood of garnering approval to make InnerSource contributions.*
+* [Maturity Model](patterns/2-structured/maturity-model.md) - *Teams have started adopting InnerSource. The practice is spreading to multiple departments. Understanding of what constitutes an InnerSource project are wide spread though. The solution is to provide a maturity model to allow for teams to go through a self check and discover patterns and practices that they are not yet aware of.*
 * [InnerSource License](patterns/2-structured/innersource-license.md) - *Two legal entities that belong to the same organization want to share software source code with each other but they are concerned about the implications in terms of legal liabilities or cross-company accounting. An **InnerSource License** provides a reusable legal framework for the sharing of source code within the organization. This opens up new collaboration options, and makes the rights and obligations of the involved legal entities explicit.*
 * [InnerSource Portal](patterns/2-structured/innersource-portal.md) - *Create an intranet website that indexes all available InnerSource project information. This will enable potential contributors to more easily learn about projects that might interest them and for InnerSource project owners to attract an outside audience.*
 * [Praise Participants](patterns/2-structured/praise-participants.md) - *Thank contributors effectively to engender further engagement from them and to encourage others to contribute*

maturity-model.md patterns/2-structured/maturity-model.mdmaturity-model.md renamed to patterns/2-structured/maturity-model.md

@@ -208,3 +208,24 @@ Teams understand their level of InnerSource adoption.
 Prior to adopting InnerSource as a working model, teams are aware of the
 practices that are expected of them - both in the short term as well as in the
 long term.
+
+## Known Instances
+
+Entelgy, Zylk, Bitergia
+
+## Authors
+
+* Daniel Izquierdo Cortazar
+* Isabel Drost-Fromm
+* Jorge
+* Nerea
+
+## Acknowledgements
+
+## Status
+
+Drafted in September 2019
+
+Currently in status "Structured".
+
+