Talk:Computer Operations/sandbox
m |
m |
||
| Line 1: | Line 1: | ||
Rob, you have listed that the passwords should never have to be changed. Why? If anything is going to change frequently, that'll be it. Members of course should change it and I can set it so that when a CC member does it, it's a reset with a notice going to the member that their password is reset and give them the new password. | Rob, you have listed that the passwords should never have to be changed. Why? If anything is going to change frequently, that'll be it. Members of course should change it and I can set it so that when a CC member does it, it's a reset with a notice going to the member that their password is reset and give them the new password. | ||
| + | |||
| + | Also why do we want to allow branch heads to promote? Are we giving them the ability to promote over a CO's head? Not a problem for me per se' just making sure we want to. | ||
| + | |||
| + | I think joindate and username are two items we should not set as easily cahngeable even by the CC. Joind date should be something that never changes. The odd mistake can be changed in the raw DB. short of a marriage, the same principle works for the username. | ||
Logan | Logan | ||
Revision as of 04:29, 15 November 2007
Rob, you have listed that the passwords should never have to be changed. Why? If anything is going to change frequently, that'll be it. Members of course should change it and I can set it so that when a CC member does it, it's a reset with a notice going to the member that their password is reset and give them the new password.
Also why do we want to allow branch heads to promote? Are we giving them the ability to promote over a CO's head? Not a problem for me per se' just making sure we want to.
I think joindate and username are two items we should not set as easily cahngeable even by the CC. Joind date should be something that never changes. The odd mistake can be changed in the raw DB. short of a marriage, the same principle works for the username.
Logan
