[slow] warnings - online edit of handbook/transport.html

This commit is contained in:
Expo on server 2024-02-19 15:43:53 +00:00
parent d03b79242a
commit 816fc6b6b2

View File

@ -38,17 +38,19 @@ In the past we have communalised travel from Cambridge, but these days with peop
<ul> <ul>
<li><a href="treasurer.html#travelorg">Coordination and coercion</a> - why this is hard</li> <li><a href="treasurer.html#travelorg">Coordination and coercion</a> - why this is hard</li>
<li><a href="https://docs.google.com/spreadsheets/d/1iNzJySh0qTvWmgPN47jTJcuYv73JgKOCsPZwLNKz1XI/edit#gid=636195718">The 2019 travel matrix</a> - In Googledocs</li> <li><a href="https://docs.google.com/spreadsheets/d/1iNzJySh0qTvWmgPN47jTJcuYv73JgKOCsPZwLNKz1XI/edit#gid=636195718">The 2019 travel matrix</a> - In Googledocs</li>
<li><a href="https://camcaving.uk/Documents/Expo/Legacy/2018/Expo 2018_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - 2018 using SCRF as expo website was broken at a critical time - again</li>
<li><a href="../years/2017/whoandwhen.html">The travel matrix</a> - 2017 standard "who & when" format on the expo website. People edited this online using "Edit this page"</li> <li><a href="https://camcaving.uk/Documents/Expo/Legacy/2018/Expo 2018_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - [slow] 2018 using SCRF as expo website was broken at a critical time - again</li>
<li><a href="https://camcaving.uk/Documents/Expo/Legacy/2016/Expo 2016_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - 2016 using SCRF as expo website was broken. This has an example of additional "by week" and "by person" tables (scroll down to the bottom).</li> <li><a href="../years/2017/whoandwhen.html">The travel matrix</a> - [slow] 2017 standard "who & when" format on the expo website. People edited this online using "Edit this page"</li>
<li><a href="https://camcaving.uk/Documents/Expo/Legacy/2016/Expo 2016_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - [slow] 2016 using SCRF as expo website was broken. This has an example of additional "by week" and "by person" tables (scroll down to the bottom).</li>
<li><a href="https://camcaving.uk/Documents/Expo/Legacy/2014/Expo 2014_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - 2014 using SCRF as expo website was broken. This has an example of additional "by week" and "by person" tables (scroll down to the bottom).</li> <li><a href="https://camcaving.uk/Documents/Expo/Legacy/2014/Expo 2014_Who and When - Cambridge University Caving Club.htm">The travel matrix</a> - 2014 using SCRF as expo website was broken. This has an example of additional "by week" and "by person" tables (scroll down to the bottom).</li>
<li><a href="../years/2004/travel.html">The travel matrix</a> - 2004 (sophisticated) "who & when" (some browsers can't render this)</li> <li><a href="../years/2004/travel.html">The travel matrix</a> - 2004 (sophisticated) "who & when". Most browsers can't render this these days, so this is effectively broken. Shamne really, it worked well.</li>
</ul> </ul>
The expo handbook assumes (in places) that it is the Treasurer who organises transport; or by default it gets done by the expo leader. This is probably not a good idea and a dedicated transport coordinator should be nominated. This must be someone who has been on expo before, and who can liaise closely with the treasurer on decisions about allowable costs. The expo handbook assumes (in places) that it is the Treasurer who organises transport; or by default it gets done by the expo leader. This is probably not a good idea and a dedicated transport coordinator should be nominated. This must be someone who has been on expo before, and who can liaise closely with the treasurer on decisions about allowable costs.
<p> <p>
Entering data: we have had no particular problems requiring all expoers to hand-edit HTML or Markdown tables when stating their travel plans. This is somewhat surprising. Entering data: we have had no particular problems requiring all expoers to hand-edit HTML or Markdown tables when stating their travel plans. This is somewhat surprising.