My WebLink
|
Help
|
About
|
Sign Out
Home
Search
01/07/2008 Council Minutes
LinoLakes
>
City Council
>
City Council Meeting Minutes
>
2008
>
01/07/2008 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/13/2015 4:43:05 PM
Creation date
2/12/2015 2:28:50 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Minutes
Meeting Date
01/07/2008
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 January 7, 2008 <br />APPROVED <br />270 The Citizens Task Force To Review Charter Provisions Pertaining to Local <br />271 Improvements and, as a result, conveyed a charter amendment proposal to the Charter <br />272 Commission. The Charter Commission elected to draft a substitute amendment which <br />273 the council has officially received. The council currently has two charter amendments <br />274 before them and the state statutes establish options for action. The council may send one <br />275 of the amendments to a ballot (special or general election). The council could also <br />276 consider approving an amendment by unanimous affirmative vote (this option would <br />277 apply to the substitute amendment only). Key days for placement on the ballot were <br />278 reviewed. <br />279 <br />280 Administrator Heitke reviewed a proposed general schedule that would allow the council <br />281 to review the substitute charter amendment, with adequate time to pursue all options <br />282 including the lengthiest option of proposing a new amendment that would again require <br />283 charter commission review. <br />284 <br />285 Community Development Director Grochala explained that the major difference with the <br />286 charter proposal is that the process for neighborhood involvement is cumbersome. A <br />287 feasibility study is done proposing possible improvements, elements are broken down <br />288 including assessments, residents get that information and make choices for <br />289 improvements, and whatever projects get the most votes would dictate what would be <br />290 done. There are concerns about how design can be accomplished, how you can separate <br />•291 elements, etc. <br />292 <br />293 Administrator Heitke is recommending a technical review of the charter commission <br />294 proposal. <br />295 <br />296 The council concurred with the proposal to proceed with a technical review and will <br />297 expect a report on the February work session agenda. <br />298 <br />299 Professional Services RFP's — Administrator Heitke noted the council has discussed <br />300 seeking proposals for on going professional services, including legal services. The matter <br />301 was purposefully held off for various noted reasons including projects underway and the <br />302 need for continuity. He is proposing now, however, that an RFP process could now <br />303 begin. He is not recommending looking at an RFP for all services at one time because it <br />304 can be a time consuming process for both staff and council. <br />305 <br />306 There was discussion about legal services, past and present. <br />307 <br />308 The council concurred on releasing an RFP for legal services. As noted in the previous <br />309 discussion regarding annual appointments that include designation of certain service <br />310 providers, it was confirmed that staff under direction to provide options to look at options <br />311 for labor and fiscal services. <br />312 <br />•313 Data Request Policy — City Clerk Bartell explained that the council has discussed the <br />314 establishment of a formal communication policy as it relates to data requests from council <br />
The URL can be used to link to this page
Your browser does not support the video tag.