Ted Leung on the air: Open Source, Java, Python, and ...

I have no trouble imagining a work session that involve iChat AV with an iSight in audio or video mode, along with a collaboratively edited document in SubEthaEdit. When you couple this with TextExtras, you get a really useful tool suite. I can even conceive of doing pair programming in such an environment.
When are we going to see stuff like this on Linux? No excuses about Rendezvous, what Wilhelm and I did last night had nothing to do with Rendezvous. And what about TextExtras? Are the GNOME and KDE textediting widget extensible in the same way?



This means a trip to D.C. for me and (I hope) the chance to make some personal contacts in the Python and MacPython communities.

After my adventures with subversion (svn), I was a little nervous, especially when I saw that Arch also uses the neon library. But for the most part, the Arch build was short and sweet. Arch has a very different model from CVS or svn. In Arch they use branches for everything, and make it easy to merge branches together. That seems kind of interesting. Even more interesting is that there really isn't any notion of a centralized server. Everyone can have their own repository and people decide whether or not they view another repository as a main line of development or not. Depending on the scenario, this seems like it would allow a very flexible way to organize groups of developers. So for now I'm going to try this, along with an Arch to CVS tool.
I've just started out with this, so I'll report more as I go along, but for those of you interested in trying this at home: The Arch Wiki tells you how to get Arch and build it. This IRC transcript gives a quick tutorial on Arch. I also grabbed some tools off of the Arch wiki: cscvs, an Arch to CVS tool, tla-tools, which has a bunch of extra tools (and is cranky about building on OS X without GNU sed -- cranky as in hangs), tla.el, which provides simple Arch support in Emacs, and zsh-completion for tla, since there are lots of new commands to learn.


These things want to be a hub for your Internet community experience, but they're just not necessary enough. Tribe gets closest, but it's nothing you're going to leave as an open window on your desktop all day. The first new social network system that builds an IM program into its structure may have a shot.If these things ever get really useful, you are going to want them to be open all the time on your machine. If that happens, then the connection data is just a data stream for whatever application sits on your desk. I know that I don't want to leave a browser window open for this. The experience just won't be interactive enough. I already have too many communications channels -- I recently participated in a discussion that happened part in blogs, part in e-mail, and part in IRC. This is not at all unusual, and I'm surprised that it didnt' wind up spilling into IM. So what am I trying to say here? The data that's in systems like Orkut needs to be available as input to desktop applications. And personally, I'm thinking a small number of desktop applications. Right now I have Mail.app, NetNewsWire, iChat and Snak (IRC) open on my machine. If I opened up either Proteus or Fire to get the rest of my IM, well, I'd need an entire display (on a multi monitor setup) to keep track of all this stuff. It's too much and I need to work. This stuff needs to consolidate.

