A full report will be forthcoming when I have finished these books or given up trying.

OSNews has an article listing a huge diversity of Mono-based applications. I hadn’t heard of a lot of these!

My wrist works again.

Hula is only a week old and yet has enjoyed tremendous attention already. The activity level is fantastic:

• Martijn van Beers has written a perl script that queries the NMAP agent to get your calendar, then exports it to the web, in a manner suitable for reading by clients like Evolution and iCal. Take note of the screenshot, which even shows recurring events working. Hoozah!

  Not content with this, Martijn is pushing ahead to write GroupDAV support for Hula. Good luck Martijn!

• Dave Camp has ported Hula to Mac OS X, where it builds and runs even without the support of fink, having so few dependencies.
• Paul Querna has got Hula working on BSD.
• Alex Hudson has posted some debs of Hula for Debian and possibly Ubuntu users.
• Kyle Yencer has created RPMs for Mandrake.
• Lachyg has Gentoo ebuilds of Hula available for download.
• John Kelley runs hulaTar, a service that provides tarballs of each svn revision.
• Dave Camp has posted an update to the hula-general mailing list wherein you will find some details on what he and some of the Novell-employed Hula hackers are planning on doing this week.

One of the important things happening this week is the re-normalization of the URLs that Hula uses for calendars and mails. We want Hula to have simple, memorable URLs. This will get us most of the way toward allowing easy calendar publication, which I am looking forward to in particular.

See, Joe and I have a mailing list that all of our friends, mainly in the Boston area, use for group communication. Most of the time the traffic on the list is of the form, “Hey, Kelly is having a party this weekend; here’s the invitation.” Or, “Anyone want to go to New York to see The Life Aquatic next week?” Or other things of this nature.

Robert and I were talking recently, and we realized that this mailing list is essentially a calendar. A calendar with no way to get a view of what’s happening on what days or who’s coming to what without reading all the mails and constructing a view in your head. A calendar that we are running on mailing list software.

So we want to try to replace, or at least augment, our mailing list with a shared calendar. One of the first steps is to allow calendar publication, so that people can maintain social calendars that their friends subscribe to (“here’s the cool sutff that’s going on in Boston”); later, we can make group calendars with multiple writers.

The new URL scheme will also be an important step to support CalDAV in the future, which we’ll probably start on in earnest next month, and which we’ll need to work with Sunbird and Chandler.

Also I lost my camera about a week ago. I think I left it in a taxi. Oops.

Jamie wrote up a summary of the lecture he gave me that inspired Hula’s direction. Obviously, I was pretty swayed by it, so I think it’s worth reading for anyone writing software.

Today we are thrilled to be launching Hula, a new project to build an open source mail and calendar server.

Hula is a really exciting project already in part because we think that we can fill a hitherto-unclaimed spot in the stack of open source applications and in part because we’ve “primed the pump” by basing it on an existing, functioning codebase: a Novell product called NetMail. NetMail already runs millions of calendars and mailboxes. And so we’re starting off with the mundane work of building a functioning server done, leaving us to focus on creating interesting new functionality.

We know the demand is high for a credible piece of software in this space. Ever since we first released Evolution in 2000, people have been asking us where they can find an open source server. The lack of an implementable open calendar server protocol has crippled calendar-server efforts for years; we think CalDAV is finally going to fix that and are getting behind that as our primary fat-client interface for Evolution and Chandler and Sunbird, and maybe Outlook as well.

Our direction is distinct from other open source collaboration server projects in that we’re not trying to build every conceivable bit of functionality that someone might consider “collaboration” into the server. Instead, we are focused on building great calendar and mail functionality. The dominant collaboration solutions today (Exchange and Notes) are built on a pre-Internet design and are just no fun to use for real people who live on the web, who collaborate across organizational boundaries (or who don’t have organizational boundaries to worry about), who want light-weight tools and URLs for their meetings and their appointments on their cell phone and so on.

So we have a couple of specific ideas we want to focus on.

We will build a JavaScript-based rich client for mail and calendaring, in the style of GMail. Those of you who follow my blog may have noticed me waxing optimistic about the power of web clients over the last few months; even before maps.google.com came out and blew everyone’s mind.

I looked for weeks to find a project implementing an open source version of GMail. I even posted to Google answers in my search. It doesn’t exist. Well, today we’re starting one, and we’re inviting the world’s crack JavaScript/DHTML hackers to help us.

We will build a real web-based calendar. Every networked calendar I’ve ever used has been exactly the same: create appointment, specify subject, location, start time, duration. Accept/tenatively accept/decline. Private/public. Free/busy search.

The current Hula web interface, by Garrett LeSage

And yet there’s no way to schedule appointments with people for whom I only have an email address, no way to get at my calendar data programmatically, to script it, to view it with an RSS feed, to access it via IM or SMS, etc. Thanks to the webcal URI standard people are starting to publish calendars but there’s no easy way to maintain these other than exporting an ICS file from your client and copying it to a server every so often.

Why has no one rethought this model?

Well, we’re going to try to. Our first ideas are up on the Hula web site. Take a second and check them out. Some of this came out of conversations with Jamie Zawinski, and he deserves credit for focusing us on calendars instead of floating off into, I dunno, voice over IP integration or something.

This announcement has been several months in the making here at Novell, but the real work to build a community and interesting new functionality is just starting. Hula is new. It’s young. If you want enterprise-class groupware functionality on Linux today, your only reasonable option is GroupWise. Hula will grow up over time, and probably go in new and unexpected directions. We’re looking forward to seeing where people take it.

