User talk:Sean William/January 2008

I am leaving you this message because recent events have given me concern. When Aaron Brenneman and I, and others, first developed this category well over a year ago, we visualized it as a simple idea. A low hassle, low bureaucracy process. We also visualized it as a process that people would come to trust, in fact as a way of increasing trust in those admins who chose to subscribe to the notion of recall. The very informal approach to who is qualified to recall, what happens during it, and the process in general were all part of that approach.

But recent events have suggested that this low structure approach may not be entirely effective. More than one of the recent recalls we have seen have been marred by controversy around what was going to happen, and when. Worse, they were marred by some folk having the perception, rightly or wrongly, that the admin being recalled was trying to change the rules, avoid the process, or in other ways somehow go back on their word. This is bad. It's bad for you the admin, bad for the trust in the process, and bad for the community as a whole.

I think a way to address this issue is to increase the predictability of the process in advance. I have tried to do that for myself. In my User:Lar/Accountability page, I have given pretty concrete definitions of the criteria for recall, and of the choices I can make, and of the process for the petition, and of the process for other choices I might make (the modified RfC or the RfAr). I think it would be very helpful if other admins who have voluntarily made themselves subject to recall went to similar detail. It is not necessary to adopt the exact same conditions, steps, criteria, etc. It's just helpful to have SOME. Those are mine, fashion yours as you see fit, I would not be so presumptuous as to say mine are right for you. In fact I urge you not to just adopt mine, as I do change them from time to time without notice, but instead develop your own. You are very welcome to start with mine if you so wish, though.

But do something. If you have not already, I urge you to make your process more concrete, now, while there is no pressure and you can think clearly about what you want. Do it now rather than later, during a recall when folk may not react well to perceived changes in process or commitment.

Further, I suggest that after you document your process, that you give a reference to it for the benefit of other admins who may want to see what others have done. List it in this table as a resource for the benefit of all. If you use someone else's by reference rather than copy, I suggest you might want to do as Cacharoth did, and give a link to a specific version.

Do you have to do these things? Not at all. These are suggestions from me, and me alone, and are entirely up to you to embrace or ignore. I just think that doing this now, thinking now, documenting now, will save you trouble later, if you should for whatever reason happen to be recalled.

I apologise if this message seems impersonal, but with over 130 members in the category, leaving a personal message for each of you might not have been feasible, and I feel this is important enough to violate social norms a bit. I hope that's OK. Thanks for your time and consideration, and best wishes.

Larry Pieniazek

NOTE: You are receiving this message because you are listed in the Wikipedia administrators open to recall category. This is a voluntary category, and you should not be in it if you do not want to be. If you did not list yourself, you may want to review the change records to determine who added you, and ask them why they added you.