To the extent feasible, system administration policies applicable to this "box" (host/system) are to be documented here.
Note that occasionally there will be some items more appropriately documented elsewhere. E.g. security sensitive information that shouldn't be openly readable to the Internet, or items that may be important to have access to when the wiki isn't available (e.g. critical maintenance related information). In general, items which shouldn't be documented here on this wiki but should be documented in local files under file:/home/admin/ - or at least referenced from there.
To the extent feasible, this document should cover current policy, "rules of the road", etc. To the extent it's covered, historical, outdated, superseded, etc. information should be covered separately (and to the extent feasible, presented in a manner unlikely to cause confusion with current policy and "rules of the road", etc.)
There are multiple objectives for this system. At least at times, these may appear to conflict. This list is intended to identify key objectives, and in the case of conflict or potential conflicts, their priority (or at least approximate priority), with highest priority (most important) first. Also, first, bit of "policy" update … but may be more theoretical (e.g. conflicts with physical reality & resources available at the time of this writing) - and may also, to fair extent, be relatively SF-LUG specific:
Date: Tue, 24 Nov 2015 22:10:12 +0000 From: jim <firstname.lastname@example.org> Policies: * The host of the sf-lug web site is a Linux machine or virtual machine dedicated to running the sf-lug web site only. A "different host" may refer to another VM running on the same physical host as that which supports the sf-lug web site. * the sf-lug web site itself should be static, with no interactive software, for ease of maintenance and security; it is essentially an internet-accessible yellow page style advertisement. * The sf-lug web site can include links to interactive web pages, although properly such interactive pages should be hosted on some different host other than that which hosts the sf-lug web site (for easy maintenance and security). * the sf-lug web site host should be open to sf-lug supporters for whatever they want to try out. "Trust is efficient." We assume no user will alter work done by other users. We assume users will make mistakes, even hork the host itself, and that users will use sudo rather than the root account to make changes (exceptions to this include Michael Paoli and Jim Stockford and whoever else can get Jim or Michael to approve). Preferably users should experiment on a host other than that which runs the sf-lug web site itself. * Jim wishes to deprecate PHP on the host that supports the sf-lug web site. Jim has no power to enforce this. Jim prefers shell scripts, C, and Python. Jim's authority derives from his paying for domain name, electrical power, bandwidth, and other costs. To the extent that other people pay such costs, they derive authority.
Access to and use of the system should follow appropriate code of ethics, e.g. the LOPSA/SAGE/USENIX code of ethics: