You might notice, the main website has received a quick face-lift. We're in the process of rolling out a new Confluenza, along with a freshening-up of the design. It's about time we came screaming out of 2001, and go for the new Web 2.0 long narrow column style.

Over on http://docs.codehaus.org/, we've upgraded to Confluence 1.3.1.

Well, you might've noticed that we went missing off the next for a while today. Originally planned as a 30-minute drive-swap, we ended up off for 6 hours and finally gave up on dd'ing the 120gb of disk. I apologize for whatever inconvenience you might've experienced. We're going to figure out another plan to allow for this upgrade without having to go offline while dd does its damage.

Can't find something? We're Google-enabled site-wide now. I couldn't be bothered to get a self-installed search engine working snazzily yet, so...

search.codehaus.org

So, you're behind a firewall but still want to kill time chatting with the hausmates or arguing with Fate...

Use the bridge.

Well, we've finally moved all projects to the new hardware. Fun fun fun.

Slow projects are getting their websites redeployed and updating the meta-information about their project.

This page should soon become the canonical jump point for all projects.

Folks have noticed the fall-out of what happens when you upgrade machines. I've been moving a lot of projects from our overpriced machine at Rackspace to the bigger and better machine in the bunker in Canada. Anyhow, to answer the #1 FAQ of the week:

Projects that have moved, and you can't seem to find, are now available if you following the form of:

cvs -d:pserver:anon@cvs.PROJECT.codehaus.org:/scm/PROJECT login
cvs -d:pserver:anon@cvs.PROJECT.codehaus.org:/scm/PROJECT checkout MODULE

Replacing PROJECT and MODULE in a way that makes sense.

Web source would then be:

  http://cvs.PROJECT.codehaus.org/

Each project has its own subdomain that holds pretty much everything for it.

Coming soon: list archives!

Wisdom gained from this migration:

It's much better to design a system where to upgrade, you simply add machines. If you have upgrade by replacement, the move is much more painful. The system I've set up now will support more growth (lots more projects for Hani to complain about); we can simply add another machine and partition along the project axis instead of the service axis.

Live and learn.

It's with a heavy heart that I submit this farewell entry.

Yesterday, during our regular quarterly review where we gather status reports on all the projects, discuss haus business, review recent proposals, and vote on policy issues, Jon Tirsen suggested that perhaps I haven't been leading the haus with the appropriate amount of vim, vigour and vitality (the v^3 principle, as he put it). The motion was seconded by Aslak and quickly a vote of confidence was taken. Alas, it turned out decidedly Not Well for me. With the head of the haus removed, nominations were collected for a replacement. Long story short, Hani was voted in. While his entry today attempts to blame a job change on the demise of the BileBlog, he fails to mention that the job is that of being Hani the Kind, leader of the neuvo Codehaus.

Part of his proposed policy changes include porting all projects to .NET along with factoring out common bits of the multitude of projects into a new top-level project known as the codehaus commune library, which will be similar to the jakarta-commons effort at the ASF. Part of this effort includes the creation of a Groovy compiler for .NET.

I must say that I was quite dismayed to learn that the animosity between Hani and the ThoughWorks drones was purely a fiction in order to undermine my credibility. Tirsen and Hani apparently have been sharing beers and planning this mutiny for months, now.

In light of these developments, I find that I can no longer consider myself a part of either the Codehaus or the bully-laden open-source movement. I wish you all luck, but I think it's time to hang up my xterm and open a bakery. Look forward to the opening of Bob's Donut Werks in Asheville, North Carolina this summer.

Hani with a fish and his new Groovy t-shirt

The Codehaus::Home is now being driven from our HAUS space on docs.codehaus.org.

Powered by Atlassian Confluence.

We've had Confluence running for a little while now, and after a few upgrades, it's seemingly fairly stable. It's definitely very very nice looking. We have at least one more upgrade scheduled soon so that Confluence can share authentication information with our Jira instance, making all existing Jira users also Confluence users.

Once again, Atlassian rocks.

Over on my blog, I announced the haus's first birthday.

Well, a year ago today, I registered codehaus.org. Kurt Schrader announced it publically about a week later, but the registrar considers today to be the founding day for the haus.

ThoughtWorks has provided a generous donation to The Codehaus. A good number of the hausmates are ThoughtWorkers and many of them hopped over to the continent for the Haus Party. You've got folks like Aslak, Joe and Paul doing super cool things, just to name a few.

