Differences between version 29 and predecessor to the previous major change of WlugSysadmins.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 29 | Last edited on Tuesday, October 20, 2009 9:02:15 pm | by CraigBox | Revert |
| Older page: | version 17 | Last edited on Friday, May 22, 2009 4:40:45 pm | by JohnBillings | Revert |
@@ -31,9 +31,9 @@
If you would like to become an admin, first you'll need an account on hoiho, so contact ChrisOhalloran about that. After that either let Chris or JohnBillings know, via email why you would like to be an admin, what skills and experience you have, then we will take it to the committee and approve your request and get whatever admin access you need sorted.
!! Being an Admin
-Need something like an AUP for admins. Must agree to respect privacy of others. Can be removed at discretion of the Committee. Please let us know if your
finished, so we can remove your access.
+Need something like an AUP for admins. Must agree to respect privacy of others. Can be removed at discretion of the Committee. Please let us know if you're
finished, so we can remove your access.
!! Going Forward
(turn this into some sort of mission statement)
@@ -41,12 +41,14 @@
The WLUG wiki, and other services have become important resources. This is really cool. They should be treated as production systems, and the admins take care in the maintenance of this system. We should not forget the point though, the people who initiated this project were engaged in self directed learning. A LUG has a number of purposes, and one of them is education. New people should be encouraged to get involved, as users, or as admins of this system if they have some skills, and an idea how to contribute.
!! Setting Goals
-WlugSysadmins,
need to be on board and support the WlugCommittee, who of course serve the WlugCommunity. Our new focus is making Software Freedom Day our signature event, (not like installfests and stuff in the past) and to continue to provide a good educational resource to the local community with our presentations, and to a larger audience via the WlugWiki. The work we do on our infrastructure should support this effort.
+WlugSysadmins need to be on board and support the WlugCommittee, who of course serve the WlugCommunity. Our new focus is making Software Freedom Day our signature event, (not like installfests and stuff in the past) and to continue to provide a good educational resource to the local community with our presentations, and to a larger audience via the WlugWiki. The work we do on our infrastructure should support this effort.
Some ideas:
+* Reorganise the server so that continued operation and access to files relies as little as possible on the availability of any single blade. Ideally it should be possible to connect to the iLO and completely reconfigure (via serial console) or rebuild (via pxe boot and network install) all other blades as long as any one blade is still accessable via the internet.
+* maintain a recent mirror of the wiki on a completely independent virtual server (thanks Rimu!) so that we can quickly restore the WLUG wiki even in a worst-case catastrophic failure of the WLUG server.
* Formalize this group and have a process for new admins to join, basically a screening process.
* An exit strategy if people don’t want to be involved anymore. (Please let us know where you left off, links to docs, remove access, etc...)
* Install a ticket system
* Monthly meetings in #WLUG to get things done
