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