My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2009_1207
Roseville
>
City Council
>
City Council Meeting Minutes
>
200x
>
2009
>
CC_Minutes_2009_1207
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/19/2010 1:00:00 PM
Creation date
1/19/2010 12:59:57 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
12/7/2009
Meeting Type
Regular
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).
View images
View plain text
Regular City Council Meeting <br />Monday, December 07, 2009 <br />Page 9 <br />intensive; but now she was hearing that the same numbers could be moved from <br />one column to another. Councilmember Pust suggested that, in an attempt to get <br />along, those numbers could have been provided as requested. <br />Councilmember Roe questioned if the budget expenditure summary was what <br />Councilmember Ihlan was seeking, or if she was seeking other documents detail- <br />ing all tax-supported items, and asked for clarification of her request. <br />Councilmember Ihlan clarified that her request was for a line item corresponding <br />to the proposed tax levy; which she had received for fee-supported programs, but <br />not for tax-supported items. Councilmember Ihlan asked, if the 2010 tax- <br />supported levy was essentially the same as 2009 except for a few line items, why <br />those specific line items could not be changed and spreadsheets run similar to <br />those on line for 2009. Councilmember Ihlan advised that what she and the pub- <br />lic were expected to do is look at 2009 numbers that were not the same on key is- <br />sues where staff was proposing increases, creating confusion for her and the pub- <br />lic on where those increases are coming from. Councilmember Ihlan opined that <br />her request was simple, and was all public information. Councilmember Ihlan <br />advised that she was not happy being forced to make a public data information re- <br />quest; and expressed disappointment that fellow Councilmembers would not sup- <br />port her request, suggesting it was simply a power play and reiterating her request <br />for their support for the benefit of her and the public, to achieve the. best budget <br />possible and proper funding for services. <br />Finance Director Miller provided clarification and advised that the public data in- <br />formation request of Councilmember Ihlan, under the direction of the City Attor- <br />ney, could not be fulfilled by staff since the information had yet to be created, and <br />the public data information was specific to items already in existence. Mr. Miller <br />advised that staff had provided the information that was available, but noted that <br />the 2010 lien item budgets had not yet been created; and noted that the process <br />normally took approximately one month to complete, specific to allocations <br />among the City's various programs and services. Mr. Miller advised that staff <br />was awaiting finality from the City Council, as part of the BFO process, to com- <br />plete that task, with emphasis on the program level, not detracting the focus at line <br />item detail. <br />Mayor Klausing quoted from the November 23, 2009 meeting minutes the City <br />Attorney opinion regarding and clarifying information requests based on informa- <br />tion not already in existence; and noted that staff was not making any attempt to <br />withhold information; and spoke in support of any City Councilmember or mem- <br />ber of the public requesting information that was in existence. Mayor Klausing <br />asked that Mr. Miller again review, as mentioned by Councilmember Pust, how <br />the programs correlated to the BFO process and line items. <br />
The URL can be used to link to this page
Your browser does not support the video tag.