My WebLink
|
Help
|
About
|
Sign Out
Home
2014-11-05_PC_Agenda
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2014 Agendas
>
2014-11-05_PC_Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/22/2016 11:33:38 AM
Creation date
4/22/2016 11:33:33 AM
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.
/
20
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 CommissionMeeting <br />Minutes –Wednesday, October 8, 2014 <br />Page 6 <br />becoming a city-sponsored or mandated meeting that would be accommodated at the <br />247 <br />public hearing level before the Planning Commission or City Council. <br />248 <br />Member Boguszewski recognized the interest of some attending to simply attend and not <br />249 <br />provide a record of their names/addresses; however, in an effort not to weaken the <br />250 <br />process, he opined it was incumbent upon the holder of the open house to provide a <br />251 <br />sign-up sheet, while allowing those attending to choose to sign-in or not to do so <br />252 <br />depending on their preference. <br />253 <br />Under that scenario, Mr. Paschke advised that he would then include language that a <br />254 <br />sign-in sheet was “required” to be provided by the developer. <br />255 <br />Member Boguszewski opined that would be fine as long as an attendee was not required <br />256 <br />to sign up, but that a sign-up sheet be provided. <br />257 <br />Member Daire advised that he had no issues with the wording of Items B, C, or E, opining <br />258 <br />that they made the process more explicit.However, Member Daire advised that he <br />259 <br />agreed with Member Boguszewski that the developer should be “required” to have a sign- <br />260 <br />in sheet available, but not “requiring” those attending to sign in.Specific to the additional <br />261 <br />language requested by the Community Development Department (lines 60-62), Member <br />262 <br />Daire opined that it from his perspective it represented an extraordinary requirement, <br />263 <br />noting that the Planning Commission didn’t provide a summary of the public hearing to <br />264 <br />each one attending the meeting;and questioned why it should be mandated for a <br />265 <br />developer.Member Daire moved to strike that last provision as proposed. <br />266 <br />Member Cunningham disagreed with Member Daire, opining that the burden of proof <br />267 <br />should be the greatest for the developer or applicant, including any extra hoops deemed <br />268 <br />necessary or desired by the City and thus required as part of their approval process. <br />269 <br />Member Cunningham stated that as long as she had served on the Planning <br />270 <br />Commission, the biggest concern heard from citizens is that more citizen involvement be <br />271 <br />provided for and that advocacy for those voicesbe provided. Member Cunningham <br />272 <br />opined that she found this to be a minimum request of a developer; and respectfully <br />273 <br />disagreed with Member Daire. <br />274 <br />Mr. Lloyd noted that anyone attending anymeetings of any kind always had the liberty to <br />275 <br />summarize those meetings; and suggested that Item E (Summary) could be relocated to <br />276 <br />Item D (Invitations) as a separate paragraph as noted by including the language of lines <br />277 <br />34-37 of the invitation, alerting those invited and/or attending that a written summary will <br />278 <br />be sent to those requesting it as long as they provided their name and address; as well <br />279 <br />as opening up that opportunity to those attending to provide their own summary to staff if <br />280 <br />they found that thedeveloper’s summary didn’t capture the meeting, along with options <br />281 <br />for how they could follow-up and provide their comments to staff. <br />282 <br />Public Comment <br />283 <br />Gary Grefenberg, 91 Mid Oaks Lane <br />284 <br />Mr. Grefenberg advised that he was speaking as a representative of the newly-created <br />285 <br />City Council advisory Community Engagement Commission that had been reviewing <br />286 <br />ways to involve residents in decisions impacting them.Mr. Grefenberg opined that the <br />287 <br />report referenced in the staff recommendation provided a step forward.However, in his <br />288 <br />past attendance at open houses, Mr. Grefenberg opined that the summary report didn’t <br />289 <br />always fairly represent those residents attending, but on occasion reflected developer <br />290 <br />prejudices and had the potential for significant conflicts of interest if that summary report <br />291 <br />was the sole responsibility of the developer.Mr. Grefenberg further opined that the <br />292 <br />proposed mailing to all attending and clarifying that any resident attending could submit <br />293 <br />their own report was based on recommendations of the Community Engagement <br />294 <br />Commission to ensure resident involvement in decision-making. <br />295 <br />Mr. Grefenberg provided as a bench handout, attached hereto and made a part hereof, <br />296 <br />a comparison of the Community Engagement Commission draft proposal, and the <br />297 <br />Planning Commission staff’s proposal, expressing his appreciation that there was some <br />298 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.