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?
Raise your hand if 'ew.'
Buffy ,'Same Time, Same Place'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Zoe Ann - Apr 12, 2003 10:29:32 am PDT #3761 of 10000
Mathair & Athair beo.
Michele T. - Apr 12, 2003 12:18:18 pm PDT #3762 of 10000
with a gleam in my eye, and an almost airtight alibi
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.
P.M. Marc - Apr 12, 2003 12:19:54 pm PDT #3763 of 10000
So come, my friends, be not afraid/We are so lightly here/It is in love that we are made; In love we disappear
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 § - Apr 12, 2003 1:43:41 pm PDT #3764 of 10000
Well not canonically, no, but this is transformative fiction.
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:
- Jon and I have access to the test site, code, and database.
- I have access to trouble ticket submission
- I have access to production code and database
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.
Michele T. - Apr 12, 2003 2:11:04 pm PDT #3765 of 10000
with a gleam in my eye, and an almost airtight alibi
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?
§ ita § - Apr 12, 2003 2:19:07 pm PDT #3766 of 10000
Well not canonically, no, but this is transformative fiction.
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.
Michele T. - Apr 12, 2003 2:21:15 pm PDT #3767 of 10000
with a gleam in my eye, and an almost airtight alibi
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...
§ ita § - Apr 12, 2003 2:24:14 pm PDT #3768 of 10000
Well not canonically, no, but this is transformative fiction.
For admin planning you mean setting up code control? I think we should do that here -- folks who haven't volunteered to code (and are therefore not going to want to be on the list) may have good ideas.
But, at the moment, Paul is code control until bitterchick gets a yay or a nay on her system.
Michele T. - Apr 12, 2003 2:27:10 pm PDT #3769 of 10000
with a gleam in my eye, and an almost airtight alibi
Code control, creating a process or a project plan, anything like that that needs doing, I meant.
And, just cause you didn't mention it and I want to make sure I understand everything (I've got a headcold and am a bit off my game), we'll be able to move to a group coding methodology once we're off HR?
§ ita § - Apr 12, 2003 2:31:16 pm PDT #3770 of 10000
Well not canonically, no, but this is transformative fiction.
we'll be able to move to a group coding methodology once we're off HR?
It's not the group coding that's the HR-prevented issue. It's the group being able to update production (which is fair -- needs to be a choke point there), and the group being able to submit trouble tickets or do techy sysadmin stuff.
The reason we have no group coding controls in place is a lack of a CVS system (Karl seems to be too swamped to pop his head up, poor guy, but he was the resident expert who had a running system).