2023-2024 NET Program Realignment: Revision history

16 November 2023

• curprev 11:5211:52, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 42,027 bytes +12‎ →‎Training Centers
• curprev 11:5211:52, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 42,015 bytes +12‎ →‎Centralized Deployments
• curprev 11:5111:51, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 42,003 bytes +12‎ →‎A few of the NET program's known issues
• curprev 11:5111:51, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,991 bytes +12‎ →‎2.) Training and socializing
• curprev 11:5111:51, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,979 bytes +12‎ →‎Organizational changes
• curprev 11:5111:51, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,967 bytes +6‎ →‎Climate change
• curprev 11:5111:51, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,961 bytes +6‎ →‎Climate change
• curprev 11:4911:49, 16 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,955 bytes +659‎ →‎Summary Tag: Visual edit

15 November 2023

• curprev 16:2816:28, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ 41,296 bytes +1‎ →‎Timeline
• curprev 16:2716:27, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 41,295 bytes +2,036‎ →‎3.) Conduct a Capacity Assessment of the neighborhood Tag: Visual edit
• curprev 16:1116:11, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 39,259 bytes +33‎ →‎3.) Conduct a Capacity Assessment of the neighborhood Tag: Visual edit
• curprev 16:1016:10, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 39,226 bytes +12‎ →‎How do ATVs and VSFs fit into this plan? Tag: Visual edit
• curprev 16:0916:09, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 39,214 bytes +192‎ →‎2.) Initial community outreach Tag: Visual edit
• curprev 15:5215:52, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 39,022 bytes +64‎ →‎2.) Initial community outreach Tag: Visual edit
• curprev 15:4815:48, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 38,958 bytes +246‎ →‎Comment: All this talk of NET getting downshifted to ATVs for not getting hours... Tag: Visual edit
• curprev 15:3915:39, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 38,712 bytes +1,772‎ →‎Comment: All this talk of NET getting downshifted to ATVs for not getting hours... Tag: Visual edit
• curprev 15:2115:21, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 36,940 bytes +975‎ →‎Comment: All this talk of NET getting downshifted to ATVs for not getting hours... Tag: Visual edit
• curprev 15:1215:12, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 35,965 bytes +1,063‎ →‎Q: So are we going to maintain our present team structure for some extended time period? Tag: Visual edit
• curprev 15:0515:05, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 34,902 bytes +34‎ →‎Comment: I am struck by the generalizations about teams in this presentation... Tag: Visual edit
• curprev 15:0315:03, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 34,868 bytes +163‎ →‎Comment: I am struck by the generalizations about teams in this presentation... Tag: Visual edit
• curprev 15:0115:01, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 34,705 bytes +1,154‎ →‎Q: How does this model overlap with powerline and other non-earthquake deployments? Tag: Visual edit
• curprev 14:4114:41, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 33,551 bytes +95‎ →‎Q: How does this model overlap with powerline and other non-earthquake deployments? Tag: Visual edit
• curprev 14:4014:40, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 33,456 bytes +3,006‎ →‎Q&A from NET Volunteers Tag: Visual edit
• curprev 13:4713:47, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 30,450 bytes +308‎ →‎Q: There are no other active NETs within a reasonable walking distance of my house. How could I set up a NERF? Tag: Visual edit
• curprev 13:4513:45, 15 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 30,142 bytes +1,163‎ →‎How do ATVs and VSFs fit into this plan? Tag: Visual edit

13 November 2023

• curprev 22:1422:14, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,979 bytes +73‎ →‎1.) Centralized deployments and self deployments Tag: Visual edit
• curprev 22:0322:03, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,906 bytes +137‎ →‎Climate change Tag: Visual edit
• curprev 21:5921:59, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,769 bytes +153‎ →‎Climate change
• curprev 21:5821:58, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,616 bytes +565‎ →‎Summary Tag: Visual edit
• curprev 21:4721:47, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,051 bytes −7‎ No edit summary Tag: Visual edit
• curprev 21:4521:45, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 28,058 bytes +401‎ →‎How do ATVs and VSFs fit into this plan? Tag: Visual edit
• curprev 21:4021:40, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 27,657 bytes +3,475‎ →‎4.) Capacity Planning Tag: Visual edit
• curprev 21:1521:15, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 24,182 bytes +1,626‎ →‎3.) Conduct a Capacity Assessment of the neighborhood Tag: Visual edit
• curprev 20:5620:56, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 22,556 bytes +129‎ →‎1.) Team decides on a Team Service Area Tag: Visual edit
• curprev 20:5520:55, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 22,427 bytes +3,849‎ →‎1.) Team decides on a Team Service Area Tag: Visual edit
• curprev 20:3120:31, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 18,578 bytes +3,823‎ →‎Training Centers Tag: Visual edit
• curprev 17:3317:33, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 14,755 bytes +12‎ →‎Centralized Deployments Tag: Visual edit
• curprev 17:3217:32, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 14,743 bytes +1,969‎ →‎Training Centers Tag: Visual edit
• curprev 16:2916:29, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 12,774 bytes +1,256‎ →‎A few of the NET program's known issues Tag: Visual edit
• curprev 16:1516:15, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 11,518 bytes +3,319‎ →‎2.) Training and socializing Tag: Visual edit
• curprev 15:1515:15, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 8,199 bytes 0‎ No edit summary Tag: Visual edit
• curprev 15:1515:15, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 8,199 bytes 0‎ →‎Notes and References Tag: Visual edit
• curprev 15:1315:13, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 8,199 bytes +1,766‎ →‎2.) Training and socializing Tag: Visual edit
• curprev 13:3913:39, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 6,433 bytes +1,108‎ →‎Centralized deployments and self deployments Tag: Visual edit
• curprev 13:1713:17, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 5,325 bytes +70‎ →‎Centralized Deployments Tag: Visual edit
• curprev 13:1413:14, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 5,255 bytes +903‎ →‎We need to revisit the purpose of a NET team Tag: Visual edit
• curprev 11:5511:55, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 4,352 bytes +675‎ →‎Forces Driving Realignment Tag: Visual edit
• curprev 11:4911:49, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 3,677 bytes +1,324‎ No edit summary Tag: Visual edit
• curprev 11:3811:38, 13 November 2023‎ Net@portlandoregon.gov talk contribs‎ m 2,353 bytes +465‎ →‎Climate change Tag: Visual edit

11 November 2023

• curprev 09:1009:10, 11 November 2023‎ Net@portlandoregon.gov talk contribs‎ 1,888 bytes +1,888‎ Created page with "This page presents a proposal for realigning elements of PBEM's volunteer programming (which includes NETs, BEECN, and ATVs). '''The objectives of these changes would be to:''' * Address the fall-off of meeting attendance at routine NET Team Meetings; * Prepare PBEM volunteer programming to meet and weather through the many changes coming to the City of Portland's government structure and the structural changes taking place at PBEM; * Ensure programming is structured lo..."