This document is meant to describe the technical steps in making a
member out of a prospective.

It's not necessarily authoritative; consult the secretary with questions.



For the new member to read/learn
--------------------------------

new-member doc:
  we have information for them in /afs/sipb/admin/secretary/new-members-blurb

passwords:
  they should learn the office root password,
  and the sipb0/sipbn/sipbcert password

SIPB policy:
  Make sure they read /afs/sipb/admin/text/policy/*



Lists
-----

members_and_prospectives:
  Update the members_and_prospectives file
  (/afs/sipb/admin/office/members_and_prospectives).

website:
  Add them to http://sipb.mit.edu/members/.

moira changes:
  blanche sipb-members -a $person
  blanche sipb-private -a $person
  blanche gsipb -a $person
  blanche sipb-prospectives -d $person



Bits
----

the sipb afs cell:
  The new member gets a sipb-cell homedir.  Their -c sipb pts id
  should be the same as -c athena; sipb-afs-sync should create this
  automatically once they're on LIST:gsipb, if it didn't already
  because of some project list.

keys:
  notify Jane that they'll be getting keys

login acls: 

  Athena 10 / Debathena office heads should have gsipb on the
  remote-login acl and in sudoers, so no further work is necessary.


  The new member should understand the social policies around logging
  into office heads remotely: the person sitting at the head owns it,
  so ask and be polite.


  For Athena 9 office heads, the new member should be added to
    /afs/sipb.mit.edu/machine/office/common/passwd.add 
  and then someone who knows what they are doing (possibly the new
  member) should run /afs/sipb.mit.edu/machine/office/bin/syncsipb as
  root on each office head of interest and copy over passwd to
  passwd.local (but not clobbering anyone else who might be logged
  into the machine.)

  If they want to be added to root's klogin, they should get a root
  instance from accounts and get it added to
  /afs/sipb/machine/office/common/klogin (and then run the syncsipb
  script mentioned above).

  changing these files requires gsipbbin permissions, not something
  everyone has



Miscellaneous
-------------

multics:
  If you want to be able to ssh into multics (sipb's private dialup),
  send mail to multics-maintainers.

discuss:
  The discuss meeting ACLs are now based on the moira lists, so
  manually modifying the ACLs is no longer necessary.  The meetings
  remain listed here for reference:

 charon:/usr/spool/discuss/sipb (sipb-members@mit.edu)
 charon:/usr/spool/discuss/sipb-ec 
 charon:/usr/spool/discuss/sipb-staff
 charon:/usr/spool/discuss/sipb@mit.edu