My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSA - SUNSHINE ORDINANCE
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2012
>
09/17/2012
>
WSA - SUNSHINE ORDINANCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/1/2012 1:25:41 PM
Creation date
9/13/2012 5:31:10 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
City Manager's Office
Item #
WSA
Date
9/17/2012
Destruction Year
2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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
Sunshine Ordinance <br />September 17, 2012 <br />Page 3 <br />Community Meetings Should Occur Early and Not Delay Development Projects <br />In order to ensure that the community outreach does not otherwise delay the development <br />process, the community meeting must be conducted within about three weeks after the City <br />receives the development application. The recommended ordinance sets forth timeframes <br />to make sure this happens. <br />Bilingual Public Notice Should Be Provided, Be Sent to Both Property Owners and <br />Residents <br />The recommended ordinance requires a 10-day public notice be provided by the applicant <br />prior to the community meeting. This notice would be sent to both property owners and <br />residents within a 500 foot radius of the project site, and be provided in both English and <br />Spanish. The recommended ordinance also requires that the notice be published in a <br />newspaper of general circulation, and be posted on the project site. The City's current <br />informal practice for community meetings relies on notifying the community by working with <br />the nearby neighborhood association leaders, rather than sending formal mailed notices. <br />And to be consistent staff recommends that the City include both property owners and <br />residents in all other notices the City sends concerning development projects. This would <br />have a fiscal impact to the City estimated at $8,500 annually. It is further estimated that <br />these notice requirements would add $700 in costs to the average applicant. <br />Communitv Meetings Should Be Convenient <br />The recommended ordinance provides that the community meeting be conducted at times <br />and locations that are convenient for community members. Early evenings or Saturdays are <br />preferable, though adjustments are acceptable if they better serve the community members <br />who are planning to attend. The recommended ordinance also provides that the community <br />meetings take place within one mile of the project site, or at the closet City facility. <br />Community Meetings Should Provide Translation Services When Requested <br />The recommended ordinance provides that an applicant make translation services available <br />should it receive a request prior to the meeting. Based on City experience, and assuming a <br />two-hour meeting, it is estimated that this requirement will cost an applicant $200 when <br />translation services are necessary. <br />Written Summary of Community Meetings To Be Part of the Public Record <br />The recommended ordinance requires an applicant to provide the City with a summary of <br />the community meeting. The meeting summary would become part of the public record <br />WSA-3
The URL can be used to link to this page
Your browser does not support the video tag.