My WebLink
|
Help
|
About
|
Sign Out
PC 062707
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2000-2009
>
2007
>
PC 062707
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2017 3:30:42 PM
Creation date
8/17/2007 10:09:40 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
6/27/2007
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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).
Show annotations
View images
View plain text
A recess was called at 10:38 p.m. <br /> <br />Chairperson Fox reconvened the meeting at 10:48 p.m. <br /> <br />Mr. Roush reiterated the referendum procedure for the benefit of the public speakers who <br />requested clarification. He noted that there was a 30-day window from the time that an <br />ordinance was adopted. He advised that most Development Agreements, including the <br />Agreement for this application, had language that provided that once the entitlements <br />were vested, then a subsequent act by City Council or the voters to disenfranchise those <br />entitlements would be considered null and void. He noted that this Agreement had a <br />10-year shelf life, and in response to Chairperson Fox’s question regarding whether that <br />could be extended by the Planning Commission, he confirmed that it could be possible to <br />make it a less lengthy process; however, the developer must be reasonably able to build <br />out the project. <br /> <br />In response to an inquiry by Chairperson Fox regarding the process to be followed by the <br />Planning Commission, Ms. Decker replied that was delineated in the staff report. <br /> <br />Mr. Roush advised that if the Planning Commission were to certify the EIR as being <br />legally adequate, it must determine whether the EIR has reasonably and thoroughly <br />evaluated, has disclosed environmental impacts, has identified mitigation measures, and <br />has adequately addressed comments made on the Draft EIR, and whether the proposed <br />findings and determinations were supported by substantial evidence in the record. If <br />those findings could be made, the Commission may certify the EIR and move ahead to <br />the PUD development plan and Development Agreement. If those findings cannot be <br />made, he believed it would be wise and helpful to the City Council to identify in what <br />respects the EIR was not adequate and then take a vote on that action. Normally, if an <br />EIR is not certified, there was no reason to move ahead with the PUD plan and <br />Development Agreement. In that case, he recommended that the Planning Commission <br />also make a recommendation to the City Council concerning the PUD development plan <br />and the Development Agreement, so it would have the benefit of the Commission’s <br />thoughts in the event it wished to certify the EIR, and whether the plan and Development <br />Agreement should be approved. <br /> <br />Commissioner Olson expressed concern that when he received the package, an updated <br />development was not included. He did not believe he was in the position to opine on the <br />Development Agreement or the conditions of approval because he would like to see some <br />additional conditions. He was also concerned about some language in the Development <br />Agreement. <br /> <br />Mr. Roush noted that he could choose to certify the CEQA documents as the first step, <br />and then approve the development plan either with the conditions or with different <br />conditions or recommend that the plan not be approved. <br /> <br />Commissioner O’Connor expressed disappointment that after the length of time that has <br />passed, some of the items of concern to the Commission had not been addressed in the <br />PLANNING COMMISSION MINUTES June 27, 2007 Page 23 of 28 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.