Technology Committee/2016-04-22

From PCSAR

Revision as of 03:25, 23 April 2016 (edit) Brett Wuth (Talk | contribs) (→Suggestions) ← Previous diff		Revision as of 03:32, 23 April 2016 (edit) (undo) Brett Wuth (Talk | contribs) (→Agenda) Next diff →
Line 9:		Line 9:
	== 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)

---

Revision as of 03:32, 23 April 2016

Contents 1 Booking 2 Participants 3 Agenda 4 Handouts 5 Minutes 6 Suggestions 7 Expenses

Booking

Meeting location, date, time and duration.

• 2016-04-22 19:00 by phone

Participants

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

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)

Handouts

Any related documents distributed before or during the meeting.

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

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

Expenses

Receipts related to the meeting.