blogs.codehaus.org is now running on the new canadian box known as beaver.

Through the miracle of mod_rewrite, mod_proxy, and a complete disregard for bandwidth consumption, the migration should be completely transparent to you even if the DNS changes haven't propagated yet. If your machine thinks that hogshead is still blogs.codehaus.org, then hogshead just proxies requests back to beaver until your machine figures it out.

Holler if you find any problems.

jira.codehaus.org can now accept comments to issues through email. When replying to a mail notification from Jira, if you include jira@codehaus.org on the recipient list, jira will add your email as a comment on the issue. It simply finds the issue key from the subject: header.

Now, all of those conversations started on lists as a the result of a mail from Jira will be saved for posterity's sake.

Search is now available for the assets of The Codehaus.

& may be used as boolean 'AND'
| may be used as boolean 'OR'
~ may be used as boolean 'NOT'

jira.codehaus.org is now running on beaver with lots more RAM and lots of spare of cycles. It's zippy.

builds.codehaus.org is back online, running damagecontrol. Drools, Groovy, and various Pico projects are being damagecontrolled.

Index of /

Now that we've given our beaver some latex, tirsen is ensuring that all drooling damage is noted.

<dcontrol> BUILD SUCCESSFUL drools

Okay, turns out we had some mixed up forms on the blogs, which effectively disabled comment submission. I've ironed out the problem and am percolating the changes out to everyone's blog. Comments should start flowing again.

I'll start adding user accounts and services over the next week or so.

Total of 4 processors activated (24484.24 BogoMIPS).

For Vincent, I've now correctly installed the CodeBeautifier plugin for MT. To use it, encase your code in a <code> block, toss in a language="java" type of attribute, and away you go. You'll have to turn Text Formatting to None instead of Convert Line Breaks. For example, typing this...

<code language="java">
public class VincentMassol 
  extends Hausmate
{
  public String cheese = "gouda";
}
</code>

will yield this:

public class VincentMassol 
  extends Hausmate
{
   public String cheese = "gouda";
}

Tentatively named beaver.codehaus.org in honour of our Canadian friends who are dealing with it, the new box is on-hand now. Ended up not going with the 80gb raid since the controller wouldn't fit into the 1U enclosure. Dave will begin the base installation this weekend, and then we'll set about adding all of our packages etc. It should be in the rack an online within the week, though it'll be longer before we migrate all users and services to it.

The new machine has been ordered, and should be delivered to one of our northern hausmates by the end of the week. Sometime between then and New Year's, the box will be installed in a rack at Sentex (Canada). I've scheduled about 2 months to migrate everything off hogshead and onto the new box. And thus, the new box needs a name. We've been following an alcohol-theme, with hogshead, falstaff, stout, and ale. Specs of the new machine are:

• Dual 3ghz Xeon processors
• 4gigs of RAM
• GigEther
• 120gb SATA drive
• 80gb RAID

We'll be unifying pretty much everything, including damagecontrol onto that machine; it needs a name to match its importance.

In the continuing effort to improve outbound haus communication, we've now created nice categories for the Haus News, and each category is individually syndicatable. For example, you can point your aggregator to the releases feed (rss or html) and learn of new releases as they are announced. This entry, for reference, is available on the administrivia feed (rss or html).

We've finally gotten the Codehaus Manifesto online, along with a slight redesign on the sites.

The manifesto is of course not static but subject to change as needed.

Finally hooked up some nice aggregators.

We've got the general hausmate blogs feed to gather the wisdom (or otherwise) of the hausmates, whereever their blogs may lie.

Then we've got the jira feed to watch what's going on at the haus across all projects we tends through our Jira instance.

Plus, we're now hosting the mavenblogs feed.

Pete Kazmier and Ben Walding did some designs for a logo, which Rebecca McWhirter tweaked and polished, resulting in...

Slowly, but quite certainly we're getting The Codehaus Buildmeister online for doing continuous and/or nightly builds of hausprojects. Ultimately, it'll be 4+1 boxes (4 slaves, 1 master). Mad props to Jon Tirsen for helping configure them. Access to the buildmeister is limited at this time, but project leads may contact a despot for information on how to get into it.

After some nudging from Aslak, CVSgraph has been installed on the web CVS server.

For example...

Codehaus Chores has been created in Jira as a way to manage administrative requests.

Got the blogging system set up today.

MovableType is now available for hausmates or projects.