My WebLink
|
Help
|
About
|
Sign Out
Home
Search
07-06-2010 Council Minutes
LinoLakes
>
City Council
>
City Council Meeting Minutes
>
2010
>
07-06-2010 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/7/2014 2:17:14 PM
Creation date
3/8/2013 11:07:06 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Minutes
Meeting Date
07/06/2010
Council Meeting Type
Work Session Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
8
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
CITY COUNCIL WORK SESSION July 6, 2010 <br /> APPROVED <br /> 271 related issue. Information received from an English Only group that was received by a <br /> 272 council member was shared with Mr. Tesch; some of the information may be helpful as <br /> 273 he prepares a resolution proposal. Council members noted they've had lots of feedback <br /> 274 on the proposal and anticipate receiving more as it goes forward. One council member <br /> 275 received a suggestion from a resident to look at Google Translator as a way that the city <br /> 276 could provide translation services at no cost. Another council member suggested that <br /> 277 providing such a service could open the city to liability in providing translation services. <br /> 278 <br /> 279 Mr. Tesch will work with Council Member Roeser on composing a resolution for <br /> 280 consideration. <br /> 281 <br /> 282 11. Joint Council and Charter Commission Meeting Agenda - Acting Administrator <br /> 283 Tesch noted that the council has been provided with a draft agenda(provided by the <br /> 284 commission)for the upcoming joint meeting with the charter commission. <br /> 285 <br /> 286 A council member asked why the question of paying the commission's outstanding legal <br /> 287 bill is on the agenda; hasn't that already been determined to be outside of what the <br /> 288 council can legally do? A member responded that it is perhaps on the agenda because <br /> 289 there are some charter commission members that may not have been involved in previous <br /> 290 discussions. The council confirmed that the amount of funding and what for is mandated <br /> 291 by state statute. The city can only authorize funding that is directly related to framing and <br /> 292 amending the city charter. <br /> 293 <br /> 294 The agenda item regarding a code of conduct was discussed briefly. The council <br /> 295 questioned if it the subject is a code of conduct for the council or the commission as that <br /> 296 isn't clearly stated. City Clerk Bartell clarified that the information in the meeting packet <br /> 297 is the code of conduct from the city code and the code of conduct approved as a policy by <br /> 298 the council. <br /> 299 <br /> 300 Regarding the tax cap amendment item, a council member suggested some concern about <br /> 301 having an unelected body putting forth a means to control the budget under the control of <br /> 302 the city's elected officials. <br /> 303 <br /> 304 Regarding road improvements,the council noted that is their topic of interest. They <br /> 305 would like to see where the commission is at on that subject and ask them to come up <br /> 306 with some suggestions to work forward. The city isn't taking care of the infrastructure in <br /> 307 place so the problem must be addressed. It would be optimum to have the charter <br /> 308 commission make recommendations, forward that to the council and then a change could <br /> 309 be accomplished with a council vote. The council discussed the charter amendment <br /> 310 process set forth by state law. <br /> 311 <br /> 312 REVIEW REGULAR AGENDA ITEMS <br /> 313 <br /> 314 There were no changes to the regular agenda. <br /> �.� 315 <br /> 316 <br /> 7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.