Place me like a seal over your heart,When we got married, I understood this passage more from the perspective of passion, and emotion - the powerful feelings of being in love. Today I still understand it this way, perhaps even more than I did then. But the reason is that love has been forged in the fires of life. Through joys and struggles, the good moments between us and the dark moments.
like a seal on your arm;
for love is as strong as death,
its jealousy unyielding as the grave.
It burns like blazing fire,
like a mighty flame.
Many waters cannot quench love;
rivers cannot wash it away.
If one were to give
all the wealth of his house for love,
it would be utterly scorned.
A few nights ago I watched the Quicktime video interview of Howard Dean and his wife. One thing that Dean said really stuck out to me (I'm not particularly a Dean fan):
Howard Dean: She is a huge influence on me. Uh, principally because our marriage is based on respect, and friendship, uh, and those are … I mean, being in love with somebody is a terrific thing, but if you only marry somebody because they're in love … you're in love with them, that's why the divorce rate is 50 percent. And, she's a real life partner, not just a, you know, somebody I fell in love with. She is a friend and I respect her, and that is enormous for me. Plus, she's a lot smarter than I am.It takes more than being in love. A lot more. It takes friendship, respect, vulnerability, the ability to say "I was wrong", and a whole host of other qualities. So when I look back at the Song of Solomon, I understand that the love being written about is not just the heat and passion of being in love, but it is all those other qualities as well. And that's what the writer means when he says
If one were to giveSo thank you, Julie for 12 years of sharing joy, happiness, pain, and suffering. I don't think I really understood what I was getting into, and I think I realize now that I still don't fully grasp it, but I'm looking forward to continuing to discover it with you.
all the wealth of his house for love,
it would be utterly scorned.
Happy Anniversary!
I Love You!

I like the user created tribes feature, which is very similar to Tribes -- there don't seem to be the listings, but the listings never really worked much for me. The profiles are asking for a lot of information, but a lot of it is irrelevant to me because I'm not interested in dating.
So now that my network is getting exposed to the world, what's the benefit? Will I get messages via Orkut that I don't in other media? I'm already connected to the people in my Orkut friends list -- I'm not in it for the numbers. I might get to meet new people via friends of friends. I'm still not seeing it... I've started hanging out in #joiito, and I've gotten more benefit out of that than Ryze, Tribe, and LinkedIn put together. It seems to me that it's not enough to have a big network. The right network is more important.

At the same time, I'm a bit ambivalent about this. Having been a researcher for a while, I've been dismayed at the slow decay of corporate research laboratories, and it's tempting to view this as another step in that direction.

So any way, if you are interested in the various XML related Apache projects, the book is a survey of what the projects including examples of their use.


In other news, it looks like some other folks are going to get involved with the look and feel of Planet Apache, so you won't be looking at my tasteless CSS styles for too much longer.

One of the reasons that it took a bit of time to get Planet Apache up and running is that there was some concern over how "official" it would be. There was a segment of the community that was concern about oversight of it (there's lot's of concern about oversight at the ASF these days). Other people were concerned about people ranting on about stuff unrelated to the ASF, which has prompted people to create subfeeds of their blogs for ASF topics only.
The consensus of the ASF community that expressed an opinion was that we host Planet Apache off the ASF infrastructure, thereby avoiding (we hope), the oversight and branding issues. This is also one reason why I haven't been super fast about getting feather up onto the site either. Fortunately Thom May stepped into the gap with hosting, and between the two of us we got the thing going.
Thom and I have not corresponded a super lot about Planet, but I was pleased to see his post about it today. Thom is interested in Planet Apache as a social vehicle, and I think that this is an important part of its function. One version of Planet Apache would be an aggregation of ASF specific subfeeds, which would get you a kind of "what's happening in the ASF world". This is kind of an informal newsletter or daily status report. That's all fine and good.
That's not what we have today. What we have today is whatever feeds people registered, which makes it less directly focused on ASF software projects and more focused on ASF people. This is important, because all ASF people are more than just the ASF projects that they work on. So it's as important, or more important to trust the people in the ASF than the organization itself. That can only happen as people get exposure to one another, and not only in a technical fashion. So the fact that Planet Apache is more like a day long water cooler conversation rather than an hourly status report is of great value. The ASF is now more than 700 committers. How do you build community across that many people? One thing that you can do is create a place where they can express themselves and their opinions uncensored, so that more of their personal side becomes visible. It helped a lot this year when I went to ApacheCon and talked to people who had blogs. There was more to talk about outside of code, and that made it easier to use that precious face to face time to build deeper relationships.
I think that Thom and I are in agreement that we won't require ASF specific feeds. If people want to do that, that's fine by me. But let me suggest to those folks that you are short changing your fellow ASF'er's and the people that use our software by doing so. Let your hearts and souls out a little bit.

Sam had a great summary of the whole deal, and one of the most important values for assessing projects. It's the people not the code. Or put another way, since you almost always need more than one person for a sizable project, it's the community, not the code.


I'm ambivalent about vCard versus FOAF. For the purposes of interoperability with other clients, vCard is probably the better format. For the sake of everything being XML, FOAF as a slight advantage, since the xml-vcard effort seems stalled, as does the rdf-vcard effort.

At the moment there is support for retreiving posts, editing them and creating new posts. Labelling posts with categories is supported. Changing posts and deleting posts is not.
This support involves modifications to the blogger XML-RPC plugin as well as a new metaweblog plugin. In addition, these pluging rely on changes to pyblosxom.py which are not yet in CVS. All the necessary files are available from the home page.
This posting was made (and edited) using these plugins.
Thanks to Adriaan Tijsseling, the author of Ecto, for helping me to debug this.
I also plan to do support for NetNewsWire's weblog editor -- Brent and I are working on some issues there.
One final note. This support is for my own use mostly, but I thought that people out there might find it useful. I'm very happy to receive patches that make this work with blogging tool X. Beyond support for Ecto and NetNewsWire, I'm not promising support for any other blogging tools.

Last night and today I've been wrestling with getting subversion 0.36 to build on Mac OS X. I was unhappy with the Fink guys because their version is so far behind, but after my experiences, I understand a bit more where they are coming from.
To build subversion (svn), you need Berkeley DB (BDB) 4.2.50, Neon 0.24, httpd 2.0.48, and subversion-0.36. Getting the tarballs and unpacking them is no problem. I built Neon and BDB according to the instructions and set them aside. No problem. Next up, build httpd 2.0.48 against BDB 4.2.50 so that httpd and subversion both use the same BDB (subversion needs BDB 4.2). I got stuck here for quite a while.
First, the httpd build wasn't finding BDB. This was partially fixed by Justin Erenkrantz who pointed me to a newer version of httpd-2.0.48/srclib/apr-util/build/dbm.m4
(I got version 1.8). This got me further not quite all the way. I made a typo in the pathe for BDB which was just dumb. But it took a couple builds to find it (thanks to Jack Repenning). The next obstacle was that httpd built, but subversion wasn't finding it or SSL. When I tried to run apachectl. It failed with an error about expat libraries being incorrect versions. I was trying to build all of the httpd modules as shared, which may have been the problem. So throttled back to enabling just the modules described in the svn INSTALL file. This still didn't produce a working apachectl. As a last act of desperation, I blew away the httpd directory and unpacked the tarball again, copied the new version of dbm.m4
and configured. And lo and behold httpd built and apachectl ran. Of course, I'm missing a bunch of modules that I want -- I guess I'll be learning how to build individual modules as DSO's (yes I did try to build all the modules non-shared. subversion didn't like that either).
Working httpd in hand, I then proceeded on to try and build svn clients and servers. After the first attempt at configuring, I saw that subversion actually builds neon itself. So much for the original build of neon. The problem was that neon wasn't getting built with SSL support. So I went looking through the mailing lists (again) for some kind of pointers. Fortunately, this message mentioned the --with-libs= option for neon, which resulted in subversion configuring correctly. The compile just finished and everything seems good. I can't guarantee that it runs, but that's next on my list.
If you've been keeping score, and you want to try this at home (assuming you've unpacked the tarballs):
cd db-4.2.50 cd build_unix ../dist/configure make sudo make install cd .. cp dbm.m4 httpd-2.0.48 (you have to get the path for dbm.m4 right after you download it) cd httpd-2.0.48 ./configure --enable-dav --enable-so --enable-maintainer-mode --enable-ssl --with-berkeley-db=/usr/local/BerkeleyDB.4.2 make sudo make install cd .. cd subversion-0.36.0 ./autogen.sh ./configure --enable-maintainer-mode --enable-ssl --with-ssl --with-libs=/sw/lib --with-berkeley-db=/usr/local/BerkeleyDB.4.2 make sudo make installNo goats, chickens, or other animals required. Just lots of frustration.
