My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Minutes - 2006/07/24
MoundsView
>
Commissions
>
City Council
>
Minutes
>
2000-2009
>
2006
>
Minutes - 2006/07/24
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/6/2025 1:46:48 PM
Creation date
3/6/2025 1:46:48 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Minutes
MEETINGDATE
7/24/2006
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
29
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
Mounds View City Council July 24, 2006 <br />Regular Meeting Page 16 <br />Councilmember Thomas clarified that the intent is to follow the ordinance procedure, but not <br />requiring other things that are required with ordinances. She stated this is not an ordinance, but <br />they are trying to make it follow the process for ordinances. <br />Councilmember Flaherty stated that he agrees with Councilmember Gunn that the language is <br />difficult to understand. Mr. Thomas stated that in the recommendation of it being a ballot <br />question, it can be included in the request that Staff clarify. <br />Councilmember Gunn asked about the City newsletter and how it will be published 10 days <br />ahead when there are only 6 newsletters published. Councilmember Stigney suggested the <br />language of "city newsletter when feasible, or the City website." <br />Mr. Thomas stated Councilmember Stigney's recommendation is well within the intent of the <br />language. He stated the listing of the additional items is to encourage the use, but the City <br />newsletter is the required use. Mr. Thomas stated it is reasonable to request Staff take a careful <br />consideration of the paragraph when drafting the final draft. <br />Councilmember Stigney asked about the formulas in Subdivision 1, which states the rate shall <br />not exceed the lesser of the following formulas. He asked about the inflationary index and asked <br />if the word "formulas" should be removed. Mr. Thomas stated there are two formulas, the lesser <br />of 5%, or CPI plus 2%. <br />Councilmember Thomas stated that there are two formulas, and any time a percentage is being <br />figured, it is a formula. She stated it is either a percentage of the budget, or the CPI plus a <br />percentage. Councilmember Stigney suggested the language "CPI plus 2% or a cap of 5%" be <br />used. <br />Mr. Thomas stated that if there is a better way for the langue to make sense, the Charter <br />Commission is not opposed to it. He stated the overall attempt is to put together a very carefully <br />planned restriction so the Council cannot implement a greater amount without taking it to the <br />voters. <br />Mayor Marty stated his concern is that the CPI was 10%, would the limit will be crippling to the <br />City in inflationary times. He stated a special election would cost the City a fair amount. He <br />stated if the City needs more than 5%, it would cost a significant amount to approve. <br />Mr. Thomas stated the Charter Commission agrees with the sentiment, but if the City finds itself <br />in the position of needing more money, the Council needs to take it to the voters with a special <br />election. He stated they reviewed with Finance Director Beer the last 10 years and next 5 years, <br />and the 5% would have worked in the past and will work in the future. He stated if times are that <br />tough, he believes the voters must be involved. <br />Mr. Thomas explained that, not counting the cuts in LGA, the numbers would all have worked <br />and they would not have had to go to the voters for any of the budgets. He stated they <br />considered both historical and projected needs, and designed the Charter to meet the City's needs <br />
The URL can be used to link to this page
Your browser does not support the video tag.