Thursday, May 14, 2009

Green

Everywhere I look I see the green. It's Spring, so my green lawn needs a bi-weekly whacking with my John Deere green lawn tractor (which is complicated by the low-hanging green-leafed limbs of some of the trees on our property). But if that was the only green I was seeing, that'd be okay. Unfortunately, it isn't.

"Going green" or "being green" or "living green" almost wholly consumes the mass media and the consumer marketplace. Right now, over half of the top results from a simple Google search for a word as common as "green" are about environmentalism, eco-friendliness, and so on. Green is the new black, or something like that.

Climate change (née global warming), carbon offsets, renewable energy, reduce/reuse/recycle, are worthy topics all. And as a Christian who believes that mankind was entrusted with wise stewardship of God-created, God-provided resources, I don't think I or anybody else holds a get-out-of-responsibility-free card. But I detect two big, green problems with much of the hype:

Man sees green — in financial opportunity. I honestly do not know who to turn to for trustworthy information about the state of the world; its climate and related trends; which problems are real, predicted, or flatly imagined; which solutions are viable; and so on. Part of the problem is that there's too much money in the eco-this-that-or-the-other trend right now. Do I really believe that every producer of goods is concerned about the world when they release some fascinating new eco-conscious version of their product? Hardly. Seems sex is getting a run for its money in the "marketing tools" arena these days.

God sees green — with envy. We have a jealous God who demands that all things be done for His glory. Not mine, not yours, and not Earth's, but God's glory. I think far too many people have traded being caretakers of creation (as a form of worshiping the Creator) for worship of the creation (Earth, humanity, Self, money, ...). That's busted.

There must be a better, more divinely-inspired way of exploring this problem space and its solutions, because being green — that is, naïve — enough to worship this rock or anything or anyone on it is a horrific non-starter.

Wednesday, May 13, 2009

ViewVC 1.1.0 (finally) released.

Today, I finally got around to releasing ViewVC 1.1.0.

I know. And you're right — that's not the most uplifting lead-off line ever written for a technical blog. Sounds mostly positive (new release?!), with a hint of exasperation, and all shrouded in a mysterious cloud of why-should-i-care. Sorry about that. But allow me to explain.

ViewVC 1.1.0 represents — maybe misrepresents — three years of development on features introduced since 1.0.0 came out. I'm pretty pleased with the features, many of which were contributed by and/or willingly tested by volunteers. Here's an overview, taken from the official release announcement:

  • Extensible path-based authorization w/ Subversion authz support
  • Subversion versioned properties display
  • Unified markup and annotation views
  • Unified, hassle-free Pygments-based syntax highlighting
  • Subversion svn:mime-type property value honoring
  • Support for full content diffs
  • Standalone server improvements
  • Commits database management and query enhancements
  • Support for per-root configuration overrides
  • Optional email address obfuscation/mangling
  • Pagination improvements
  • ... plus many bug fixes and additional enhancements!

"That's it? After three years' time, that's all we get?!"

It's okay. I've asked myself that a hundred times, too. It's a bummer, but I think I'm learning another hard lesson about open source projects: when a piece of software reaches a certain level of maturity, the developers-to-users ratio tends toward nil.

Before I ever started working on ViewCVS (which was what ViewVC was called at the time), it was already a well-established, widely used piece of software. CollabNet used it to display version control repositories in its CollabNet Enterprise Edition software suite. SourceForge.net was doing the same. It seemed that everybody had a copy of ViewCVS. The software was ubiquitous, worked well, and CVS wasn't changing significantly. And ViewCVS's developer participation reflected this plateau of innovation, too — I think there might have been two or three folks active at the time, mostly just fixing the occasional bug.

Seven years ago, I was tasked by CollabNet to add support for Subversion to ViewCVS. Subversion hadn't even released its 1.0 version at the time. Subversion was still this young, exciting, rapidly developing new entry into the version control world. I (with the help of others) did get Subversion support added to ViewCVS, and along the way I inherited primary maintainer-ship of the project. The project was renamed to ViewVC later to reflect the fact that it was no longer CVS-only, and I began focusing on fixing outstanding bugs and tracking changes in Subversion's new releases.

