ObjectWeb Portal

Hi folks,

Another topic for discussion: Barracuda has been accepted as a project at
ObjectWeb. We need to decide exactly what that's going to look like.
Specifically, they'd like us to move everything to their project servers.
I'd prefer not to go quite this far, since:

a) the community pitched in to buy our own machine, and I'd hate to just
abandon that
b) there really are advantages to having our own machine in terms of running
sample apps, etc - we can control the environment, and upgrade
libraries/software as needed, without having to worry about breaking someone
elses apps
c) the whole protection issue (this was more of a concern with Lutris than
OW, but the same prinicple still applies - if the sponsor goes away or gets
nasty, and you have your own server, its no big deal)

So I've basically been thinking that we continue to run everything off of
http://barracudamvc.org, and just mirror the cvs source tree over at
ObjectWeb. Of course that means we have to figure out what's causing our box
to crash and fix it. And we also need to get mail archiving set up. And get
daily build working. etc. In short, we still have some work to do on the
Barracuda box, and we're particularly short on time right now. And as you
can see below, OW has quite a bit of infrastructure, plus people who support
it (so we don't have to).

An alternate strategy might be to move a lot of the infrastructure stuff
_off_ of the Barracuda MVC box (like email, archiving, searching, etc), but
continue to host docs and sample apps on our own box. So the gist of all
this is I'm looking for input...what do you think of the ObjectWEb setup,
and what would you recommend for us to leverage?

Shawn, Denny, Jake, and Diez in particular should chime in here...

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"