My WebLink
|
Help
|
About
|
Sign Out
Home
2015-08-05_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2015
>
2015-08-05_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/16/2015 11:30:36 AM
Creation date
10/16/2015 11:30:33 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.
/
16
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, August 5, 2015 <br />Page 14 <br />appreciation for the good feedback and good ideas heard during tonight’s public <br />658 <br />comment, and the public process in general to facilitate this dialogue. Mr. Nelson stated <br />659 <br />the developer’s commitment to hold an open house as the Owasso School project <br />660 <br />proceeds, and clarified that it was not nor had it ever been their intent to skirt any open <br />661 <br />house discussion with neighbors. Mr. Nelson assured neighbors and the commission that <br />662 <br />they would follow-up with an open house for both projects in the very near future. <br />663 <br />Chair Boguszewski recognized that the developer was operating under current city code <br />664 <br />and not being required to hold an open house, and reiterated that the developer was not <br />665 <br />attempting to evade holding an open house. <br />666 <br />Mr. Nelson noted that, for a considerable time during the planning process, the developer <br />667 <br />didn’t even think there would be a need to plat the property for this project, other than <br />668 <br />through the administrative approval process. However, once it became evident that the <br />669 <br />road right-of-way and 1.5 acre overlap on 50’ of Lot 2 needed to be cleaned up on the <br />670 <br />title, Mr. Nelson advised this initiated this more formal process to clarify those issues. <br />671 <br />To further clarify for the benefit of the public, Chair Boguszewski noted that both he and <br />672 <br />Member Daire served on the Task Force previously referenced by Member Daire; and <br />673 <br />further noted that the Task Force was supported by Mr. Paschke and Mr. Bilotta of staff; <br />674 <br />with the general intent to look at the current process and triggers requiring notification of <br />675 <br />projects with the eye toward improving and probably enlarging the number of property <br />676 <br />owners and residents included in notices beyond that of today. Chair Boguszewski <br />677 <br />advised that over the last several years, efforts to improve good civic engagement and <br />678 <br />address resident issues with an apparent lack of transparency in the past had come forth <br />679 <br />based on common courtesy, that the current process needed modification. However, <br />680 <br />since nothing had yet been finalized or any recommendations formally presented to the <br />681 <br />City Council for formal action, Chair Boguszewski opined that it would be unfair in the <br />682 <br />middle of those discussions, to require a developer to meet those higher standards <br />683 <br />before they were adopted. <br />684 <br />Chair Boguszewski noted that it was prudent that the Roseville public be aware that the <br />685 <br />City desired to continue improving the process. <br />686 <br />Mr. Paschke noted, in this unique instance, the developer was not required to plat the <br />687 <br />property and they could have simply subdivided the property without any project. Mr. <br />688 <br />Paschke clarified that when talking about extending the notification process for projects <br />689 <br />requiring a formal review and approval process versus the normal administrative process <br />690 <br />as guided and zoned, it was not the intent to notify for each and every project coming <br />691 <br />forward unless it met certain triggers or thresholds. <br />692 <br />Member Daire noted a recent parking lot resurfacing project occurring near a citizen’s <br />693 <br />home and their questioning of why they were not notified of that occurring. Member Daire <br />694 <br />noted his surprise with that statement, and reiterated that it had made him sensitive to <br />695 <br />people needing to know what was going on around them. Member Daire clarified that he <br />696 <br />did not intend to suggest this developer was attempting in any way to avoid examination <br />697 <br />of their project. <br />698 <br />While recognizing no fault with the developer, and specific to the work of the Task Force, <br />699 <br />Member Cunningham asked that her colleagues bring this particular example to the Task <br />700 <br />Force as evidence of the need to modify current practices and processes. Member <br />701 <br />Cunningham noted the need for the developer to be aware of and respond to questions <br />702 <br />and concerns of residents before a public hearing at the Planning Commission level. <br />703 <br />Member Cunningham expressed appreciation to residents accepting that this property <br />704 <br />would be developed and no longer be a vacant lot. However, Member Cunningham <br />705 <br />expressed confidence in the developer and their efforts in performing their due diligence <br />706 <br />in meeting current requirements; and offered her support of the project moving forward. <br />707 <br />Member Stellmach noted that, since this property was zoned HDR, a much denser <br />708 <br />project could have been possible. Member Stellmach stated this represented a good <br />709 <br />project for the overall neighborhood, and offered his support for the proposal. <br />710 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.