Post #507: Last night’s Town Council meeting

The 1/6/2019 meeting was largely uneventful.  In this post I summarize a handful of items from that meeting in not-quite-chronological order.

You can find the meeting materials on this page.  You can find my audio recording of the meeting (taken from the Town’s streaming of the meeting) at this Google Drive link.  My .xls “index file” to show you where to find items on the tape can be found at this Google Drive link.

For your reference, here’s the agenda:

2020 01 06 Town Council meeting agenda

 


A pig flew past the window, chasing after a lead balloon.

About two and a half minutes into the meeting, my wife got up and asked Town Council voluntarily to comply with both the Virginia Campaign Finance Disclosure Act (CFDA) and the Stand by Your Ad act.

The reception to this request was less than enthusiastic.

You can see my CFDA discussion in Post #340.  Currently, no campaign finance laws apply in Town of Vienna elections.  Anyone can give any amount of money to any Town of Vienna candidate.  There is no requirement that any such contribution be publicly reported.  And anyone may post ads trying to influence the outcome of the election without revealing who they are.

My wife is asking the Town to change this situation by voluntarily placing town  elections under the CFDA, as the Town of Herndon did earlier this decade.  They aren’t going to do that.  Not much I can do except to say, please remember this (and the Noah’s Ark meeting) the next time Town Council starts blathering about how much they favor transparency in government. 


Candidates for Mayor

Council members Colbert and Springsteen announced that they would be running for Mayor.  Colbert stressed her strong association with (and blessing from?) the current Mayor.  Springsteen emphasized both his long-standing service and his understanding of Vienna citizens’ desire to maintain “small town” Vienna.  You can hear their speeches starting around 1:01:00 (just over one hour) into my tape of the meeting.

Apparently it is Vienna tradition that anyone on Council who intends to run for Mayor should makes that announcement at the first meeting of the new year.  (I wasn’t aware of this but others assure me that’s the case.)  The inference — but clearly not a hard-and-fast rule — is that nobody else on Council is running for Mayor.

