>> While having documentation of the setup is essential, I don't think >> making that documentation available outside the group of >> administrators is a good thing to do.
Martin> I disagree. Administrators tend to forget where the information Martin> is stored, and how to access it; they are also uncertain as to Martin> whether certain aspects are documented at all. Giving Google Martin> access to this information (or any other search engine) Martin> simplifies maintenance. I agree with Martin. I do very little actual maintenance, only of the SpamBayes setup on mail.python.org. That's about all I can ever remember how to do. Heaven help you, for instance, if you ever need me to update someone's ssh pub key. :-) At the very least, if I am the last resort available, I know I can poke around the wiki to figure that out. A compromise might be to use Google docs to share this information between just the admins. Or create a RotoRooters group on the wiki and add appropriate ACLs to the root page(s) on the wiki. The Google Docs solution would also have the advantage that, just like the roto-rooters email alias, it doesn't depend on any of the python.org infrastructure. Presumably, in the face of a significant outage people might still be able to find what they are looking for. Skip _______________________________________________ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www