A thread to discuss naming threads, board policy, new thread suggestions, and anything else that has to do with board administration and maintenance. Guaranteed to include lively debate and polls. Natter discouraged, but not deleted.
Current Stompy Feet: ita, Jon B, DXMachina, P.M. Marcontell, Liese S., amych
My tentative opinion is that I'm okay with it. However, the back end's not ready for prime time, so it will involve me being uberadmin wherever it is.
HOWEVER, and this is something we need to check (I'll need Tom's help) the code may still be spiking the CPU cycles. That has to be cleared up definitely before it goes anywhere.
If it is okay, I see it as something where anything that's done to improve the code for anyone else comes back here, even if it's something I (or others) am/are paid to do with this code here.
Does that seem fair?
Last time the subject came up, which was pretty soon after the board opened, you guys were ooky.
I was one of the folks who suggested it, and yeah, a number of folks were against it at the time. I'm still in favor. You probably want to look into some sort of open-source licensing to protect it from being swiped by unscrupulous sorts.
I was also thinking that perhaps we should look into setting up some sort of backup hosting somewhere, putting a copy of the code on it, and using that as our contingency plan in the event we go down.
You probably want to look into some sort of open-source licensing to protect it from being swiped by unscrupulous sorts.
The original suggestion that ooked me was just handing over the code and walking away. I'm still weirded out by that. The version where I'm still back office, and can nurse the puppy -- I'm okay with. And until it was weaned, I think it would be borrowed code.
Not that that'd stop the unscrupulous, but it wouldn't be distributed, per se.
t feels feet slipping out from under her into the mysterious dark end of geekness
Uh ... OK. What ita says.
I was also thinking that perhaps we should look into setting up some sort of backup hosting somewhere, putting a copy of the code on it, and using that as our contingency plan in the event we go down.
I think this is a good idea. Maybe a streamlined, easy-maintenance version with limited threads.
A copy of the code and the user database, I'm guessing. And the database will need to be periodically manually refreshed from the master one.
Right, and to make things easy, we could point buffistas.com at it.
I'll need to check the referrer logs, to see how many users we have coming in from buffistas.com to org. Though, we could still have .com bounce to .org unless case of emergency and all that. But that means Tom or I (as things stand) would need to be the ones to break the glass.
Gus pointed out over in Firefly that we're just a little over 100 posts from the end of that thread. One suggestion is "Firefly 4: Also, we can kill you with our brains" originally suggested by Allyson here
Allyson "Firefly 3: Too Damned Pretty to Die" Dec 1, 2004 11:30:15 am PST
and then modified by tommyrot to add the "Also" here
tommyrot "Firefly 3: Too Damned Pretty to Die" Dec 1, 2004 1:37:21 pm PST
Just wanted to say I vote for it.
