Differences between version 36 and revision by previous author of WlugSysadmins.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 36 | Last edited on Tuesday, January 12, 2010 4:04:00 am | by AristotlePagaltzis | Revert |
| Older page: | version 35 | Last edited on Monday, January 11, 2010 10:26:11 pm | by JohnBillings | Revert |
@@ -31,15 +31,15 @@
If you would like to become an admin, first you'll need an account on hoiho, so contact the Secretary about that. After that you will need to talk to another admin, 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 you're finished, (and what you did)
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, and tell us what you did
.
!! Going Forward
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.
-That being said, new admins should always look at how they can build on past work, rather then initiating some new project, working on it for awhile
, getting bored with it and sodding off. If your
not going to take the time to learn how the system was engineered in the first place and what it's
intent was, then we really can't use your contribution. There is still room for new development projects, but not if a system in place already just needs to be improved.
+That being said, new admins should always look at how they can build on past work, rather then initiating some new project, working on it for a while
, getting bored with it,
and sodding off. If you're
not going to take the time to learn how the system was engineered in the first place and what its
intent was, then we really can't use your contribution. There is still room for new development projects, but not if a system we have
in place already just needs to be improved.
!! 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.
