DOCS Replaced references to core mailinglist with forum

docs/en/05_Contributing/00_Issues_and_Bugs.md

@@ -57,6 +57,5 @@ read our guide on [how to write secure code](/developer_guides/security/secure_c
 
 ## Sharing your Opinion
 
-* [silverstripe.org/forums](http://www.silverstripe.org/community/forums/): Forums on silverstripe.org
-* [silverstripe-dev](http://groups.google.com/group/silverstripe-dev/): Core development mailinglist
+* [forum.silverstripe.org](http://forum.silverstripe.org): Forums on silverstripe.org
 * [All issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues)

docs/en/05_Contributing/01_Code.md

@@ -93,7 +93,7 @@ Once your pull request is issued, it's not the end of the road. A [core committe
 If you've been naughty and not adhered to the [coding conventions](coding_conventions), 
 expect a few requests to make changes so your code is in-line.
 
-If your change is particularly significant, it may be referred to the [mailing list](https://groups.google.com/forum/#!forum/silverstripe-dev) for further community discussion.
+If your change is particularly significant, it may be referred to the [forum](https://forum.silverstripe.org) for further community discussion.
 
 A core committer will also "label" your PR using the labels defined in GitHub, these are to correctly classify and help find your work at a later date.
 
@@ -165,7 +165,7 @@ After you have edited the file, GitHub will offer to create a pull request for y
 [API documentation](https://api.silverstripe.org/) for good examples.
 * Check and update documentation on [docs.silverstripe.org](https://docs.silverstripe.org). Check for any references to functionality deprecated or extended through your patch. Documentation changes should be included in the patch.
 * When introducing something "noteworthy" (new feature, API change), [update the release changelog](/changelogs) for the next release this commit will be included in.
-* If you get stuck, please post to the [forum](https://www.silverstripe.org/community/forums) or for deeper core problems, to the [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
+* If you get stuck, please post to the [forum](https://www.silverstripe.org/community/forums)
 * When working with the CMS, please read the ["CMS Architecture Guide"](/developer_guides/customising_the_admin_interface/cms_architecture) first
 
 ## Commit Messages

docs/en/05_Contributing/04_Release_Process.md

@@ -136,7 +136,7 @@ timeline and ask the reporter to keep the issue confidential until we announce i
    Additionally, [CVE](http://cve.mitre.org) numbers are accepted.
 *  Halt all other development as long as is needed to develop a fix, including patches against the current and one
 previous major release (if applicable).
-* Pre-announce the upcoming security release to a private mailing list of important stakeholders (see below).
+* Pre-announce the upcoming security release to aprivate pre-announcement mailing list of important stakeholders (see below).
 *  We will inform you about resolution and [announce](https://forum.silverstripe.org/c/releases) a 
 [new release](http://silverstripe.org/security-releases/) publically.
 

docs/en/05_Contributing/07_Translations.md

@@ -134,7 +134,7 @@ This also applies for any modules staying compatible with SilverStripe 2.x.
 
 ## Contact
 
-Translators have their own [mailinglist](https://groups.google.com/forum/#!forum/silverstripe-translators), but you can 
+Translators have their own [mailing list](https://groups.google.com/forum/#!forum/silverstripe-translators), but you can 
 also reach a core member on [IRC](https://irc.silverstripe.org). The transifex.com interface has a built-in discussion 
 board if you have specific comments on a translation.
 

docs/en/05_Contributing/index.md

@@ -3,7 +3,7 @@ introduction: Any open source product is only as good as the community behind it
 
 ## House rules for everybody contributing to SilverStripe
  * Read over the SilverStripe Community [Code of Conduct](code_of_conduct) 
- * Ask questions on the [forum](http://silverstripe.org/community/forums), and stick to more high-level discussions on the [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
+ * Ask questions on the [forum](http://silverstripe.org/community/forums)
  * Make sure you know how to [raise good bug reports](issues_and_bugs)
  * Everybody can contribute to SilverStripe! If you do, ensure you can [submit solid pull requests](code)
 

docs/en/index.md

@@ -15,13 +15,13 @@ and play with the interactive [demo website](http://demo.silverstripe.org/).
 
 SilverStripe has an wide range of options for getting support:
 
+* Join our [forum](https://forum.silverstripe.org)
 * Ask technical questions on [Stack Overflow](https://stackoverflow.com/questions/tagged/silverstripe) 
 * Get help on our [Slack channel](https://www.silverstripe.org/community/slack-signup/)
 * Read the technical reference in our [API Documentation](http://api.silverstripe.org/)
 * Get a user-focused overview of the CMS features in our [User Help](http://userhelp.silverstripe.com)
 * Discuss new features, API changes and the development [roadmap](http://www.silverstripe.org/software/roadmap/)
   on [UserVoice](http://silverstripe.uservoice.com/forums/251266-new-features)
-* Join our [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
 
 
 ## Building your first SilverStripe Web application