Technology Committee/2016-04-22
From PCSAR
< Technology Committee(Difference between revisions)
(→Agenda) |
(→Participants) |
||
| (10 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) | ||
== Handouts == | == Handouts == | ||
| Line 16: | Line 19: | ||
== Minutes == | == Minutes == | ||
{{Meeting/Minutes}} | {{Meeting/Minutes}} | ||
| - | * {{ | + | |
| + | 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 | ||
| + | |||
| + | == Suggestions == | ||
| + | {{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" --> | ||
== Expenses == | == Expenses == | ||
{{Meeting/Expenses}} | {{Meeting/Expenses}} | ||
Current revision
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.
| # | Suggestion | Referred to |
|---|---|---|
| 0001 | determine how much of D4H equipment data can be easily exported | technology |
| 0002 | request D4H custom field type for clickable URL | technology |
| 0003 | Show tech committee how to support RapidNotify | technology |
| 0004 | Show tech committee how to support Phone.com | technology |
| 0005 | provide technology committee root access to server | technology |
