Lakewood Flag Flap Continues, As Predicted

Last June, this blog reported the controversy surrounding the Lakewood flag poles thusly:

V. David Sartin of The Cleveland Plain Dealer reports that Mayor Madeline Cain of suburban Lakewood ordered workers to install a new flagpole outside City Hall to avoid flying a gay pride flag below Old Glory. The City Council had agreed earlier to fly a gay banner to recognize Lakewood's large homosexual community. Prior to the mayor's edict, it was expected that the banner would fly on the same pole as the US flag along with a banner commemorating American prisoners of war.

The gay pride/two flagpole controversy has sparked a local firestorm. One resident, Jerry Murphy, offered the following:

"Now that you have that rag on a stick up there, you open up a door to all the other strange groups, like the Nazis . . . ."

Mr. Murphy's comment is quite true in that neither the mayor nor the City Council established criteria for who may hoist flags nor which flags are acceptable.

This whole story is disturbing. The Lakewood City Council and Mayor created the problem and it looks like it's going to grow in intensity. They should have adopted a policy that specified only the US flag and the Ohio flag are permitted to be flown in front of City Hall. Instead, they decided to use public property to advertise for special interests, this time, the homosexuals, next time, some other group. The problem is not going to go away.

When the public elects boneheads to office, there should be no surprise when everything turns into crap.

Since that time, a new mayor and City Council have been elected in Lakewood. Urged by Councilman Ryan Patrick Demro, a resolution was passed calling for Mayor Thomas George to take down the pole.

Demro proposed putting the flagpole at the city's refuse plant at 12920 Berea Road. But he later amended that to allow the mayor to decide where to intall [sic] the pole. The reinstalled pole can fly only the American flag, according to council's resolution.

Presumably, this issue should now be resolved. I suspect there'll be more to report in the future.