welcome: please sign in

The following 412 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
able   about   above   Abuse   access   account   across   act   acting   add   Add   address   administrator   administrators   admins   Advising   agrees   alert   all   allowance   almost   also   always   among   an   and   answering   any   anyone   approved   apt   archive   are   aren   arrangements   arranging   articles   as   assignment   associated   at   At   auditing   autonomously   awake   barring   base   basis   be   because   been   behalf   behind   board   Both   brief   but   by   bylaws   can   categories   category   charge   clear   co   come   communication   Conduct   containing   contrast   Coop   could   course   covers   cracking   created   critical   database   day   decision   default   defined   delegated   deserving   Despite   different   differentiated   direction   directors   Distribution   Do   do   documents   does   Domain   domain   down   duties   each   Each   elected   elections   emergencies   enabled   evenly   everything   exactly   except   expect   expected   expects   expulsion   extent   extreme   fairly   files   Financial   financial   firewall   first   for   forbidden   formal   from   general   give   goes   good   ground   grounds   guidelines   handle   Handle   handling   has   have   hcoop   he   helping   high   him   his   hours   How   http   Hunt   ideas   If   if   immediate   important   in   incorporation   infrastructure   installation   interests   involved   is   it   It   jobs   just   keep   Keep   know   knows   large   larger   law   lead   leadership   legal   legitimate   less   Let   like   likely   list   listed   lists   mail   Mailman   Maintain   Maintaining   make   Make   makes   making   Manage   many   matters   may   meet   meeting   meetings   member   members   membership   Meta   might   minutes   Misc   money   moral   more   Mostly   necessary   need   net   new   nice   not   Note   notification   number   Of   of   office   officers   Official   official   often   on   one   ongoing   only   op   operations   or   order   organized   other   our   own   package   packages   pad   page   pages   paid   Pal   paperwork   particular   particularly   Pay   payment   payments   Pennsylvania   people   performed   Periodically   person   physical   pick   plan   policies   Policies   Policy   policy   portal   possible   possibly   Post   post   power   powers   president   President   privacy   private   privileges   probably   Process   processing   progress   Protecting   questions   quite   rare   real   reason   records   related   relational   reliability   report   represents   requests   Requests   requirement   requirements   Requirements   respecting   Respond   response   Response   responsible   results   right   role   roles   root   Run   running   same   scale   scans   Schedule   scratch   Secretary   secretary   security   See   seems   Send   sent   Server   servers   services   set   setting   should   sign   since   single   situations   so   some   somehow   someone   special   specific   spread   status   strictly   stuff   subordinate   Summaries   superuser   support   Sysadmin   sysadmin   sysadmins   Sysadmins   System   Task   task   tasks   technical   tend   termination   than   that   That   The   the   their   them   then   they   this   This   though   through   tickets   time   times   to   Tool   total   transcripts   treasurer   Treasurer   try   turn   types   ultimately   under   up   update   updating   us   use   used   vacation   via   view   Volunteer   volunteer   votes   want   way   We   we   Web   webpage   week   what   whatever   when   whenever   where   which   who   wiki   will   willing   with   within   won   would   zones  

Clear message


If we want to scale up to a larger member base and high reliability, then we need to know exactly what is expected of people who volunteer for particular duties. That way, someone can turn down a role if he knows he can't meet the time requirements, and he knows exactly what is expected of him if he does sign on. This page is our scratch pad for ideas on formal guidelines in this direction.

See the TaskDistribution page for an in-progress assignment of people to jobs.

1. Policies deserving their own pages

2. Summaries of official roles and their duties

3. Requirements of anyone in an official role

4. Sysadmin stuff

How many sysadmins (all with root access) should we have? 4 seems like about the right number. It would be nice if we could somehow pick admins with good spread across the different time zones, to give us more times when one is likely to be awake and able to handle emergencies.

It might be nice for each sysadmin to have brief "office hours" each week, where he agrees to be on IRC answering questions and helping people in real time.

5. Official list of tasks

We should try to come up with a list of task types that covers everything expected of people in special roles. Each task should have an associated list of people in charge of it, listed in a total order. At any time, the first person on the list for a task who is not "on vacation" via the above allowance is responsible by default for handling it. Of course, it's always possible to make special arrangements for some tasks, but the lead person for the task will be in charge of arranging them.

I expect that the tasks of the officers (president/secretary/treasurer) will almost always be performed by single officers, since they will tend to be less time-critical. The sysadmin tasks should probably be spread evenly among the sysadmins.

Let's list the tasks, organized by which role we expect to handle them.

5.1. President

5.2. Treasurer

5.3. Secretary

5.4. Sysadmins

AdminPolicies (last edited 2008-07-07 04:27:59 by localhost)