Work on boomstick continues. Code that was unnecessarily integrated into the boomstick webapp (such as the markout generator) has more or less been disentangled into organs. Put together an organ grinder script to package organs separately from the core application -- still need to abstract that out for skins and valuemeals as well, but that's not huge. Also tested webdav support, which I get for free thanks to svn+apache -- short version is that is works about as well as your client. It's getting to the point where I could package a release. I'm inclined to, even though the repo api still needs to be, um, written. Perhaps a pre-pre-pre-pre-pre-pre-pre-alpha release, to get the code and some of my thoughts cleaned up.

I recently put together a simple RSS feed organ, and decided to write it in XSLT 2.0, which I also get for free thanks to Saxon. It probably goes without saying, but XSLT 2.0 is just a ton nicer than 1.0, simply by virtue of dropping RTFs and allow user-defined functions. I'd also like to add XQuery support, I'd really really like to, but there are apparently two hurdles:

- There is a conflict between Cocoon's APL and Saxon's MPL, at least for the Apache folks.
- Someone is going to have to get off their ass and write a generator.

Answers my question about why Saxon's never been included in Cocoon, though. Now, writing a generator probably (hopefully?) isn't that daunting of a proposition. There's nothing inherently hideous about writing Cocoon generators, and without looking at Saxon's XQuery API, I'd hope (pray) that I can just instantiate it, throw an .xql at it, and get back a DOM or a SAX stream or something. Which leaves the license issue...

Back in 2001, the dude who created Cocoon didn't think there was a legal problem with packaging APL and MPL code together although "it's not encouraged." So perhaps the licensing isn't an issue, either. I haven't figured out what license I'd put boomstick under, so that complication doesn't factor in, yet.

I dunno. Anyone have any experience with releasing code that incorporates third-party code with (possibly) conflicting licenses, specifically the APL and MPL?