My WebLink
|
Help
|
About
|
Sign Out
Home
2009-09-22_PWETC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Minutes
>
200x
>
2009
>
2009-09-22_PWETC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/22/2010 12:10:22 PM
Creation date
3/22/2010 12:10:07 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
9/22/2009
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
11
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
Scott Anderson stated in order to avoid claims of violation of the open meeting <br />law, Section 4 of the policy states try to make communication one way. An <br />example would be if a committee member had questions or comments about the <br />reading material Duane Schwartz provided to the Public Works Environment and <br />Transportation committee it is encouraged that communication should be directed <br />only to Duane Schwartz. Then Duane Schwartz could communicate back to the <br />rest of the committee. <br />Member Vanderwall asked to clarify that Scott Anderson was not presenting this <br />information to get an opinion. His presentation is more for instructions on <br />communications. Scott Anderson answered this is correct and that he could also <br />answer any questions about the policy. <br />Scott Anderson stated Section 5 of the policy states communications during a <br />council meeting should be done orally, not electronically. Member Vanderwall <br />asked if this means then that committee members should not look at incoming <br />electronic messages during a meeting. Scott Anderson answered that his <br />interpretation is if there is a full meeting with many people and someone sends an <br />electronic communication with their opinion, the committee member doesn't <br />know who it is from until it is opened. It is not wrong to open the communication <br />but the message that is being conveyed by communicating this way is that the <br />person does not want the committee member to communicate back during the <br />meeting. <br />Scott Anderson stated Section 6 is the part of the policy which describes the Open <br />Meeting law. The Open Meeting law states business should be conducted in <br />public. This gives the public a chance to give their opinion and makes council or <br />committee members accountable for the decisions they are making because it is <br />public. Discussions between council or committee members can happen outside <br />of a public meeting however no decisions can be made during the discussion. If a <br />discussion occurs outside of a public meeting between council or committee <br />members and City business is discussed, that discussion needs to be mentioned in <br />a public meeting so the public is aware the discussion took place. <br />Scott Anderson mentioned Serial Meetings which can occur with electronic <br />communication. Serial Meetings are when one person goes to someone else to <br />talk about something and then goes on to talk to another person and then another <br />person and then a decision is made without the discussion being made public. <br />Serial Meetings can be conducted by the same person or by several people. <br />Member Stenlund asked how many people are needed to make a public meeting. <br />Scott Anderson answered it would be a quorum or more of the body where <br />business is discussed or conducted or information regarding business is received. <br />A chance social meeting at for example a party is not a meeting unless public <br />business is discussed. <br />Page 5 of 11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.