Forum OpenACS Q&A: Re: organize openacs.org!
I still think we should have a publically visible "How to maintain openacs.org" doc though. (Maybe Furfly already has some of that sort of stuff for their own and clients' use?) It can say at the top that Furfly is responsible for sysadmin stuff, call them, etc., or whatever. But we should still have a document with up-to-date, accurate info explaining everything someone might need to know about the box, about maintaining the website, about who is responsible for what, etc. Note that this is not at all just sysadmin stuff, although certainly a significant amount of it is, but rather, everything specific we need to know about the infrastructure to maintain, debug, etc. openacs.org. Comments?