My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Upper Gunnison River Water Conservancy District Regular Board Meeting Minutes (5)
CWCB
>
Water Supply Protection
>
DayForward
>
3001-4000
>
Upper Gunnison River Water Conservancy District Regular Board Meeting Minutes (5)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/17/2010 2:42:00 PM
Creation date
6/15/2010 12:52:54 PM
Metadata
Fields
Template:
Water Supply Protection
Description
Gunnison Meetings, Minutes, Supporting Documents
State
CO
Basin
Gunnison
Water Division
4
Date
2/25/2002
Author
Upper Gunnison River Water Conservancy District, Bob Drexel, Gregory N. Peterson
Title
Upper Gunnison River Water Conservancy District Regular Board Meeting Minutes
Water Supply Pro - Doc Type
Minutes
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).
Show annotations
View images
View plain text
received four more sets of comments on the Plan. She said that the basic input has <br />been that the plan is not a balanced evaluation, that some measures are evaluated in <br />detail and others are not, which makes it hard to compare them, that the plan needs lots <br />of work, and is not detailed enough to make decisions. Ramon Reed suggested <br />focusing on the primary goal first, then progressing to the others. She suggested that <br />the board discuss process tonight, rather than discussing the comments specifically. <br />She recommended that the board hold a work session on a Saturday in order to have <br />adequate time to discuss the policy and procedural issues that have been raised. <br />After discussing scheduling concerns, the consensus of the board was to meet on <br />Thursday, March 14, from 4:30 p.m. to 9:00 p.m. <br />Dale Irby said that the Stockgrowers appreciate the board's efforts thus far, and support <br />the District's efforts to provide protection from downstream senior calls. <br />5. BOARD POLICY REGARDING ELECTRONIC MAIL AND MEETING <br />RECORDINGS <br />The board discussed the manager's February 13, 2002 memorandum regarding <br />administrative policy on electronic mail and board meeting recordings. <br />Steve Glazer asked if email can be protected as confidential, John McClow said yes. <br />He suggested adding "certain communications by electronic mail may be designated as <br />confidential" to the board's previously- adopted policy on email communication, so that it <br />reads: "Electronic mail received or transmitted through the electronic mail <br />communications system of the District may be considered "public records" as defined in <br />Section 24 -72 -202 C.R.S. and may be subject to monitoring at any time. Electronic mail <br />received or transmitted through the electronic mail communications system of the <br />District may be open to public inspection as provided in Section 24 -72 -203 C.R.S. <br />Certain communications by electronic mail may be designated as confidential." <br />Bill Trampe moved and Diane Lothamer seconded to adopt the following <br />statement as board policy regarding electronic mail: "Electronic mail received or <br />transmitted through the electronic mail communications system of the District <br />may be considered "public records" as defined in Section 24 -72 -202 C.R.S. and <br />may be subject to monitoring at any time. Electronic mail received or transmitted <br />through the electronic mail communications system of the District may be open <br />to public inspection as provided in Section 24 -72 -203 C.R.S. Certain <br />communications by electronic mail may be designated as confidential." <br />The motion carried. <br />Board consensus was that when necessary due to time constraints, that confidential <br />documents may be sent by email. <br />
The URL can be used to link to this page
Your browser does not support the video tag.