Zoe, you're mistaken. There was no "database checking", and as much as I love both help and Nora, the two didn't intersect.
You'll have to make the thesis of your Nora Fan Club something different, I fear.
Giles ,'Lies My Parents Told Me'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Zoe, you're mistaken. There was no "database checking", and as much as I love both help and Nora, the two didn't intersect.
You'll have to make the thesis of your Nora Fan Club something different, I fear.
OK. Someone did make the claim over on People's Forum. I didn't realise it was contraversial. Shall I retract the applause?
Could you provide a link to the post you're referring to? I don't remember seeing it.
No. I checked back to try and find it but couldn't. There is one deleted post which could be the same one.
I didn't halucinate the post, I recall reading it.
What is the point I am missing here please?
The point is that ita does all the database work.
Which could, in itself, become a problem. Not that ita isn't a goddess, but that, as the demands of the site grow, ita can't scale.
Not that ita isn't a goddess, but that, as the demands of the site grow, ita can't scale.
I suppose clones are right out...
ita, does Jon have the keys in case of emergency?
ita, does Jon have the keys in case of emergency?
Jon has the mental keys (PHP, and working on SQL), but not the literal keys.
So far things are segmented thus:
This might later be moot, but part of the problem is how stuff is segmented. I have more keys than I want, because of how the passwords are set up. I don't want anything that buts onto the financial having the account stuff -- that's all Jesse. And the keys to the production code ARE those keys.
There needs, IMO, to be a separation between the tech and the account admin (CC info, etc). Because I'm already leery of how much I've had to blur the lines, I'm hesitant to propagate that.
Perhaps, in the not too distant future, that can be remedied.
And no, I don't scale. Not at all.
What can be done to separate the tech and account stuff more?
What can be done to give more people with skilz access to the ticket list, test site, and code?
What can be done to separate the tech and account stuff more?
Nothing. That's HR's setup issue. No -- I think the production DB has a separate ID/password.
What can be done to give more people with skilz access to the ticket list, test site, and code?
Ticket list -- nothing, as above. Test site and code ... really if people want to READ, I can hand out the user ID and password like candy. It's what I was going to do after we have code control in place, anyway. But really, really, until we have a system, there's no room for experimentation or development by more than one person at a time.
And we'll get a system once we're off HR, because it's their issue, yes?
Is there any administrative planning we can do for this in advance? I know there's a so-far-unused devlist -- perhaps that would be the place to do any such planning work...