One of the incidental things we are doing with Hula is that the web site is a wiki. I’m really interested to see how well that works out; for today’s launch we’ve locked the pages to prevent opportunistic vandalism, but we’ll probably open them up to world-writeability (literally) in a couple of days. Many thanks to Kate Turner and Brion Vibber for their help with MediaWiki over the last few days.

I’m probably going to be spending a lot of today explaining Hula to journalists, but when I’m not doing that I’ll be in #hula on freenode.

Each time he writes a new book, I expect Dave Eggers to fall on his face and put out crap. My pessimism, I think, is rooted in those long “metanarrative” sections from A Heartbreaking Work of Staggering Genius (and in its title!), which barely worked, verging on showoffy-cutesy-clever. He has always come across as an author on the brink: on the brink of self indulgence, on the brink of a bad joke, of being too young, too ironic, or something. And I think he knows it.

But he’s put out two books since (You Shall Know Our Velocity and How We Are Hungry), and I’ve just finished the latest (Hungry) and I really liked it, though it had the same cringe-factor moments in it as the previous two.

I’m sure his books aren’t for everyone. I don’t think my dad could read them; I think he’d probably seem like a juvenile, crappier version of a serious writer to someone like my dad, who studied literature for decades, taught journalism at a university, etc.

The real point of this entry was to quote a paragraph I really liked but now I can’t find it. The gist of it was that flying is more common today than it was when my parents were growing up, and so it’s fairly normal (for my generation) to have friends whom you see sporadically, in random places around the world throughout the year. I identified.

So, while I’m typing here anyway, I’ll just note that I also read Neal Stephenson’s entire Baroque Cycle sometime last year, which was basically extended light entertainment with an educational twist, sort of like watching 3-2-1 Contact when I was a kid.

And it also had those cringe-inducing passages; so bad, they are difficult to even mention. Among the worst was a reference to a Microsoft marketing campaign, wherein one of the main characters, Jack Shaftoe, is walking along a dock, selecting galley slaves for his boat, and they’re all jeering at him, and one of them shouts out “Where do you want to row today?”

Get it?

I had to put the book down for a few days after that, but picked it back up in the end because the sunk costs were so high, I couldn’t bear not finishing it. And it was genuinely engrossing to see the world through Stephenson’s eyes; it made me want to visit Amsterdam again, anyway.

And, you know, it’s easy to be a critic.

Other Me-Oriented News

In other me-oriented news, it’s been over 4 months since I’ve had a cigarette, I beat Miguel 3-1 at chess tonight (though he punished me badly two nights ago), this web site is amazing, the BBC plugin for my beloved squeezebox is wonderful, I am in love with wikitravel and last week in two separate incidents people on the street recognized me from this web site.

“Are you nat.org?” they asked.

Boy is that disorienting.

David Reveman, who became a Novell employee a couple of weeks ago, has been writing a new X server on OpenGL/Glitz called Xgl. Because Xgl is built on GL primitives it naturally gets the benefit of hardware acceleration. For example, window contents get rendered directly into textures (actually they get copied once in video memory for now), and so you get the benefit of the 3d hardware doing the compositing when you move semi-opaque windows or regions around.

But there are other benefits too. Simple GL operations on the windowing system can suddenly produce incredible results. Want live, running thumbnailed versions of iconified windows? Done. Want your six virtual desktops to be the six faces of a cube that spins, with lighting? Done.

Xgl running GNOME.

David has a lot of ideas like these, and you probably do too. Apple’s cute hacks, like Expose, are inspirational but now that space can be ours to explore. Xgl opens up a whole world of hardware acceleration, fancy animations, separating hardware resolution from software resolution, and more.

I’m personally pretty excited about this. I think running the X server on hardware-accelerated GL directly seems like a very elegant way to go. David was educating me tonight on how X’s last lingering limitations are being cast off. With Gtk moving to Cairo, the X server running on Glitz/OpenGL, and hardware vendors providing 3d-accelerated OpenGL drivers for their cards, we will have a UI/graphics platform as powerful as OS X or Windows.

David is going to be demoing his server at XDevConf in Boston this weekend. The source code for Xgl is here.

Update: Thanks to David’s help, I am now running Xgl on my laptop (ATI FireGL T2). Some observations: dragging windows doesn’t generate any expose events, and is incredibly smooth and solid; antialiased text rendering is hardware-accelerated and so vte now screams (though it still uses all my CPU, so is not useful for compiling); it is a bit unstable, but far better than I expected.

Cool!

I also just learned a neat trick to create direct peer-to-peer network connections even in the face of two restricted NATs. This technique does require an “introducer” server on the public internet, but after an initial connection is made all data goes directly between the peers.

This method is probably common knowledge to you if you run in the right circles; iChat AV uses it, and probably Skype and others do as well. There is a good description on this page too; search for “bubble packet” in the text. Brady Anderson of iFolder fame taught me about this tonight.

Alex got a phone!

And he can pay for breakfast!

We walked up to Twin Peaks.

The results of my Wiki survey:

MediaWiki 9 DokuWiki 5 GracefulTavi 2 QwikiWiki 1 PmWiki 1 Instiki 1 Total 19

I’m going to go with MediaWiki. It runs Wikipedia so it scales, it can export its contents, and it has a really active community.

I guess it shouldn’t surprise me that Wikipedia maintains a list of available wiki software.

Joe Shaw faces off with a banana (interpretive).