Move the sigs and wgs introduction to their folders

README.md

@@ -19,7 +19,7 @@ following information.
 
 Community charter is documented in [governance.md](governance.md), this is
 an initial draft and will need to be approved and updated by the TSC. We
-also have [sig document](sigs.md) and [working group document](working-groups.md)
+also have [sig document](sigs/README.md) and [working group document](working-groups/README.md)
 charter provided.
 
 ## Code Of Conduct

governance.md

@@ -253,7 +253,7 @@ summary of the SIG's work to the community. SIGs are also responsible to:
 * Keep up-to-date meeting notes, linked from the SIG's page in the community
 repo
 * Announce meeting agenda and minutes after each meeting, on the
-mindspore-discuss mailing list and/or IRC or slack or other channel.
+`mindspore-discuss` mailing list and/or IRC or slack or other channel.
 * Ensure the SIG's decision making is archived (i.e on IRC meeting log)
 * Report activity in overall MindSpore community meetings
 * Participate in release planning meetings, retrospective, etc (if relevant)

sigs.md → sigs/README.md

 # SIGs - Special Interest Groups
 
-As described in the MindSpore [governance](governance.md), Special
+As described in the MindSpore [governance](../governance.md), Special
 Interest Groups (SIGs) are persistent groups responsible for specific parts of
 the project. SIGs have open and transparent proceedings to develop goals and
 implement code contributions. SIGs are also responsible for ongoing maintenance
@@ -10,7 +10,7 @@ of the code in their areas.
 
 If you are interested in participating, please [join the discussion](https://mailweb.mindspore.cn/postorious/lists/)
 in the respective list. Details about any upcoming meetings will also be shared
-in the mailing list. SIG artifacts can be found in the [sigs repository](sigs).
+in the mailing list. SIG artifacts can be found in the current repository.
 
 ## Current SIGs
 
@@ -26,3 +26,4 @@ in the mailing list. SIG artifacts can be found in the [sigs repository](sigs).
 | Security | This SIG is responsible for the development of MindSpore security related tools. |
 | AKG | This SIG is responsible for the development of MindSpore auto kernel generator. |
 | MSLITE | This SIG is responsible for the development of MindSpore lite. |
+| MDP | This SIG is responsible for the development of MindSpore programming library for Bayesian deep learning. |

working-groups.md → working-groups/README.md

 # Working Groups
 
-As described in the MindSpore [governance](governance.md), Working
+As described in the MindSpore [governance](../governance.md), Working
 Groups (WGs) are temporary groups formed to address issues that cross SIG
 boundaries. Working Groups have a have a clear goal measured through specific
 deliverables and disband after the goal is achieved. Working groups do not own
@@ -20,4 +20,11 @@ synthesize proposals and decisions.
 Working Groups have most of their discussions on mailing list. If you are
 interested in participating, please join the discussion in the respective list.
 Details about any upcoming meetings will also be shared in the mailing list.
-Working Group artifacts can be found in the [working-groups repository](working-groups).
+Working Group artifacts can be found in the current repository.
+
+## Current WGs
+
+| WG name | Responsibilities |
+| :------- | :--------------- |
+| Research | <center>&mdash;</center> |
+| MM | <center>&mdash;</center> |

working-groups/mm/README.md

+# MindSpore Molecular Modeling Working Group (WG)