Updating troggle docum. links in handbook

handbook/website-history.html

@@ -92,12 +92,16 @@ haphazard nature of the development of the "script and spreadsheet" method meant
 had an individual system for storing QMs. Without a standard system, it was sometimes unclear 
 how to correctly enter data. 
 
-<p><em>From "<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>
-Troggle: a novel system for cave exploration information management</a>", by Aaron Curtis, CUCC [with some additions]</em>
+<p><em>From "<a href="/expofiles/documents/troggle/troggle2020.pdf" download>
+Troggle: a revised system for cave data management</a>", by Philip Sargent and Aaron Curtis, CUCC [with some additions]</em>.
+ 
+<em>Original (2006) paper: "<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>
+Troggle: a novel system for cave exploration information management</a>", by Aaron Curtis</em>.
 <hr />
 
 <h2>History in summary</h2>
 
+<a href="https://en.wikipedia.org/wiki/RISC_OS"><img class="onright" src="t/riscos.jpg" width="100px"/></a>
 <p>The CUCC Website, which publishes the cave data, was originally created by 
 Andy Waddington in the early 1990s and was hosted by Wookey. 
 
@@ -130,8 +134,6 @@ troggle, the survey data, the tunnel data. Seagrass was turned off at
 the end of 2013, and the site has been hosted by Sam Wenham at the
 university since Feb 2014. 
 
-
-
 <h3>2018</h3>
 <p>In 2018 we had 4 repositories, 2 mercurial, 2 git
 
@@ -145,6 +147,26 @@ university since Feb 2014.
 <p>In spring 2018 Sam, Wookey and Paul Fox updated the  Linux version and the Django version (i.e. troggle) to 
 something vaguely acceptable to the university computing service and fixed all the problems that were then observed.
 
+<h3>Early 2019</h3>
+<p>In early 2019 the university computing service upgraded its firewall rules which took the
+server offline completely. 
+<p>
+Wookey eventually managed to find us free space (a virtual machine) 
+on a debian mirror server somewhere in Leicestershire (we think). 
+This move to a different secure server means that all ssh to the server now needs to use cryptographic keys tied to individual machines. There is an expo-nerds email list (all mailing lists are now hosted on wookware.org as the university list system restricted what non-Raven-users could do) to coordinate server fettling.
+
+<p>At the beginning of the 2019 expo two repos had been moved from mercurial to git: troggle and drawings (formerly called tunneldata). 
+</div>
+
+<h4>Wookey: July 2019</h4>
+<p>The troggle software has been migrated to git, and the old erebus and cvs branches (pre 2010) removed. Some decrufting was done to get rid of log files, old copies of embedded javascript (codemirror, jquery etc) and some fat images no longer used.
+<p>
+The tunneldata repo has also been migrated to git, and renamed 'drawings' as it includes therion data too these days.
+<p>
+The loser repo and expoweb repo need more care in hg->git migration (expoweb is the website content - which is published by troggle). Loser should have the old 1999-2004 CVS history restored, and maybe Tom's annual snapshots from before that, so ancient history can usefully be researched (sometimes useful). It's also a good idea to add the 2015, 2016 and 2017 ARGE data we got (in 2017) added in the correct years so that it's possible to go back to an 'end of this year' checkout and get an accurate view of what was found (for making plots and length stats). All of that requires some history rewriting, which is best done at the time of conversion.
+<p>
+Similarly expoweb is full of bloat from fat images and surveys and one 82MB thesis that got checked in and then removed. Clearing that out is a good idea. I have a set of 'unused fat blob' lists which can be stripped out with git-gilter. It's not hard to make a 'do the conversion' script, ready for sometime after expo 2019 has calmed down.
+
 <h3>More recent</h3>
 <p>
 For the current situation see <a href="troggle/trogstatus.html">expo systems status</a>.