Which brings up a point. I've been approached by some PF refugees about porting this code for their use.
How does the community feel about this?
'Beneath You'
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
Which brings up a point. I've been approached by some PF refugees about porting this code for their use.
How does the community feel about this?
ita, I'm a techno-moron, so whatever you and this community decide, I'll stand and nod.
It isn't my work; it belongs to you who spent so much sweat on it.
If you wanted to open-source it, I'd applaud you. But if you don't, you're entitled.
If you port it, my tiny theater board would also be interested.
As a community member, I don't really mind if the board-look is duplicated. However, if that means that they'll be coming to you with problems, I'm firmly against it. Basically, whatever's easier for the coders, stompies, and other peeps.
Last time the subject came up, which was pretty soon after the board opened, you guys were ooky.
As far as I'm concerned, it's pretty much up to the people that built it.
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.
I see it as something where anything that's done to improve the code for anyone else comes back here
Oh, yeah.
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.