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/sipbtest/sipbexch password SIPB policy: Make sure they read /afs/sipb/admin/text/policy/* Lists ----- moira changes: blanche sipb-members -a $person blanche sipb-private -a $person blanche gsipb -a $person blanche sipb-full-members -a $person blanche sipb-prospectives-$year_prospectivized -d $person members_and_prospectives: Update the members_and_prospectives file (/afs/sipb/admin/text/members/members_and_prospectives). This could be done using emacs (as we are still using RCS to maintain it). Open it up, do C-x v v. Do the changes, C-x C-s and then C-x v v to start the commit process; type the commit message and then do C-c C-c to actually commit. Alternatively, you could use the vanilla RCS commands. First, checkout the file using `co -l ./members_and_prospectives`. Then, make your edits with your favorite text editor (*ahem* Vim *ahem*). Finally, check in your changes with `ci -u ./members_and_prospectives`, enter the commit message, and end it with a single period on a line. website: Add them to https://sipb.mit.edu/members/. Bits ---- the sipb afs cell: Email sipb-afsreq@mit.edu to get the new member a sipb-cell homedir. Their -c sipb pts id should be the same as -c athena; sipb-afs-sync should create the pts id (not the homedir) automatically once they're on LIST:gsipb, if it didn't already because of some project list. keys: Mail enablingservicesfinance@mit.edu and ist-blt@mit.edu requesting a key, and CC the new members, sipb-ec@mit.edu, and (if necessary) sipb-secretary@mit.edu asking for when they can come in to pick up the keys. Githubs: Add them to the sipb organization on both github.com and also github.mit.edu, and make sure to add them to the Keyholders team. login acls: Debathena office heads should have gsipb on the remote-login acl and in sudoers, so no further work is necessary. If gsipb isn't on `hesinfo $USER grplist`, then follow the Athena 9 procedure below for the Debathena boxes to allow remote-login. (Unfortunately, there no existing fix for sudoers; just add yourself to the local sudo group if you want to be able to sudo.) 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. Also note that these files need to be checked out and checked into RCS (see the instructions earlier in the document). 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