Editing Technology Committee

From PCSAR

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This is a committee that has not yet been formally charted by the [[Board]].
It is currently discussing what it will look like.

== Members ==
* {{member|Brett Wuth}} (Chair)
<blockquote>{{Committee member suggestions|technology|Brett Wuth}}</blockquote>

* {{member|Matt Lynch}}
<blockquote>{{Committee member suggestions|technology|Matt Lynch}}</blockquote>

* {{member|Pat Neumann}}
<blockquote>{{Committee member suggestions|technology|Pat Neumann}}</blockquote>

([[Members:Membership Database/Technology|Database listing]])

== Mandate ==
* chartered at 2016-03-01 board meeting
== Meetings ==
* 2017: {{mtg|2017|02|21}}, {{mtg|2017|03|21}}, {{mtg|2017|05|16}}
* 2016: {{mtg|2016|04|22}}
== Communications ==
The Technology Committee has a dedicated mailing list: 
[[EMail Lists#pcsar-technology|pcsar-technology]].

== Discussion ==
The committee members have agreed to take on a technical role in PCSAR.

We don't want to create extra work for us, so we're proposing that we only
rarely meet as committee, instead we use technology for our advantage.
Email, SMS and the wiki.  Or other means if you can recommend them.

As PCSAR is increasing its use of technology, it needs people like us to
recommend a path forward and to support that technology when others
can't.

One of our strategies should be to set up technology in such a
way that non-technical members can use it without requiring much of our
time.  This should be especially true during searches, when we're all
likely to be tied up elsewhere.  We can achieve this through our choice
of technology, our design of how its used, simplification procedures,
and good documentation.

Areas which we think will fall partially under our area of
responsibility:

The server, including
* The [[wiki]] and [[web server]]
* The membership database stored online
* Mailing lists

D4H (the OFC's on-line record system)

RapidNotify (the call-out system)

Custom mapping

Phone.com (our multifeatured virtual phone system)

Our two regular phone lines (403-627-5804 and 403-627-2262)

inReach (satellite texting and locating service and device)

And possibly, when we look at the merits of future changes, to
* the Sat Phones 
* the radios

Most of these are areas where Brett has traditionally been doing work.
The intention isn't to dump these things on other people, but rather to make sure
they're part of the decision making of where we are going with these
and others have the knowledge and access to step in if he's not available.
== Issues ==
* See {{subpage|Suggestions}}

'''Immediate
* moving pcsar server to commercial host
** not necessarily Canadian host
** consider whipcord.com in Lethbridge
** upgrade the distribution
** better DNS
* hand-off access to server (root)
* computer in MCP
** dedicated
* email archive accessible to members
** gmail account
** use plus addressing for category: equipment, preplan
** consider having an email address that automatically posts messages to the wiki

'''Medium Term
* plan inventory tool
** select tool:
** trial run: firehall cabinet
* examine whether cheaper phone configurations, sat phones, inReach, and land lines
* data connectivity at MCP
* email services
** president@pcsar.ca
** email portal webmail
** consider google for business
* inReach
** how to integrate member's inReach devices into search
** plan increase in number of team inReach devices
** automating inReach rate changes

'''Medium Term extending into Long Term
* GPS data integration
** download data from members GPS's or PCSAR's GPS's
** load GPS with waypoints, route, base map, or segment area (geofence)
* examine cost of sat phones and alternatives
* custom mapping
** standard search segments
** can we use front end tools that don't require much training

'''Long Term
* Develop plan for provincial digital radio system

Priorities are set by:
# what offloads work from people that are busy
# what creates most impact
# what saves money

== Financial ==
* {{subpage|Budget}}

Please note that all contributions to PCSAR are considered to be released under the Attribution-Share Alike 3.0 Unported (see PCSAR:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://pcsar.dyndns.org:8080/mediawiki/index.php/Technology_Committee"

Editing Technology Committee

From PCSAR

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 100: / Line 100: @@
 * inReach
 ** how to integrate member's inReach devices into search
-*** ask inReach if they could have a way to volunteer their inReach to be accessible by PCSAR
 ** plan increase in number of team inReach devices
 ** automating inReach rate changes
-* GPS data integration
-** download data from members GPS's or PCSAR's GPS's
-** load GPS with waypoints, route, base map, or segment area (geofence)
 '''Medium Term extending into Long Term
+* GPS data integration
+** download data from members GPS's or PCSAR's GPS's
+** load GPS with waypoints, route, base map, or segment area (geofence)
 * examine cost of sat phones and alternatives
 * custom mapping