My WebLink
|
Help
|
About
|
Sign Out
Home
2016-02-03_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2016
>
2016-02-03_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/11/2016 11:15:52 AM
Creation date
4/11/2016 11:15:50 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.
/
13
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, February 3, 2016 <br />Page 11 <br />Member Bull reiterated his initial concerns, but agreed with language as presented. <br />493 <br />Mr. Paschke noted that the language was similar to that used in the zoning code. <br />494 <br />Member Bull expressed appreciation for the detail included about submission <br />495 <br />requirements; and clarified that his concern was related to having it all encompassed in <br />496 <br />this ordinance; when attempts were made elsewhere to move things out of ordinance <br />497 <br />and into applications for staff to be able to modify as needed verses requirements to <br />498 <br />change ordinances or modify language repeatedly (e.g. line 226) <br />499 <br />Mr. Paschke noted there were two views: 1) that would be great to provide staff with that <br />500 <br />latitude and flexibility on the application and be able to determine whether or not certain <br />501 <br />things were worth having listed there. 2), Mr. Paschke noted that this is specific for <br />502 <br />unique developments versus typical applications, and therefore, he thought it would be <br />503 <br />better to retain it in the ordinance to encapsulate that special process and necessities <br />504 <br />rather than on the application form(s). Mr. Paschke stated that if found not working, <br />505 <br />which would be part of the initially testing, he would find it more applicable to be part of <br />506 <br />future code revisions; but if found to be occurring too frequently, the process could be <br />507 <br />changes accordingly. However, for the time-being, Mr. Paschke spoke in support of <br />508 <br />changes via ordinance. <br />509 <br />Chair Boguszewski noted (line 233) the separation of submittals and applications related <br />510 <br />to the open house, and asked if that was to provide staff flexibility to change that <br />511 <br />administratively or if there could be a way to change it so it was still listed as a guide in <br />512 <br />the template. <br />513 <br />Member Stellmach noted such as “the following and any additional items staff may feel <br />514 <br />appropriate.” <br />515 <br />Mr. Paschke cautioned revising that language, noting that it could be staff beyond that of <br />516 <br />the Community Development Department, such as the Engineer or Public Works <br />517 <br />Department, or even the Parks & Recreation Department as applicable. <br />518 <br />Mr. Gozola also noted another benefit of this change may be if and when a judge looked <br />519 <br />at this list, and in staff’s attempt to protect the city, once things were or were not <br />520 <br />included on the list on an application, or if the application itself changes and should not <br />521 <br />include the list for some reason, the process entered into a grey area in terms of <br />522 <br />whether or not an application can be deemed incomplete. Mr. Gozola noted that lines <br />523 <br />227-228 in the introductory language allowed for such adjustments. <br />524 <br />Chair Boguszewski recognized that logic. In lines 235-266, Chair Boguszewski noted <br />525 <br />that without the process for a majority vote of the City Council to change ordinance <br />526 <br />language, except with the language in line 227 allowing for waivers, such requirements <br />527 <br />could be selectively waived by staff. <br />528 <br />Member Murphy noted that in order to prevent such a potential staff waiver and to retain <br />529 <br />the reasonable list provided, there would be nothing wrong with having a City Council <br />530 <br />level discussion that may add to that list. While items can be waived, Member Murphy <br />531 <br />opined it would not prove terribly burdensome to add additional items if items were <br />532 <br />found to be missed or new technologies indicated them. Seeing that PUD’s are the <br />533 <br />exception to typical, straightforward land use issues, Member Murphy opined that the <br />534 <br />requirement to meet the exception list should be kept at a high level. <br />535 <br />Chair Boguszewski asked his colleagues if, given their nature, changes of that manner <br />536 <br />should be reviewed by discussion of the City Council, and therefore kept in the currently <br />537 <br />proposed language; with the consensus of the body being affirmative. <br />538 <br />Member Gitzen expressed concern related to cancellation language and whether it <br />539 <br />sufficiently addressed both pre-existing and new PUD’s. <br />540 <br />Mr. Paschke sought clarification that the concern was regarding pre-existing PUD’s <br />541 <br />seeking to be cancelled and supported by staff, and would there would be any problems. <br />542 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.