Fast-forward a few years. Now Subversion's rate of change — at least, in terms of what's of interest to a repository browser tool — is starting to plateau, too. And ViewVC's contribution rate is again reflecting that. Fewer active committers (< 2), investing less time (< 1 day/month), and with fewer volunteer contributions.

It's lonely here.

But it doesn't have to be. There still remain opportunities for improvement in ViewVC. Off the top of my head, I'd say adding support for other version control systems — Mercurial, Git, etc. — is a place where your expertise and effort would be not only appreciated, but required, if only because I don't use those systems myself. Scalability and performance improvements are always welcome. And I'd love to see ViewVC's MySQL integration expanded — why not use the database as a glorious cache of information that takes too long to harvest at runtime from the VC system?

So, while I might casually kick myself in the backside for finally and barely eeking out a new release of ViewVC, I do so understanding now that this may just be the way things go for mature software, thankful for ViewVC's many users, and happy to be working on free code.

Take ViewVC 1.1.0 for a spin. Kick the tires. Send feedback — positive and negative — to the mailing lists. I might be slow to respond, but "I'm not dead!", and neither is ViewVC.

.o O ( "I think I'll go for a walk … I feel happy." )

Tuesday, April 21, 2009

On hymns and praise songs

Yep, this pretty much sums it up.

Liz, I know this doesn't count as "writing more on my blog", but at least I've given you something to read via my blog. Close enough?

Thursday, March 26, 2009

I am a worship leader. (And so are you.)

While contemplating God's love letter to artists, and directly on the heels of a message at church last night about the ways in which Satan attacks Christians, I find myself staring directly into the eyes of some of the same old insecurities that have haunted me over the past few months. I'm ready to 'fess up about those now.

I have some musical talent. I think I can even offer a pretty objective evaluation of that talent:
  • I sing, but my voice is thin in higher registers and can suffer pitch control problems in lower ones. And, probably due to vocal abuse, the clean tone I could produce ten years ago is giving way to something more crackly.
  • I play guitar, but am self-taught, and have never invested enough into learning either the acoustic or electric guitars to move beyond competence and into proficiency.
  • I'm not such a fine songwriter. I'm lyrically uninspired, and melodically challenged. But I'm really good at taking another person's song foundation and enhancing it (with neat arrangements, harmonies, counter-melodies, motifs, and so on).
  • I can wield digital audio software skillfully, and have even developed some pretty neat sonic "tricks" that have served me well. But I can't seem to produce output that sounds quite like I envision. (A recent attempt at something Counting Crows-ish was referred to — behind my back, mind you — as "yacht rock", with an apparent Air Supply influence. Ouch.)
I think it's healthy for folks to be able to recognize what they truly can and can't do. Wouldn't you agree?

Then here come the demons. "Why, again, are you helping to lead worship at yet another church? You don't fit the mold. Real worship leaders have hip haircuts; wear trendy clothes; are 10 lbs. underweight (instead of 20 lbs. over); have at least eight stomp boxes and a sound engineer devoted solely to their rockstar groove; sing with perfect pitch, tone, and timbre; and can spew God-honoring utterances while ripping fingers-of-fury blazing guitar solos. With their eyes closed and both hands raised to the heavens. You are no worship leader. You are, at best, background noise."

Oh, man, that stuff stabs. Plunge. Twist. Gush. (It hurts even now, just thinking about it.) But that's okay — I figured out some time ago how to protect myself from those barbs. See, I've dealt with this in the past by simply denying that I was (or was attempting to be) a worship leader. I was "just trying to help with the music program", or something like that. After all, the Enemy can't beat me in a race I refuse to run, right?

Sadly, I was wrong: I am defeated because I refuse to run. My responsibility as a created being — the tax on my very existence — is to worship the Creator. But my responsibility as a human is to lead (by encouragement, example, or otherwise) my fellow humans to do the same. My roles as a husband and father, especially, demand this service to my wife and children. And how can I be seeking loopholes in the Covenant when I've failed to lead those who I would consider some of my closest friends to worship God with me? No, whether I accept the label of "worship leader" or not, the responsibility is mine. God's will begins with thanksgiving and worship.

