Matt Sergeant wrote:
I'm personally in no hurry to do this, but it depends what the community thinks.
I'm in no rush, either. There are several things to consider:
First, we've chosen not to use the resources provided by the ASF so that we can publish AxKit's public site *using* AxKit. I still think its the Right Thing(tm) for us to eat own dog food (and that means hosting elsewhere), but we shouldn't forget that we have the option available.
Also, precisely *because* we eat our own dog food, its doubly important that axkit.org be attentively maintained. Frustrating users is bad enough; saying "our way is better" then presenting them with a b0rken site just plain makes us look bad.
Reality is that the situation has changed from when things were set up initially. More people are using AxKit than ever, and so the consequences of axkit.org being down are greater. Hosting axkit.org on Matt's box (and expecting him to be Johnny-on-the-spot when things go wrong) provided a key resource when we needed it, but I think that both our needs and the expectations of our users have outgrown the current environment.
Mike Nachbaur's offer is a generous one, but I've always been leery of relying on work resources for community projects (some PHB gets a wild hair and *boom* the site is down for weeks while we find something else). Maybe we need to explore the what's and what ifs before accepting or declining.
Paid hosting/colo is another option; but then where does the $$ come from? Us? donations? As an ASF project, can we even legally accept community donations? Beyond that, there are the companies that offer AxKit hosting, maybe we can weasel free host...er, I mean, work something out with one of them.
Anyway, there really is no need to rush this unduly, but I do think we have grown to the point that we need to start looking for more robust options.
-kip
