My WebLink
|
Help
|
About
|
Sign Out
Home
2016-07-13_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-07-13_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/11/2016 4:10:15 PM
Creation date
7/11/2016 4:10:06 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Agenda/Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
37
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Regular Planning Commission Meeting <br />Minutes – Wednesday, June 1, 2016 <br />Page 5 <br />Engagement Commission (CEC) to define the public engagement and participation <br />191 <br />process, above and beyond formal public hearings. Mr. Lloyd noted that part of these <br />192 <br />preliminary discussions would involve the extent of public engagement at the front end, <br />193 <br />including the nature of desired changes in the comprehensive plan process and whether <br />194 <br />the current goals are still relevant, and to address those goals already achieved and no <br />195 <br />long needed in the comprehensive plan’s guidance. <br />196 <br />Member Daire asked if, upon examination of those policies and whether or not current <br />197 <br />goals had been achieved or not, would that dictate a complete redo versus an update. <br />198 <br />Mr. Lloyd advised that would depend on the depth to which that conversation was <br />199 <br />directed. On one hand, Mr. Lloyd noted there was the larger version of an update versus <br />200 <br />a rewrite scenario; evaluation of what indicated a more open-ended update versus a <br />201 <br />complete rewrite; and determining whether those goals still mattered to the community or <br />202 <br />whether or not some of those goals had been achieved already. <br />203 <br />In his reading of the proposal, Member Daire stated the need to recognize the <br />204 <br />community’s demographic changes, both ethnically and from an age standpoint. Since <br />205 <br />those appear to be new elements, Member Daire noted the need to seek input on those <br />206 <br />new elements; and asked if that meant determining if those elements complied with the <br />207 <br />2008 comprehensive plan or if the plan needed revising to accommodate more diversity. <br />208 <br />Member Daire opined it sounded like a specific outreach for CEC involvement to address <br />209 <br />those growing ethnic segments in the community, which in turn to him sounded like a <br />210 <br />rerun of the community visioning process incorporating that input on ethnicity and age <br />211 <br />demographics, allowing for modification of those previous comprehensive plan <br />212 <br />statements to be more topical, inclusive and respond to citizens in a way that’s positive <br />213 <br />and proactive as well. In that case, Member Daire stated that sounded to him like more <br />214 <br />than an update. <br />215 <br />Mr. Lloyd stated that an update could simply engage those demographic groups newer to <br />216 <br />the community, or more represented than at the last process, with expectations that any <br />217 <br />update included those voices. Mr. Lloyd clarified that any update involved more than <br />218 <br />simply numeric’s to provide a baseline for the Metropolitan Council, but beyond that it <br />219 <br />was a matter of scale. Mr. Lloyd reiterated that the draft RFQ and RFP included in <br />220 <br />tonight’s meeting materials were not intended as the right scale, just a direction perceived <br />221 <br />by staff to-date, and intended as an update, not a rewrite or for a purely numerical effort. <br />222 <br />Mr. Lloyd noted that this is all part of that conversation: how fundamental do we want to <br />223 <br />get in our evaluation of community goals. <br />224 <br />Member Daire stated he didn’t have a personal sense for what kind of demographic <br />225 <br />changes and scale for them, beyond the 2010 census and forecasts by an arm of the <br />226 <br />Metropolitan Council and/or State of MN. Specific to the ethnic composition of Roseville, <br />227 <br />Member Daire opined, if there were no significant changes however defined, perhaps it <br />228 <br />was less critical to spend a lot of time reaching out. However, if there were a lot of <br />229 <br />significant increases in the Karen or Somali communities as indicated by Member <br />230 <br />Boguszewski’s written comments, Member Daire opined that it seemed just including that <br />231 <br />outreach process was a major undertaking even beyond providing that input in the <br />232 <br />comprehensive plan update and its various elements. <br />233 <br />Ms. Collins further clarified Mr. Lloyd’s interpretation of an “update.” Ms. Collins noted <br />234 <br />that this went beyond updating statistics of making minor amendments, but involved the <br />235 <br />potential rewrite of entire sections in the existing comprehensive plan. For example, Ms. <br />236 <br />Collins noted that the current plan referenced the City’s Housing & Redevelopment <br />237 <br />Authority (HRA), which no longer existed; with that entire section reworked for the current <br />238 <br />Roseville Economic Development Authority (REDA) instead. Ms. Collins noted that each <br />239 <br />section would require a review and receive group input for any changes, whether <br />240 <br />rewriting, tweaking or leaving as is. However, Ms. Collins further clarified that the <br />241 <br />question was how much was done ahead of time and how much was done after a team <br />242 <br />(e.g. consultant(s), community stakeholders, or staff) was established. Ms. Collins stated <br />243 <br />there was no doubt that each section would need to be reviewed; with some design and <br />244 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.