IMO

Lars and I proposed a Lightning Talk at ApacheCon where we share with the attendees some of the various "fan mail" the ASF gets (via Email and FAX). It didn't get picked, but that doesn't mean it wasn't a great idea. Since the ASF FAX machine is located here in my home office, I get to see them first hand, and I like to bring a handful with me to ApacheCons to share with the rest of the members. They always get a few laughs. Anyway, I'm thinking about actually scanning them all as they come in and having them archived someplace for posterity. A small sampling of them can be found here and here. Before you follow the linkls, note that the language is quite, well... curt. Glad to see all our hard work be so appreciated... <grin>

Late last night (late because, well, it's always late when flying back east from the west coast, unless you want to take the red-eye, and later still since my connecting flight got cancelled), I got back home after spending 3+ days at ApacheCon US 2005. It was a blast. First of all, of course, it was great re-hooking up with people that I simply don't see enough. Not nearly enough. Also, it was great finally meeting people that I've hadn't had the opportunity to do so (like Paul and Jean and Susie!). The sessions I attended (and chaired) were top-notch, and the venue itself (the Sheraton San Diego Hotel & Marina) was, well,... let's put it this way: heads and shoulders above the venue of the last coupla US ApacheCons. Also at ApacheCon, there was the Hackathon, which I thought was pretty productive (code-wise and community-wise), and the ASF Members Meeting, where we added quite a number of new people to the ASF roster (full list to be public once we know who accepts). With the size of the ASF now, organizing the members meeting is getting somewhat difficult, as far as doing the roll call and then counting the votes. This year I tried, for the roll, having myself and other directors mark people's names off as they entered the room. This worked out OK, but I now regret doing it that way. There's a lot to be said for calling people's names out loud, so that others in the room can then match the name and faces... I think I'll go back to the old way. There's other stuff I want to post about re: ACUS 2005, but those will come later.

Lots of stuff to post about, but instead of lumping them all into one, I'll make separate entries. First big news is that we've released v2.2.0 of the Apache HTTP Server ("Apache"). I must admit that I was somewhat concerned about what appeared to be a rush to release, to meet some artificial deadline, but the more I think about it, what's important is getting this release out quickly to many people, so they can use it and provide feedback on it. Even though the 2.1 tree has gotten a serious workout by some very large, big-name sites, now that 2.2 is GA, the codebase will get an even wider user audience. There are a lot of very cool features, and some "older" features have been significantly improved. I'm expecting a lot of people to finally migrate off of 1.3 in favor of 2.2. Much is being made about how 2.2.0 was released 10 years to the day from 1.0.0. Somehow that makes me feel both old and young at the same time. It seems crazy that I've been developing and hacking Apache for over 10 years now. That's a relationship longer than a lot of marriages I know about! During that time it's been my fortunate good luck to have worked with some truly gifted programmers, true artists of the craft. I don't like mentioning names because there are so many, and I don't want to hurt anyone's feelings, but 2 in particular stand out, and I feel comfortable mentioning them because they are no longer actively engaged with the ASF. Robert S. Thau (RST) was crucial in the initial design of the main aspects of what we currently think of as basic Apache concepts (pools, the API, etc...). And Dean Gaudet was a master in going from concept to code, and in optimization of both. I learned much from both. It's also interesting to see how things have changed, and how the basic concept of how the ASF works is constantly being verified by Apache. In the over 10 years since Apache was released, I've seen developers come and go, yet the community remains, and it's the community that develops. I've seen other open source projects whither and die when a "key" developer leaves, yet healthy ASF projects continue to grow, because we've always stressed the community; and time and time again we've seen how right that is, and that people step up, and fill any "voids" that might exist.