My WebLink
|
Help
|
About
|
Sign Out
Home
2016_0224 HRC Packet
Roseville
>
Commissions, Watershed District and HRA
>
Human Rights Commission
>
Agendas and Packets
>
2016 Agendas and packets
>
2016_0224 HRC Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/13/2016 3:10:33 PM
Creation date
9/13/2016 3:10:30 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Human Rights Commission
Commission/Committee - Document Type
Coversheet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
35
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 City Council Meeting <br />Monday, February 8, 2016 <br />Page 22 <br />1 <br />2Mayor Roe advised that, of the 2016 priority projects for the CEC, he wasn’t per- <br />3sonally sure if those items aligned with the community’s vision. Mayor Roe stat- <br />4ed that his personal expectation specifically with starting community visioning <br />5work prior to the 2017 comprehensive plan, one thing talked about with the CEC <br />6last year and the different categories and spectrum of engagement (e.g. identifying <br />7stakeholders and tools for each type of process). Mayor Roe opined that was key <br />8in looking at the comprehensive plan update. However, with the current Imagine <br />9Roseville 2025 document being over ten years old and some of its provisions out- <br />10of-date based on decisions before the city now, Mayor Roe suggested it may be <br />11time to recommend a process to update – not recreate – that community vision as <br />12a starting point to initiate the comprehensive plan update. Mayor Roe opined that <br />13it would be his goal to have that update, not an extensive document difficult to <br />14use, but as a reference document at which time that related infrastructure work <br />15could be tied into other engagement processes (e.g. SE Roseville) and without <br />16giving the CEC too much that would prove difficult for it to accomplish in a time- <br />17ly manner. <br />18 <br />19As a member of the Imagine Roseville 2025 Subcommittee, Councilmember <br />20Willmus stated he found the organization of that group overall quite effective and <br />21broad, with a number of satellite groups reporting back to the broader steering <br />22committee. Councilmember Willmus expressed his interest in retaining that mod- <br />23el, but questioned it that effort should be put on the CEC. <br />24 <br />25Mayor Roe clarified that it was not his intent that the CEC run the process, but <br />26simply recommend a process back to the City Council. <br />27 <br />28Councilmember Willmus suggested the CEC could recommend utilizing the past <br />29process and ways to tweak it; and expressed appreciation to Mayor Roe for clari- <br />30fying his intent. Councilmember Willmus stated that it was his intent to look to <br />31the CEC to recommend models used in the past, their areas of success, areas need- <br />32ing revision and ideas to do so; but clarified he was not intending that the CEC <br />33become that steering committee nor that he had any intent of mixing those two <br />34contexts. <br />35 <br />36Mayor Roe agreed with the comments of Councilmember Willmus. <br />37 <br />38Councilmember Laliberte also agreed with those comments; clarifying that the <br />39City Council was not asking the CEC to recreate the wheel if good processes were <br />40already in place or simply needed tweaking, she would consider that first before <br />41working from scratch. Councilmember Laliberte spoke to learning lessons from <br />42those past processes and applicable suggestions for employing those strategies in <br />43some but not all cases, and why not; and systematically engaging processes in one <br />44place but not all. <br />45 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.