Technology Committee/2016-04-22

From PCSAR

< Technology Committee(Difference between revisions)
Jump to: navigation, search
Current revision (03:53, 23 April 2016) (edit) (undo)
(Participants)
 
(6 intermediate revisions not shown.)
Line 6: Line 6:
== Participants ==
== Participants ==
{{Meeting/Participants}} <!-- Don't remove this line -->
{{Meeting/Participants}} <!-- Don't remove this line -->
 +
* {{member|Brett Wuth}}
 +
* {{member|Matt Lynch}}
== Agenda ==
== Agenda ==
{{Meeting/Agenda}} <!-- Don't remove this line -->
{{Meeting/Agenda}} <!-- Don't remove this line -->
-
* brainstorm tools for inventory
+
* brainstorm tools for inventory (done)
-
* ideas of what the committee should work on
+
* ideas of what the committee should work on (done)
* D4H bot password (done)
* D4H bot password (done)
Line 17: Line 19:
== Minutes ==
== Minutes ==
{{Meeting/Minutes}}
{{Meeting/Minutes}}
-
* {{subpage|Minutes}}
 
mediawiki
mediawiki
Line 41: Line 42:
-
* Develop plan for provincial digital radio system
+
* plan inventory tool
-
* investigate adding LASARA channel to PCSAR radios
+
** select tool: by May 3
 +
** trial run: firehall cabinet
* moving pcsar server to commercial host
* moving pcsar server to commercial host
** not necessarily Canadian host
** not necessarily Canadian host
-
* hand-off access to server (root)
+
** consider whipport.com in Lethbridge
 +
** upgrade the distribution
 +
** better DNS
* orientation to RapidNotify
* orientation to RapidNotify
* orientation to Phone.com
* orientation to Phone.com
 +
* hand-off access to server (root)
 +
* examine whether cheaper phone configurations (627-2262)
 +
 +
 +
* Develop plan for provincial digital radio system
 +
* investigate adding LASARA channel to PCSAR radios
 +
* email services
 +
** president@pcsar.ca
 +
** email portal webmail
 +
** email archive accessible to members
 +
** consider google for business
* custom mapping
* custom mapping
** standard search segments
** standard search segments
 +
** can we use front end tools that don't require much training
* GPS data integration
* GPS data integration
** download data from members GPS's or PCSAR's GPS's
** download data from members GPS's or PCSAR's GPS's
-
** load GPS with waypoints, route, base map, or segment area
+
** load GPS with waypoints, route, base map, or segment area (geofence)
-
* examine whether cheaper phone configurations (627-2262)
+
* examine cost of sat phones and alternatives
* examine cost of sat phones and alternatives
-
* how to integrate member's inReach devices into search
+
* inReach
-
* plan increase in number of team inReach devices
+
** how to integrate member's inReach devices into search
-
* automating inReach rate changes
+
** plan increase in number of team inReach devices
 +
** automating inReach rate changes
* computer in MCP
* computer in MCP
** dedicated
** dedicated
Line 68: Line 84:
* what offloads work from people that are busy
* what offloads work from people that are busy
-
 
+
actions:
 +
* investigate simple creation search polygons (segment boundaries)
 +
* what will it take to set up dedicated machine to collect GPS data
== Suggestions ==
== Suggestions ==
{{prompt|List suggestions for future actions that came up during this meeting.}}
{{prompt|List suggestions for future actions that came up during this meeting.}}
{{suggestion list}} <!-- To add a suggestion, save this page and then click on "New suggestion" -->
{{suggestion list}} <!-- To add a suggestion, save this page and then click on "New suggestion" -->
 +
== Expenses ==
== Expenses ==
{{Meeting/Expenses}}
{{Meeting/Expenses}}

Current revision

This page is based on the Meeting template.

Use that template to make similar pages.

Contents

[edit] Booking

Meeting location, date, time and duration.

  • 2016-04-22 19:00 by phone

[edit] Participants

List who should participate and indicate for each person whether they've been invited, have confirmed or declined, and attended.

[edit] Agenda

Purpose of meeting or detailed agenda.

  • brainstorm tools for inventory (done)
  • ideas of what the committee should work on (done)
  • D4H bot password (done)

[edit] Handouts

Any related documents distributed before or during the meeting.

[edit] Minutes

Rough notes or formal minutes of the meeting.


mediawiki

  • MonoDB
  • semantic mediawiki

Equipment Committee

  • Bill

D4H

  • would have to expand who has access to system
  • has good list of typical fields
  • risk of severed relationship
  • not integrated into wiki
  • cross-links to wiki - not active, no field type for HTML or URL
  • chance that we might not have D4H

trickle strategy

to do:

  • verify that D4H equipment can be fully exported (or at least all that's important to us)
  • request custom field type for clickable URLs


  • plan inventory tool
    • select tool: by May 3
    • trial run: firehall cabinet
  • moving pcsar server to commercial host
    • not necessarily Canadian host
    • consider whipport.com in Lethbridge
    • upgrade the distribution
    • better DNS
  • orientation to RapidNotify
  • orientation to Phone.com
  • hand-off access to server (root)
  • examine whether cheaper phone configurations (627-2262)


  • Develop plan for provincial digital radio system
  • investigate adding LASARA channel to PCSAR radios
  • email services
    • president@pcsar.ca
    • email portal webmail
    • email archive accessible to members
    • consider google for business
  • custom mapping
    • standard search segments
    • can we use front end tools that don't require much training
  • 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
  • inReach
    • how to integrate member's inReach devices into search
    • plan increase in number of team inReach devices
    • automating inReach rate changes
  • computer in MCP
    • dedicated
  • data connectivity at MCP


setting priorities

  • what saves money
  • what creates most impact
  • what offloads work from people that are busy

actions:

  • investigate simple creation search polygons (segment boundaries)
  • what will it take to set up dedicated machine to collect GPS data

[edit] Suggestions

List suggestions for future actions that came up during this meeting.

#SuggestionReferred to
0001determine how much of D4H equipment data can be easily exportedtechnology
0002request D4H custom field type for clickable URLtechnology
0003Show tech committee how to support RapidNotifytechnology
0004Show tech committee how to support Phone.comtechnology
0005provide technology committee root access to servertechnology

[edit] Expenses

Receipts related to the meeting.

Personal tools