While we understand the reasons for the mayoral veto of adding an additional flag to the flag poles, we do think that the council does need to address some of the concerns brought up at May 20’s meeting.
Especially on determining the length of certain flags flying in months that have more than one flag being flown and coming up with a schedule, especially in a month where two or more are being flown.
This is the city’s flagpole to represent groups in this community, and the case in front of the council was the first time a flag was brought forward by a council member. While it didn’t get the resolution council per son Mark Andresen expected at the June 3 meeting, with two council members voting to keep the veto, it sets clear that the council will be addressing this policy again later this year and determining if there are any other flags that need to be added to the flagpoles in the next calendar year.
Clearing out some of the gray areas still in the flag policy, especially later this winter and determining if there are any additional that have been missed like the Jewish American History Month flag that represents members of Mount Vernon would be beneficial.
We disagree that the flagpole has been a waste of taxpayer money. The trees that once sat at that space were posing issues to the foundation of city council building and needed to be addressed, and the flag poles and design of that space is aesthetically pleasing, thanks to the work of city crews. Groups being recognized and supported by their local government does not diminish the representation of others in the community.