Official Description
====================

The Secretary shall keep records of all meetings, shall direct all
necessary correspondence, shall be charged with maintaining general
office records and files, and shall keep records pertaining to the
current active or inactive status of all members.

Right After You're Elected
==========================

- Have yourself added to sipb-ec, since you're a member of the SIPB Executive
  Council

- Have yourself added to sipb-acl, so that you can put people on sipb-members
  after they've been elected.

- Get added to the ASA signatories list as a Reservations and Financial
  signatory.
  http://web.mit.edu/asa/www/asa-db.shtml

- Go get your signature added to the list of people who can sign SIPB
  requisitions and view SIPB's account view SAPGUI.


All The Time
============

- Maintain a list of active members.

- Take minutes at SIPB meetings:
  * General
   - the minutes are stored in /afs/sipb/admin/minutes/
   - there's a minutes.el file there to make things easier
  * For each meeting
   - be at the meeting 10 minutes early to bump someone off a computer
     and start the attendance
   - take minutes during the meeting
   - after the meeting, clean up the minutes, ask people for clarification,
     fix spelling errors, etc.
   - send the minutes out to sipb-minutes with a clever subject
   - if people reply with corrections, correct the minutes in afs.

For new members:
- send mail to oisfinance@mit.edu CC'ing the new member requesting a key
  and asking them to figure out a time to pick up the key.
- add them to gsipb, sipb-members, and sipb-private
    for i in gsipb sipb-members sipb-private; do blanche -a $NEWMEMBER $i; done
- make sure they end up in the gsipb pts group in the sipb afs cell
  (which, at least automated, involves sending mail to sipb-afsreq)
- add them to
    /afs/sipb/machine/office/common/passwd.add
- change their status in
    /afs/sipb/admin/text/members/members_and_prospectives


Notes: from jmorzins:

They can be added to the moira group gsipb by any normal people.

They should also be added to system:gsipb -c sipb, but this must
be done by a sipb afs administrator.


There are a couple other things that can also be done:
if the person wants to log into office machines remotely, they
can be added to /afs/sipb/machine/office/common/passwd.add

After being added, they will need to run /afs/sipb/machine/office/bin/syncsipb
(run it as root, on each machine...)

If they want to be able to "ksu" to root on an machine, they also
need to add themself to the /afs/sipb/machine/office/common/klogin file.
(And, after being added, will again need to run syncsipb on each
office machine, as root.)

In order to have a <USERNAME>.root@ATHENA.MIT.EDU entry in the
klogin file, the person will have to have a kerberos root instance.
Athena user accounts, or mit server operations can, create
kerberos root instances.  This allows them to run "ksu", and
become root using their special password, instead of using their
normal password.

New members should get sipb cell home directories.