<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div class="" style=""><span class="" style=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">HOT</span></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 12.727272033691406px; font-family: monospace; background-color: transparent; font-style: normal;"><span class="" style=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">The Tasking Manager is simply _critical_ to HOT response in emergencies, and preparedness projects. There has been a lot of coding work recently, Pierre Giraud getting V2 in shape for release. Developers and designers are eager to contribute. Everyone has creative ideas on improvements and new functionality for the
OSMTM.</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">We love the OSMTM :)</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">But, what HOT has lacked for OSMTM (and all of its software projects honestly) are structured ways to communicate, handle feedback, plan for the future, manage deployment schedule, onboard new developers and designers, etc. </span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px"
class="">With all the activity, this seems like the right moment to start to figure this out. All of us who have an interest in the OSMTM should meet soon. What I propose is that we gather at the next Tech Working Group meeting, and once other business has been concluded, we continue into an OSMTM agenda.</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">On the agenda would be</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">* The current development of V2 (I will send another email later today detailing where things are at)</span><br style="font-family: monospace; font-size:
12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">* The design and developer CU Boulder student initiative</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">* Defining a software management process for the OSMTM (ie communication, handling of bug/feature requests, deployment process, documentation, onboarding, etc)</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">I believe the next HOT Tech WG will be on Monday, May 5, at 17:00 UTC, on #hot IRC. (Drazen please correct me if that's wrong).</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family:
monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">Hopefully that works for most of us. Let me know directly if timing is an issue.</span><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><br style="font-family: monospace; font-size: 12.727272033691406px" class=""><span style="font-family: monospace; font-size: 12.727272033691406px" class="">Mikel</span><br class="" style=""></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 12.727272033691406px; font-family: monospace; background-color: transparent; font-style: normal;"><span class="" style=""><span style="font-family: monospace; font-size: 12.727272033691406px" class=""><br></span></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 12.727272033691406px; font-family: monospace; background-color: transparent; font-style: normal;"><span class="" style=""><span
style="font-family: monospace; font-size: 12.727272033691406px" class="">ps This is a resend of a message from yesterday that didn't seem to go through to the list, but did end up in the archive. Hope this works.</span></span></div><div class="" style=""></div><div class="" style=""> </div><div class="" style="">* Mikel Maron * +14152835207 @mikel s:mikelmaron</div></div></body></html>