Fix mailing list links (boostorg#1831)

Author: gregjkal

config/urls.py

@@ -164,7 +164,7 @@
         # temp page for community until mailman is done.
         path(
             "community/",
-            TemplateView.as_view(template_name="community_temp.html"),
+            TemplateView.as_view(template_name="community.html"),
             name="community",
         ),
         # Boost community calendar

core/tests/content/leaf.html

@@ -9303,7 +9303,7 @@ <h2 id="_acknowledgements">Acknowledgements</h2>
 <footer class="main-footer">
 <div class="footer-container">
 <div class="links">
-<a href="https://lists.boost.org/mailman/listinfo.cgi/boost-users">Contact</a>
+<a href="https://lists.boost.org/mailman3/lists/boost-users.lists.boost.org/">Contact</a>
 <a href="/privacy/">Privacy Policy</a>
 <a href="/terms-of-use/">Terms of Use</a>
 <a href="/doc/user-guide/reporting-issues.html">Report Bug</a>

templates/community_temp.html renamed to templates/community.html

@@ -13,17 +13,17 @@
         <h5 class="text-2xl leading-tight text-orange">Mailing Lists</h5>
         <p class="py-1 my-2 border-b pb-4 border-gray-700 text-slate dark:text-white">Discover the Boost library community with options tailored to developers, casual users, and enthusiasts.</p>
         <div class="grid lg:grid-cols-3">
-          <a href="https://lists.boost.org/mailman/listinfo.cgi/boost" class="px-2 py-3 text-center rounded-lg cursor-pointer hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
+          <a href="https://lists.boost.org/mailman3/lists/boost.lists.boost.org/" class="px-2 py-3 text-center rounded-lg cursor-pointer hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
             <h6 class="pb-1 text-sm md:text-base">Developers</h6>
             <i class="fa fa-helmet-safety"></i>
           </a>
 
-          <a href="https://lists.boost.org/mailman/listinfo.cgi/boost-users" class="order-3 px-2 py-3 text-center rounded-lg cursor-pointer lg:order-2 lg:col-span-1 hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
+          <a href="https://lists.boost.org/mailman3/lists/boost-users.lists.boost.org/" class="order-3 px-2 py-3 text-center rounded-lg cursor-pointer lg:order-2 lg:col-span-1 hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
             <h6 class="pb-1 text-sm md:text-base">Users</h6>
             <i class="fa fa-user fa-lg"></i>
           </a>
 
-          <a href="https://lists.boost.org/mailman/listinfo.cgi/boost-announce" class="order-2 px-2 py-3 text-center rounded-lg cursor-pointer lg:order-3 hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
+          <a href="https://lists.boost.org/mailman3/lists/boost-announce.lists.boost.org/" class="order-2 px-2 py-3 text-center rounded-lg cursor-pointer lg:order-3 hover:bg-gray-100 group dark:hover:bg-slate text-sky-600 dark:text-sky-300 hover:text-orange dark:hover:text-orange">
             <h6 class="pb-1 text-sm md:text-base">Announcements</h6>
             <i class="fa fa-bullhorn"></i>
           </a>

templates/includes/_footer.html

@@ -80,7 +80,7 @@
 <footer class="main-footer"{% if user.is_authenticated %} data-track-login-method="{{ request.user.indicate_last_login_method }}" data-login-method="{{ request.session.boost_login_method }}"{% endif %}>
   <div class="footer-container">
     <div class="links">
-      <a href="https://lists.boost.org/mailman/listinfo.cgi/boost-users">Contact</a>
+      <a href="https://lists.boost.org/mailman3/lists/boost-users.lists.boost.org/">Contact</a>
       <a href="{% url 'privacy' %}">Privacy Policy</a>
       <a href="{% url 'terms-of-use' %}">Terms of Use</a>
       <a href="/doc/user-guide/reporting-issues.html">Report Bug</a>

templates/review/review_process.html

@@ -12,7 +12,7 @@ <h2 id="steps-for-getting-a-library-accepted-by-boost">Steps for Getting a Libra
 
         <h3 id="learn-about-boost">Learn about Boost</h3>
         <p>
-          Follow posts on the <a href="https://lists.boost.org/mailman/listinfo.cgi/boost">Boost developers' mailing list</a> for a while, or look through the <a href="https://lists.boost.org/Archives/boost/">message archives</a>. Explore this website. Learn the <a href="../contributor-guide/requirements/library-requirements.html">Library Requirements</a>. Read the rest of this page to learn about the process. Search the web to get an idea of the commitment required to get a library into Boost.
+          Follow posts on the <a href="https://lists.boost.org/mailman3/lists/boost.lists.boost.org/">Boost developers' mailing list</a> for a while, or look through the <a href="https://lists.boost.org/Archives/boost/">message archives</a>. Explore this website. Learn the <a href="../contributor-guide/requirements/library-requirements.html">Library Requirements</a>. Read the rest of this page to learn about the process. Search the web to get an idea of the commitment required to get a library into Boost.
         </p>
 
         <p>There is a culture associated with Boost, aimed at encouraging high quality libraries by a process of discussion and refinement. Some libraries get past community review in less than two years from first concept, but most take longer, sometimes a lot longer. Five to ten years to get a library past review and into Boost is not unheard of, and you should prepare yourself for the personal investment required.</p>
@@ -25,7 +25,7 @@ <h3 id="determine-interest">Determine Interest</h3>
         <p>Potential library submitters should also be careful to publicize, canvas for, and gauge interest in their library, ideally before beginning it, but certainly before submitting it for review. Even a superbly designed library can fail review if there isn't enough interest in the subject matter; We can only review libraries with enough appeal to form a viable peer review. Ensuring that enough people are interested in your potential library goes a long way to ensure that.</p>
 
         <p>
-          There are many places to publicize and canvas for a library. The <a href="https://lists.boost.org/mailman/listinfo.cgi/boost">Boost developers' mailing list</a> ought to be your first stop in gauging interest in a possible new C++ library. Be prepared to pivot your design and focus until your proposed library finds traction. Other places useful for gauging interest in a library might be <a href="https://www.reddit.com/r/cpp/">Reddit/r/cpp</a>.
+          There are many places to publicize and canvas for a library. The <a href="https://lists.boost.org/mailman3/lists/boost.lists.boost.org/">Boost developers' mailing list</a> ought to be your first stop in gauging interest in a possible new C++ library. Be prepared to pivot your design and focus until your proposed library finds traction. Other places useful for gauging interest in a library might be <a href="https://www.reddit.com/r/cpp/">Reddit/r/cpp</a>.
         </p>
 
         <p>A message to the Boost developers mailing list might be as simple as "Is there any interest in a library which solves Traveling Salesperson problems in linear time?"</p>
@@ -59,13 +59,13 @@ <h3 id="refinement">Refinement</h3>
 
         <h3 id="getting-seconded-for-review">Getting Seconded for Review</h3>
         <p>
-          When you feel that your library is ready for entry into Boost, you need to find at least one member (but preferably several) of the Boost community who is willing to publicly endorse your library for entry into Boost. A simple method of achieving this is to post to the <a href="https://lists.boost.org/mailman/listinfo.cgi/boost">Boost developers' mailing list</a> a short description of your library, links to its github and documentation, and a request for endorsements.
+          When you feel that your library is ready for entry into Boost, you need to find at least one member (but preferably several) of the Boost community who is willing to publicly endorse your library for entry into Boost. A simple method of achieving this is to post to the <a href="https://lists.boost.org/mailman3/lists/boost.lists.boost.org/">Boost developers' mailing list</a> a short description of your library, links to its github and documentation, and a request for endorsements.
         </p>
 
         <p>It is expected that those who endorse a library for review will have performed at least a cursory check of the library's suitability for Boost in terms of documentation, fit with the rest of Boost and usefulness. A public endorsement of a library for review means that from an initial glance, they believe that the library has a reasonable chance to be accepted during a formal review. The expectation is that these endorsers will themselves review of the library during formal review period, though this is not binding.</p>
 
         <p>
-          Once you have a list of people who have publicly endorsed your library for review, email the <a href="https://lists.boost.org/mailman/listinfo.cgi/boost">Boost developers' mailing list</a> to request that your library be added to the <a href="review-results.html#currentscheule">Current Schedule</a> where the following information will be shown:
+          Once you have a list of people who have publicly endorsed your library for review, email the <a href="https://lists.boost.org/mailman3/lists/boost.lists.boost.org/">Boost developers' mailing list</a> to request that your library be added to the <a href="review-results.html#currentscheule">Current Schedule</a> where the following information will be shown:
         </p>
 
         <ul>