lists: Update to new asterisk-dev mailing list and push community forums.

Author: jcolp

docs/Asterisk-Community/Asterisk-Community-Code-of-Conduct.md

@@ -26,7 +26,7 @@ Ask for help
 ------------
 
 * If you don't know how to proceed with an aspect of development or documentation, ask for help! Always read the documentation, but don't be afraid to ask "silly" questions.
-* When asking for help, take advantage of the resources that are available to you, including the [Documentation](https://docs.asterisk.org), [mailing list archives](http://lists.digium.com/mailman/listinfo/), and [Asterisk: The Definitive Guide](http://asteriskdocs.org/).
+* When asking for help, take advantage of the resources that are available to you, including the [Documentation](https://docs.asterisk.org), [community forums](https://community.asterisk.org/), [mailing list archives](http://lists.digium.com/mailman/listinfo/), and [Asterisk: The Definitive Guide](http://asteriskdocs.org/).
 
 Take responsibility
 -------------------
@@ -67,5 +67,5 @@ The role of project leadership is handled by the founders of the Asterisk projec
 
 In addition to providing development resources for Asterisk itself, Sangoma provides community resources including the bug tracker, mailing lists, wiki, version control, continuous integration services, and other necessary project infrastructure. 
 
-Development discussions take place on the public [asterisk-dev mailing list](http://lists.digium.com/mailman/listinfo/asterisk-dev) and the [#asterisk-dev](https://libera.chat/) IRC channel. More information on the development of Asterisk can be found on the Asterisk wiki.
+Development discussions take place on the public [asterisk-dev mailing list](https://groups.io/g/asterisk-dev) and the [#asterisk-dev](https://libera.chat/) IRC channel. More information on the development of Asterisk can be found on the Asterisk wiki.
 

docs/Asterisk-Community/Asterisk-Community-Services.md

@@ -11,6 +11,6 @@ There are several services provided for the development of Asterisk.
 * [Source Browsing](https://github.com/asterisk/asterisk)
 * [Mailing Lists](/Asterisk-Community/Mailing-Lists)
 
-The Asterisk development team directly maintain a subset of community services, specifically the legacy Atlassian services and the downloads server. If downtime is expected a notice will be sent to the [asterisk-announce](http://lists.digium.com/mailman/listinfo/asterisk-announce) mailing list.
+The Asterisk development team directly maintain a subset of community services, specifically the legacy Atlassian services and the downloads server. If downtime is expected a notice will be posted on the [community forums](https://community.asterisk.org/).
 
-If community services are unavailable for a prolonged period of time, please notify [the Asterisk development team.](mailto:asteriskteam@digium.com?subject=Community-Service-Interruption)
+If community services are unavailable for a prolonged period of time, please notify [the Asterisk development team.](mailto:asteriskteam@digium.com?subject=Community-Service-Interruption)

docs/Asterisk-Community/Asterisk-Issue-Guidelines.md

@@ -24,7 +24,7 @@ Search and ask on the forums, mailing lists, and IRC. Again, see <http://www.ast
 * **Random wishes and feature requests with no patch:** (I want Asterisk to support <insert obscure protocol or gadget>, but I don't know how to code!)  
 See the [How to request a feature section](#how-to-request-a-feature-or-improvement) for more information on requesting a feature.
 * **Business development requests** (I will pay you to make Asterisk support fancy unicorn protocol!)  
-Please head to the asterisk-biz mailing list at <http://lists.digium.com>. If what you want is a specific feature or bug fixed, you may want to consider [requesting a bug bounty](/Development/Asterisk-Bug-Bounties).
+Please head to the Commercial category at <https://community.asterisk.org/>. If what you want is a specific feature or bug fixed, you may want to consider [requesting a bug bounty](/Development/Asterisk-Bug-Bounties).
 * and...
 
 
@@ -160,7 +160,7 @@ Feature or improvement requests without patches are not kept on the primary issu
 
 New features and major architecture changes are often discussed at the [AstriDevCon](/Development/Roadmap/AstriDevCon) event held before Astricon.
 
-If you really need the feature, but are not a programmer, you'll need to find someone else to write the code for you. Luckily, there are many talented Asterisk developers out there that can be contacted on the [asterisk-biz](http://lists.digium.com) mailing list. You can also offer a bounty for a bug or new feature - see [Asterisk Bug Bounties](/Development/Asterisk-Bug-Bounties) for more information.
+If you really need the feature, but are not a programmer, you'll need to find someone else to write the code for you. Luckily, there are many talented Asterisk developers out there that can be contacted on the [community forums](https://community.asterisk.org/). You can also offer a bounty for a bug or new feature - see [Asterisk Bug Bounties](/Development/Asterisk-Bug-Bounties) for more information.
 
 Patch and Code Submission
 -------------------------
@@ -181,7 +181,7 @@ There are some key qualities to keep in mind. These should be reflected in your
 #### How can I speed up my issue resolution?
 
 1. Follow the guidelines on this patch! Having good, accurate information that helps bug marshals reproduce the issue typically leads to much faster issue resolution.
-2. Provide a patch! Issues with patches are also generally resolved much faster. If you can't write a patch, there are many smart, talented developers in the Asterisk community who may be worth helping you. You can contract with them on the [asterisk-biz](http://lists.digium.com) mailing list, or offer a [bug bounty](/Development/Asterisk-Bug-Bounties).
+2. Provide a patch! Issues with patches are also generally resolved much faster. If you can't write a patch, there are many smart, talented developers in the Asterisk community who may be worth helping you. You can contract with them on the [community forums](https://community.asterisk.org/), or offer a [bug bounty](/Development/Asterisk-Bug-Bounties).
 
 
 

docs/Asterisk-Community/Mailing-Lists.md

@@ -3,20 +3,24 @@ title: Mailing Lists
 pageid: 22088306
 ---
 
-There are several [mailing lists](http://lists.digium.com/) where community members can go do discuss Asterisk. Some of the key lists are:
+### Community Forums
 
+For end-user support and commercial postings the [community forums](https://community.asterisk.org/) should be used.
 
+### Development Mailing List
+
+A [development mailing list](https://groups.io/g/asterisk-dev) is present for discussion regarding the development of Asterisk itself.
+
+### Read-Only Mailing Lists
+
+The Asterisk project previously maintained an independent mailing list server for many different purposes. This has been decommissioned and archived, with the community forums and new development mailing list taking their place. Links to the old mailing lists remain below in case archive access is required.
 
 | List | Description |
 | --- | --- |
 | [asterisk-announce](http://lists.digium.com/mailman/listinfo/asterisk-announce) | Asterisk releases and community service announcements |
 | [asterisk-biz](http://lists.digium.com/mailman/listinfo/asterisk-biz) | Commercial and Business-Oriented Asterisk Discussion |
-| [asterisk-dev](http://lists.digium.com/mailman/listinfo/asterisk-dev) | Discussions about the development of Asterisk. [#Development List Note](#development-list-note) |
-| [asterisk-app-dev](http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev) | Discussions about the development of applications that use Asterisk. [#Development List Note](#development-list-note) |
+| [asterisk-dev](http://lists.digium.com/mailman/listinfo/asterisk-dev) | Discussions about the development of Asterisk. |
+| [asterisk-app-dev](http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev) | Discussions about the development of applications that use Asterisk. |
 | [asterisk-security](http://lists.digium.com/mailman/listinfo/asterisk-security) | Asterisk Security Discussion |
 | [asterisk-users](http://lists.digium.com/mailman/listinfo/asterisk-users) | Discussions about the use and configuration of Asterisk. |
 
-### Development List Note
-
-The asterisk-dev list is geared toward the development of Asterisk itself. For discussions about developing applications that *use* Asterisk, please see the [asterisk-app-dev](http://lists.digium.com/mailman/listinfo/asterisk-app-dev) list. For discussions about deploying or using Asterisk, please see the [asterisk-users](http://lists.digium.com/mailman/listinfo/asterisk-users) mailing list.
-

docs/Development/Asterisk-Bug-Bounties.md

@@ -6,7 +6,7 @@ pageid: 22087953
 I want to offer a bounty for a particular bug! Where can I do that?
 -------------------------------------------------------------------
 
-Bug bounties for Asterisk may be posted on the Asterisk Development mailing list at <http://lists.digium.com/mailman/listinfo/asterisk-dev>
+Bug bounties for Asterisk may be posted on the Asterisk Development mailing list at <https://groups.io/g/asterisk-dev>
 
 **Minimum offer:** $500
 
@@ -43,7 +43,6 @@ This was discussed on the dev list in Jan 2013: <http://lists.digium.com/piperma
 
 ### Finding bug bounties
 
-The archives of the Asterisk Development mailing list located at <http://lists.digium.com/pipermail/asterisk-dev/> can be used to locate bug bounties. For bounties which are also present on the Asterisk issue tracker they will be displayed below:
-
- Digium/Asterisk JIRAee634d14-2067-31b4-9ca3-00e0845ec070labels = bounty and status != closed
+The legacy archives of the Asterisk Development mailing list located at <http://lists.digium.com/pipermail/asterisk-dev/> can be used to locate old bug bounties.
 
+Current Asterisk Development mailing list archives are located at <https://groups.io/g/asterisk-dev/>.

docs/Development/Policies-and-Procedures/C-API-Deprecation.md

@@ -39,7 +39,7 @@ Marking A C API As Deprecated For Standard Release
 
 #### The following instructions are for the master branch in which the C API is to be deprecated.
 
-1. Before a C API can be marked as deprecated a discussion needs to occur on the [asterisk-dev mailing list](http://lists.digium.com/pipermail/asterisk-dev/) and its use has to be confirmed as non-critical.
+1. Before a C API can be marked as deprecated a discussion needs to occur on the [asterisk-dev mailing list](https://groups.io/g/asterisk-dev/) and its use has to be confirmed as non-critical.
 2. Create a new issue in the [Asterisk project issue tracker](https://github.com/asterisk/asterisk/issues/) using the "Deprecation" issue type. Ensure the issue summary is descriptive as it will go into release notes.
 3. Obtain the Asterisk source code from [GitHub](https://github.org/asterisk/asterisk). Since you'll need to put your patch up for review, make an account in GitHub as well, following the instructions in [Code Contribution](/Development/Policies-and-Procedures/Code-Contribution).
 4. Create a new Git branch for your deprecation change.

docs/Development/Policies-and-Procedures/Module-Deprecation.md

@@ -47,7 +47,7 @@ Marking A Module As Deprecated For Standard Release
 
 #### The following instructions are for the master branch in which the module is to be deprecated.
 
-1. Before a module can be marked as deprecated a discussion needs to occur on the [asterisk-dev mailing list](http://lists.digium.com/pipermail/asterisk-dev/). Depending on the result of this it would also be wise to reach out the [asterisk-users mailing list](http://lists.digium.com/pipermail/asterisk-users/) and [community forums](https://community.asterisk.org/) to ensure that the module is not seeing widespread usage. If you feel uncomfortable doing so reach out to unknown user and he can assist in doing so.
+1. Before a module can be marked as deprecated a discussion needs to occur on the [asterisk-dev mailing list](https://groups.io/g/asterisk-dev/). Depending on the result of this it would also be wise to reach out the [community forums](https://community.asterisk.org/) to ensure that the module is not seeing widespread usage. If you feel uncomfortable doing so reach out to unknown user and he can assist in doing so.
 2. Create a new issue in the [Asterisk project issue tracker](https://github.com/asterisk/asterisk/issues/) using the "Deprecation" issue type. Ensure the issue summary is descriptive as it will go into release notes.
 3. Obtain the Asterisk source code from [GitHub](https://github.com/asterisk/asterisk). Since you'll need to put your patch up for review, make an account in GitHub as well, following the instructions on [Code Contribution](/Development/Policies-and-Procedures/Code-Contribution).
 4. Create a new Git branch for your deprecation change.

docs/Development/Policies-and-Procedures/New-Features-and-Improvements.md

@@ -48,7 +48,7 @@ If a new feature or improvement causes a regression the project may choose to re
 Large Number Of Commits
 =======================
 
-If an overall change consists of a large number of commits (such as across the tree spelling fixes or doxygen fixes) please reach out to the [asterisk-dev mailing list](http://lists.digium.com/mailman/listinfo/asterisk-dev) for guidance on the best way to put the change up for review before doing so. Depending on the number of commits you may be asked to squash them into a single commit for a review, instead.
+If an overall change consists of a large number of commits (such as across the tree spelling fixes or doxygen fixes) please reach out to the [asterisk-dev mailing list](https://groups.io/g/asterisk-dev) for guidance on the best way to put the change up for review before doing so. Depending on the number of commits you may be asked to squash them into a single commit for a review, instead.
 
 Changes In Review When Branch Goes Security Fix Only
 ====================================================

docs/Development/Roadmap/Asterisk-14-Projects/index.md

@@ -5,7 +5,7 @@ pageid: 30279108
 
 This page serves as a place to collect development information and notes for Asterisk 14.
 
-If you have any questions about the content here, please talk with developers on the [asterisk-dev](http://lists.digium.com/mailman/listinfo/asterisk-dev) mailing list or #asterisk-dev.
+If you have any questions about the content here, please talk with developers on the [asterisk-dev](https://groups.io/g/asterisk-dev) mailing list or #asterisk-dev.
 
 
 

docs/Development/Roadmap/Asterisk-15-Projects/Stream-Support-Across-Asterisk.md

@@ -24,7 +24,7 @@ Stream support has been merged into Asterisk as of 15. This has been done in a b
 
 
 !!! info ""
-    If you are reading this and have any questions consulting the [asterisk-dev mailing list](http://lists.digium.com/mailman/listinfo/asterisk-dev) or the [#asterisk-dev](/Asterisk-Community/IRC) IRC channel are the best venues for discussion.
+    If you are reading this and have any questions consulting the [asterisk-dev mailing list](https://groups.io/g/asterisk-dev) or the [#asterisk-dev](/Asterisk-Community/IRC) IRC channel are the best venues for discussion.
 
       
 [//]: # (end-info)