My WebLink
|
Help
|
About
|
Sign Out
Home
2013_07_10_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2013
>
2013_07_10_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:28:57 AM
Creation date
10/21/2014 11:28:56 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
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, July 10, 2013 <br />Page 3 <br />Member Daire suggested that Section B.5. (Summary Submission) be revised to include <br />95 <br />a requirement that a list of names and associated addresses be part of that submission, <br />96 <br />provided via a sign-up sheet at the open house to ensure comments from those with <br />97 <br />specific concerns within the notification area would be heard. <br />98 <br />Chair Gisselquist closed the Public Hearing at 7:02 p.m.; no one spoke for or against. <br />99 <br />MOTION <br />100 <br />Member Boguszewski moved, seconded by Member Murphy to recommend to the <br />101 <br />City Council APPROVAL of the TEXT AMENDMENT to Section 1011.02, <br />102 <br />Procedures, of the Subdivisions Chapter of Roseville City Code, as provided in <br />103 <br />Section 5 of the staff report dated July 10, 2013; <br /> amended as follows: <br />104 <br /> <br /> Section B.2 (Timing) to read “…not less than fifteen (15) or more than forty-five <br />105 <br />(45) days…” <br />106 <br />Member Boguszewski spoke in support of a list and associated addresses as <br />107 <br />recommended by Member Daire; however, he recognized that those attending could not <br />108 <br />be forced to sign-up. If the Commission chose to include that recommendation as an <br />109 <br />amendment to the motion, Member Boguszewski suggested that the submittal summary <br />110 <br />include a “voluntary list of names and associated addresses.” <br />111 <br />Member Murphy stated that he initially thought that sounded like a good idea; however, in <br />112 <br />his review of the last sentence in that section, citizens were welcome to submit their own <br />113 <br />summary of the meeting highlighting concerns/issues and any mitigations/resolutions. <br />114 <br />Member Murphy advised that his concern was whether the open house summary report <br />115 <br />was an accurate portrayal of the comments versus the perception of the host of the open <br />116 <br />house; and opined that the last sentence encouraging citizen submittal would accomplish <br />117 <br />the same goal as recommended by Member Daire, while allowing them to remain <br />118 <br />unedited by the host. <br />119 <br />Member Daire opined that a citizen would be able under any circumstances to reflect his <br />120 <br />views and understanding of a particular situation; however, by requiring the developer to <br />121 <br />hold the open house and be responsible to report the results and to document responses <br />122 <br />should remain a responsibility of the developer or open house host. Member Daire <br />123 <br />questioned how the City could guarantee that a citizen could submit a dissenting view of <br />124 <br />the meeting summary if they hadn’t seen the summary; and opined that his <br />125 <br />understanding of the City Council’s intent was to expose the neighborhood to the nature <br />126 <br />of the development prior to any Public Hearing in advance and prior to their notice by <br />127 <br />staff of the Public Hearing for initial review of the preliminary plat at the Planning <br />128 <br />Commission level. Member Daire further opined that this would ensure citizens weren’t <br />129 <br />caught broadsided by a development proposal without sufficient research and reaction <br />130 <br />time for a response with their particular concerns; and thereby adding another layer of <br />131 <br />public information to field reactions prior to the formal Public Hearing; and allowing the <br />132 <br />developer and neighborhood to hash out any differences that may exist. Member Daire <br />133 <br />referenced the recent Dale Street Project informational meetings hosted by the City’s <br />134 <br />Housing & Redevelopment Authority (HRA) as an wonderful example that demonstrated <br />135 <br />how much can be gained by sharing information transparently prior to formal action and <br />136 <br />allowing a developer to adjust his proposal to provide more confidence to the <br />137 <br />neighborhood that their concerns are being listed to and/or mitigated. When suggesting <br />138 <br />that names and addressed of those attending should be included as part of the submittal, <br />139 <br />Member Daire advised that his intent was provide proof that the developer had notified <br />140 <br />the appropriate stakeholders, but also to alert the Planning Commission of any potential <br />141 <br />difficulties that may arise before or as part of the Public Hearing. <br />142 <br />Mr. Paschke advised that the City Council was directing the developer to provide staff <br />143 <br />with the summary report of any issues/concerns, not necessarily specific persons, also <br />144 <br />allowing staff and ultimately the Commission and City Council to be cognizant of any <br />145 <br />issues that may have been inadvertently missed or not addressed previously. Mr. <br />146 <br />Paschke noted that this didn’t necessitate having names or addresses; even though the <br />147 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.