Parker Peters wrote:
Do you risk maintaining old procedures, which once
worked quite well but are starting to buckle under the weight, or do you experiment with something new and untested?
I would hope we risk the new and untested procedures, but I've rarely seen a new policy or procedure pass unless it actually increases admin power while decreasing admin responsibility.
Being new by itself is not an adequate reason for adopting new procedures. The transclusion templates have been a big favorite among the geeks, but making editing difficult for everything else. I suppose you could say that that makes them admin friendly
These are some of the real issues that Parker Peters is raising. Note that
they are dilemmas, and the nature of a dilemma is that there is no right answer, except perhaps from the safety of hindsight. And yet, decisions have to be made.
Yes, decisions have to be made. I've made a few suggestions today that I hope will be taken seriously:
#1 - the creation of a "mini-admin" or "first grade" admin position, as a "training wheels" step for new admins, so that they have some power but not the total power an admin today has, to minimize the damage they can do while allowing them to learn the role of an admin.
That would be fine if the problem were purely technical, but I don't think it will accomplish much in dealing with jerks.
Ec