I appreciate the perspective Geoff Janes provides on the search for God's will at http://geoffreyjanes.blogspot.com/2009/03/what-is-gods-will-for-my-life.html. I should consider myself fortunate to have discovered — through the talents God has given me and the discernment of trustworthy others — a piece of God's extended will for me at this time: demonstrating that thanksgiving and worship with a guitar in hand at Providence Baptist Church. It may only be for a season — that is not mine to know. But at any cost, I must therefore seek only to do that will, and waste neither energy nor emotion chasing the unattainable stereotype constructed by the Enemy. My skills are not worthy of renown. Fortunately, they weren't fashioned for that purpose.

So today, I reject as invalid the notion that leading worship isn't my job. I accept as valid criticism that I've not been particularly good at this in the past. I apologize to my family and friends for not living a life that consistently and convincingly compels you to worship, too — love demands better than that. And as for that background noise I'm ever-so-capable of? I'm cool with that. But may it be a joyful noise from this day forward.

Tuesday, March 24, 2009

God's love letter to artists

Jon Acuff (of Stuff Christians Like) writes today about God's love letter to artists. Like Jon, I've overlooked multiple times the Artist Ordination Ceremony there in the book of Exodus. I especially appreciate Jon's challenge to those gifted artistically to use their gifts to "rebuilt the temple" — to improve the physical, spiritual, and emotional lives of our fellow man. What better way to bring glory to God than to use the tools He has given to edify the objects of His greatest affection?

Monday, March 16, 2009

Heaven and hell

I came across the following joke today in the comments section of a particularly good post on Jon Acuff's Stuff Christians Like blog. (Thanks Helen, whoever you are.) It's … er … something to chew on.

A man spoke with the Lord about heaven and hell. The Lord said to the man, "Come, I will show you hell." They entered a room where a group of people sat around a huge pot of stew. Everyone was famished, desperate and starving. Each held a spoon that reached the pot, but each spoon had a handle so much longer than their arms that it could not be used to get the stew into their own mouths. The suffering was terrible.

"Come, now I will show you heaven," the Lord said after a while. They entered another room, identical to the first - the pot of stew, the group of people, the same long-handled spoons. But there everyone was happy and well-nourished.

"I don't understand," said the man. "Why are they happy here when they were miserable in the other room and everything was the same?"

The Lord smiled, "Ah, it is simple," he said. "Here they have learned to feed each other."

Thursday, March 5, 2009

Today, I feel like a successful husband

Determining if you are succeeding as a husband probably involves some pretty unruly psychological calculus, but today I feel like a successful husband. Why? Did my wife express her love and devotion in some particularly convincing way? Was I presented a trophy etched with "Best Hubby 2009"? Is the Internet community hanging on my every tweet to find some sage advice on being an ideal mate? Not hardly. It's for much less obvious reasons that I feel this way.

Last night, as Amy and I left church, she had a huge smile on her face and she said, "I think I've found my place".

This was the first Wednesday evening service we've attended at our new church. After the service last night, Amy and I participated in practice sessions with the church's music team for the first time. The music director and pastor have graciously agreed to let us try to work to bring a slightly more contemporary flavor to the worship music of the church. So I added my guitar to the piano and keyboard sound already present, and Amy is donating her voice to the praise music and to the choir. It was the participation with the choir that had Amy so thrilled last night.

What has Amy's happiness as a musician to do with my success as a husband? Everything. I can rest well at night knowing that I have encouraged her to serve the church in any capacity she desires and feels gifted to serve. I have worked to arrange meetings with the pastor and music director so we can research this area of service. And I have consistently recognized, praised — and even constructively criticized, when necessary — Amy's wielding of her God-given musical talents. And someday, when God blesses her obedience and service to Him in this matter, I will be able to both share in her joy (three-point shot, nothing but net) and claim some of it for myself (the assist).

Could success as a husband really just boil down to using unconditional love to guide my wife toward the likeness and service of Christ?