If that’s the full list of candidates, then from my myopic lens of reducing the size and extent of redevelopment, that gives me an obvious choice of Springsteen over Colbert.  This, notwithstanding the recent vote to commingle the MAC rewrite with the rewrite of all the zoning in Vienna, and to develop the ground rules for doing that in secret (Post #495).


Level of service standards for Maple

This one turned out to be a huge disappointment for me.

You can read my just-prior post for the background, but, briefly, the issue is whether to adopt some goal for reasonable traffic flow down Maple as part of the Town’s comprehensive plan. That goal would be expressed as a “level of service” on Maple, graded from A (free flow of traffic) to F (gridlock).  Fairfax County has a county-wide standard of no less than a “D” level of service, but accepts level “E” in some congested areas.  Currently, Maple Avenue as a whole appears to score as level “D”.

Why was I disappointed?  First, this appears to have been initiated by Town staff, not Town Council.  (Councilmen Noble, asked, in effect, “did we ask for this”?).  Second, apparently Town staff intend to use this in the narrowest possible way, by looking at the additional traffic from one development project at a time, and if that traffic pushes Maple Avenue below the acceptable level of service, requiring that project to adopt “mitigation measures” to maintain the level of service.  Third, Councilman Majdi brought up the issue of integrating such a standard into an overall redevelopment plan for Vienna, he got (what I heard) as a bunch of evasion and double-speak.  To me, at least, it was not at all clear how this fits into the overall rewrite of all the zoning in the Town of Vienna, if at all.

On that last one, I’ve seen that sort of purposeful ambiguity enough times to realize what that means.   Town staff aren’t going to do that, but they aren’t going to say that they aren’t going to do that.  So if there is any overall concept of “please do not develop Maple to the point where traffic cannot move”, that’s going to have to come from Town Council, and will likely be opposed in the usual manner by Town staff.

So that’s the crux of my disappointment.  I thought that Town Council would use this to act like real planners, and use it to shape the overall scope of allowable Maple Avenue redevelopment.  As in, if we forbid any expansion of Maple Avenue itself to handle more cars (which is unspoken but appears to be true), then let’s estimate how much additional development we can afford on Maple before we drive the level-of-service below level “D” (or “E”, or whatever they adopt as the standard).  And then structure the new zoning regulations to give us no more than that limit.

I.e., I thought they intended to do some actual forward-looking planning, acknowledging the key role that traffic congestion plays in qualify-of-life in Vienna.  But if they did that, it would probably limit the overall extent of development on Maple.  So that sort of proposal certainly isn’t going to come out of our strongly pro-development Town staff.  Any such thinking would have to come out of Town Council.  And I’m not hearing any such thinking, yet.

The other disappointment is that, if used as proposed by staff, this is a traffic-control placebo.  Staff can point to it and say that they’ve addressed the impact of development on traffic, when they have done no such thing.

Why?  Traffic congestion is the cumulative effect of a lot of little decisions.  Traffic congestion can rarely be attributed to any one point source or any one development.   In all likelihood, any “level of service” goal will never be binding on one individual development.  (With the possible exception of the redevelopment of Giant Food, which could pour on-order-of a thousand cars onto Maple each morning, at that one location (Post #479).)

It’s all about the difference between “development” and “a development”.  If you’re serious about not screwing up Maple Avenue traffic any further, what we need is some overall limit on (the totality of) redevelopment on Maple.  (If such a limit is warranted by objective analysis.)  Absent action by Town Council, what we are going to get from Town staff is a rule that addresses “a development”, meaning one individual project along Maple Avenue.

Not only is that not going to address the issue, it’ll let people dodge around the fact that the true issue hasn’t been addressed.  It’s the traffic analog of the completely ineffective open-space requirement.  Look, MAC is designed to give you parks and plazas!  It says so right in the law.  Now take a close look at the size and quality of the open space MAC has brought thus far.  That’s how much traffic congestion control via a one-development-at-a-time approach to level-of-service will likely bring.


Vacating alleyways

Again, read my last post for details.  This ended up being deferred.

My takeaways from this are the following.  First, I don’t really understand the law here.

Second, virtually nobody else other than the Town attorney understands the law here.  Not the people asking for the Town to vacate the alleyway right-of-way, not Town Council, and so on.  Based on what the Town Attorney said, in most cases, the Town can’t sell the right to the alleyway, it has to revert to one or the other of the adjacent property owners, depending on how the alley was created in the first place.  And that requires researching the original title to the land.)

Third, the Town has no systematic plan for addressing these requests.  I think Councilman Noble emphasized that.

Fourth, there doesn’t seem to be any systematic plan for addressing a lot of issues with the Town right-of-way.  This is what Councilman Majdi had tried to get a handle on at the last meeting, but got shot down in favor of having the Town Manager do an “after action” (followup) report on the Wawa tree cutting, and how the Town could prevent such mishaps in the future.

On that last point, I thought the Town Council was mixing apples and oranges, but maybe not.  Today they were addressing the narrow issue of disposing of Town alleyway rights-of-way that serve no public purpose.  Majdi’s point, from last time, was far broader, and included things like oversight of treatment of Town right-of-way during redevelopment.

Councilman Springsteen was disinclined to consider any requests for vacating alleyway rights-of-way at the moment, in light of what happened with Wawa.  His position is that we needed to keep these a buffers between business and residential areas.

When all was said and done, this issue was tabled until the Town Manager comes back with his “after action” report on the Wawa incident.

 

Post #506: Tonight’s Town Council meeting

There are at least three interesting agenda items for tonight’s Town Council meeting.  You can find the meeting materials on this page.  One has to do with “vacating” town alleyways (i.e., selling the land to an abutting land owner).  A second has to do with the Town setting a goal for the “level of service” on Maple Avenue, that is, a goal for the most congestion it will tolerate before trying to do something about it.  Third, the Town is finalizing plans to hire a contractor to tell them how much it will cost to put the utility lines underground along Maple. Continue reading Post #506: Tonight’s Town Council meeting

Post #505: Revisiting #2: Let’s move the Noah’s Ark meeting into the 21st century.

Read Post #480 for the definition, and Post #495 for how this applies to Town’s decision to establish the rules for rewriting all the zoning in Vienna in private, out of the public view.

In a nutshell:

  • Under the Virginia Freedom of Information Act (FOIA), any time three* or more members of a public body gather to discuss public business, that’s a public meeting.
  • All public meetings have to be open to the public, unless there’s some well-defined reason for having a closed meeting.  The statute identifies a specific list of such reasons (e.g., personnel actions).
  • A meeting of two members of a public body is not a public meeting.  It has to be three or more.

* Or, if a quorum is fewer than three.  So if there’s a two-person subcommittee, if those two people meet to discuss public business, that’s a public meeting.

OK, now think like a bureaucrat.  How do you dodge the clear intent of the Virginia FOIA, and manage to hold a meeting of (e.g.) seven members of the Town Council, but bar the public?

Simple:  You break your meeting up into little pieces, where each piece only has two Town Council members present.  Let me term each such piece of the overall meeting a “meetinglet”.

A single meetinglet, by itself, is more-or-less useless.  But now, instead of one meeting with all seven present, you hold a coordinated series of meetinglets, one after the other, with Town Staff providing information on what has been said in all prior discussions.  For legal purposes, instead of that being treated as one meeting of seven people that has been broken up into meetinglets, the law treats each meetinglet separately.

Hence, “Noah’s Ark” meeting, because you bring in the Town Council two-by-two.  You break the seven-person meeting into a series of two-person meetinglets, and presto, it’s legal.

Continue reading Post #505: Revisiting #2: Let’s move the Noah’s Ark meeting into the 21st century.

Post #504: Revisiting old business #1, the mystery of the additional $7,000,000 2020 loan

I don’t quite have the heart to write a post summing up where we stand on MAC zoning.  Which is how I should start the new year.

So, in the meantime, I’m revisiting a few old issues, mostly those that I find puzzling or annoying.  Today’s issue is both.  Today’s post is about the Town’s forthcoming $28M — or-is-it-$35M? –2020 bond issue.

Mostly, I’m revisiting this because, upon reflection, what the Town said about the $35M borrowing authorization simply reeks of baloney.*  They said that the last $7M of borrowings was added with no purpose in mind, and it would be used to add to the reserves in the capital fund.

* I realize baloney does not reek, but my wife made me change this from the original wording.

The sole point of this post is to point that out, as clearly as possible, that this is nonsense.  And then to take a pure guess as to what’s actually going on.  The Powers That Be in Vienna will or will not inform the peasantry of the true reason for the additional loan (i.e., the spending of the peasantry’s tax dollars), at some point, as they deign.  Or not.  All I can do is point out that what they said in that meeting about the additional $7M in borrowings isn’t plausible. Continue reading Post #504: Revisiting old business #1, the mystery of the additional $7,000,000 2020 loan

Post #503: 21/150

Image Source:  Linked from the Dominion Power outdoor lighting website.

Maybe it’s because I’m so burnt out, writing about the Town of Vienna.  Maybe it was an exchange I had with somebody where I said that if you actually look at the “olde-tyme” streetlights along Maple, they look like hell.  Maybe it’s the fact that the Town is going to place four of those lights along Wade Hampton.   Maybe it’s just my knee-jerk reaction to quantify the data wherever that can be done cheaply and quickly.

In any case, the title of this post is the count of olde-tyme “acorn” streetlights that are burnt out (21), out of the total of such lights (150) along Maple.  In round numbers, one out of seven street lights along the “nice” section of Maple (Courthouse to East Street) is burnt out.

Just FYI, it took me about 5 minutes to count them, by taking a drive along Maple.  So this is the count, as I was driving by.  It might be off by one or two.  But it’s materially correct.

Continue reading Post #503: 21/150

Post #502: Craft candles without a tarp

I like to burn beeswax candles during the holiday season,.  I suppose that’s because the scent reminds me of my grandparents’ church.

Candle-making is also a nice craft to do with your kids.   The process is satisfying, it requires parental supervision, and the results are “consumables”.  You aren’t stuck with them, because the whole point of making a candle is to burn it.

That said, most instructions for making traditional candles with your kids omit the most important part:  The tarp.  That is, the tarp you should lay down on your kitchen floor before you start.  Because if you don’t, you get little tiny drips and flecks of wax everywhere, and then you can skate across your kitchen floor for the next week until that wears off.  After an episode or two of that, I learned that traditional candle-making, using liquid wax, is for the garage, not the house.

But there is a way to craft candles that involves no mess:  Beeswax sheets.  My kids made the candles above (years ago).  The process could not be easier.  Take a sheet of colored beexwax and wrap it tightly around a wick.  Strange as it may seem, those burn just like a regular candle.  The candles pictured above are burning now, as I am writing this.

It’s certainly not the cheapest way to make a beeswax candle.  If you’re going to make a lot of beeswax candles, it’s far less expensive to buy beeswax in bulk and either cast or dip the candles using melted wax.  Currently, bulk beeswax seems to be going for $7 to $8 per pound.  Kits with colored beeswax sheets and wick included seem to run about three times that much, per pound.

But it is by far the easiest.  Cut up the sheets as you desire, warm them in your hands until they are pliable, and carefully roll up the wick in the wax sheet.  That’s it.  When you are done rolling up the sheet, the candle is ready to burn.

What’s not to like?  It’s non-denominational, because as far as I can tell there is no religion that’s against using candles.  Little kids can do it.  Bigger kids can get creative when they do it.  And it involves bright colors and fire, both of which are child magnets.  If you run out of ideas about what to do with your kids this holiday season, consider making candles.

Post #501: Hebrews 13:8

In memory of my dad, who I’m sure would appreciate the joke, because I stole it from him.


1:


2:

Source:  https://gifer.com/en/gifs/impatient


 

3:  Hebrews 13:8.

If it’s not funny, re-read it and place more emphasis on the first two words.


4:


5:  Warning:  Recorder got bored and left early

2019-12-16 Town Council Work Session audio file.mp3

https://vienna-va.legistar.com/MeetingDetail.aspx?ID=719394&GUID=75A75570-641E-451A-BAC5-D73402CC6D30&Options=info&Search=

 


6:

Source:  https://gifer.com/en/gifs/thumbs-up

Post #499: Why I don’t recycle my Christmas tree.

It’s much more useful as a fire starter.

Above is the last little fragment of last year’s Christmas tree, just to show you how well and how quickly it burns.  Looks green, burns like gasoline.

I have a wood stove, and I’ve never run across a commercial fire starter that works as well as a dry Christmas tree.  Catches in an instant, burns fast and burns hot.  So don’t recycle my Christmas tree.  I keep it, cut it up, and use it in my wood stove in place of commercial fire starters.

The only downside is that dry Christmas tree pieces are so flammable that I don’t dare keep them in the house.  Commercial fire starters are much safer than a dry Christmas tree.

This time of year you’ll see safety reminders about the hazard of Christmas tree fires.  And now you know somebody who uses his Christmas tree in place of commercial fire starters.  That’s how well they burn.