Merge pull request #54 from LinqLover/replace-pipermail-2

Fix another occurrence of pipermail

_includes/footer.html

@@ -3,7 +3,7 @@
     <p class="small">
         &copy; 1996-{{ site.time | date: '%Y' }} {{ site.copyright }} -
         <a href="/imprint/">Imprint</a> -
-        <a href="https://forum.world.st/Squeak-f45487.html" target="_blank"><i class="fa fa-globe"></i></a>
+        <a href="https://lists.squeakfoundation.org/archives/list/[email protected]/" target="_blank"><i class="fa fa-globe"></i></a>
         <a href="https://twitter.com/squeaksmalltalk" target="_blank"><i class="fa fa-twitter"></i></a>
         <a href="https://www.linkedin.com/groups?gid=98736" target="_blank"><i class="fa fa-linkedin"></i></a>
         <a href="https://github.com/squeak-smalltalk" target="_blank"><i class="fa fa-github"></i></a>

_pages/development_process.md

@@ -94,7 +94,7 @@ Here are some useful guidelines:
 
 * **You break it, you fix it.** If you change something, you are generally expected to take care of problems caused by this change. Though there are exceptions. If in doubt, please ask.
 
-* **Do good and talk about it.** When you are done with whatever you have been working on, let people know about it. It can be as short as a note to Squeak-dev, or a comment in the issue tracker, saying “I have fixed the long standing bug with *xyz.* Please update and enjoy.” Large numbers of interconnected patches and discussions can be hard to survey for others. Whenever possible, include references to related Monticello versions or threads on the mailing list (which are permalinkable via the [pipermail archives](http://lists.squeakfoundation.org/pipermail/squeak-dev/)) in the summary of your work.
+* **Do good and talk about it.** When you are done with whatever you have been working on, let people know about it. It can be as short as a note to Squeak-dev, or a comment in the issue tracker, saying “I have fixed the long standing bug with *xyz.* Please update and enjoy.” Large numbers of interconnected patches and discussions can be hard to survey for others. Whenever possible, include references to related Monticello versions or threads on the mailing list (which are permalinkable via the [mailman archives](https://lists.squeakfoundation.org/archives/list/squeak-dev@lists.squeakfoundation.org/)) in the summary of your work.
 
 * **Unit Testing.** Unit tests are an essential part of maintaining the reliability of our releases. New unit tests are always welcome. Keep in mind that a unit test should take as little time to run as possible. Maintaining the reliability of Squeak is always easier when all tests pass: If you break something, the appearance of a new failure or error is immediately obvious and the cause is more easily found. To that end fixes for failures or errors are extremely valuable. Also, please avoid submitting changes that cause failures or errors themselves.