<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<span class="author-g-at5bfz122ztqf7aa2q45">Hi Team Terrain,</span>
<div id="magicdomid26" class="ace-line"><br>
</div>
<div id="magicdomid90" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">regarding your request for
the terrain layout, tents and locations, we would like to have a
tent for around 15 people. This includes both the guys from the
field phones and dect telephone system.</span></div>
<div id="magicdomid160" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">Furthermore we plan to
have a 2-seats POC helpdesk for arbitrary questions regarding
fieldphone/dect/telephone questions or issues in general for
now.</span></div>
<div id="magicdomid164" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">The dect registration with
its long queues should no longer be required as we've got an
auto-registration feature in the pipeline.</span></div>
<div id="magicdomid162" class="ace-line"><br>
</div>
<div id="magicdomid191" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">We've got a dependency to
the L0 utility building at/in the Aventure House since the field
phone switching center uses direct lines to every single field
phone deployed to the camping ground.</span></div>
<div id="magicdomid203" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">These lines use the
existing copper infrastructure of the scouting ground and L0 is
the connection point.</span></div>
<div id="magicdomid204" class="ace-line"><br>
</div>
<div id="magicdomid209" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">As discussed on Nov, 25th,
a tent on the sand patch would be fine, but the location is not
defined, yet.</span></div>
<div id="magicdomid214" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">Furthermore we discussed
some ideas how to cross footpaths, like bury the telephone
cables in the sand or routing the cables over the roof of the
Aventure House to the tent.</span></div>
<div id="magicdomid215" class="ace-line"><br>
</div>
<div id="magicdomid280" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">We'd appreciate a location
close to L0 utility since a short distance from the tent to L0
is crucial for us. High core copper cables are unfortunately
very expensive.</span></div>
<div id="magicdomid281" class="ace-line"><br>
</div>
<div id="magicdomid22" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">Thanks for your efforts!</span></div>
<div id="magicdomid282" class="ace-line"><br>
</div>
<div id="magicdomid23" class="ace-line"><span
class="author-g-at5bfz122ztqf7aa2q45">chris1911 for Team POC</span></div>
<div id="magicdomid11" class="ace-line"><br>
</div>
<p><br>
</p>
<div class="moz-cite-prefix">On 2020-11-24 19:52, Ruud Koolen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:202011242052.40404.redlizard@redlizard.nl">
<pre class="moz-quote-pre" wrap="">Dear Team:POC,
It's high time we got going on getting a rough version of the MCH2021 terrain
layout together.
Despite the mantra of copy/paste/improve, the plan is not to use the layout
from SHA2017 as an authoritative baseline. Many things have changed since
four years ago, and many lessons were learned; so we are going to take a
fresh look at the space we have and how to fill it, taking into account new
opportunities, new restrictions, and feedback about what worked well and what
did not.
In that context, I'd like to hear what your team would like the terrain layout
to look like. What big space-using things are you going to be organizing,
that need a spot? And does your team have strong opinions about where those
things should go, or where other general-purpose things should go relative to
each other? Are there things that need to be close to other things, or far
away from other things, or with access to particular infrastructure, for your
team to be able to do its job? And are there such constraints that are not
strictly necessary, but which would be very convenient if it can be arranged?
I have given my best estimates of the answers to the questions, listed below;
but these are certain to be complete. If you could send me a mail with all
the things I inevitably missed, I'd be much obliged. General feedback on what
you'd like to see changed, or what worked very nicely last time and what you
would like me to not touch, are also very welcome.
If mail is not sufficient, and you'd like to talk it over in more detail
and/or draw things on whiteboards, ping me on IRC and we'll set something up.
Or join tomorrow's mumble meeting, and yell at me.
On the topic of tomorrow's mumble meeting, I would be very happy with some
ideas, wishlists, and inspiration about terrain layout from a broad audience.
So by all means, join the discussion tomorrow, and tell me all about what
needs to move and what should stay right where it is, and why.
----------
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">What big space-using things are you going to be organizing, that need a spot?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">- POC backoffice tent and helpdesk
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">And does your team have strong opinions about where those things should go,
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">or where other general-purpose things should go relative to each other?
- Does the POC backoffice necessarily want to be close to a centralized crew
area? Or is somewhere in the middle of camping grounds just as nice?
----------
Kind regards,
Team:Terrain
</pre>
</blockquote>
</body>
</html>