[[!meta title="SIPB Documentation Project"]]

The SIPB Documentation Project is a project to document in written
form the collective knowledge that SIPB members take for granted or
use in maintaining services and projects that are not otherwise
written down anywhere.

See [[SIPB Documentation|/doc]] for documentation produced so far.
Existing documentation can always be improved.


See [[Project Ideas|doc/project-ideas]] for stuff to try doing to
further the goals of the SIPB.

<!-- See LennyBugs and LennyBugsAll for the bugs we took on in the Lenny
RC-bug-squashing hackathon of December 13, 2008. -->


## Documentation Ideas

This is a partial list of further topics that need documentation.
Additions welcome.

 * "Printing at MIT"
   * `lpq`, `lprm`, `queues.mit.edu`
   * `-i printadm` (maybe)

 * "Using Debathena" -- You've installed Debathena -- now what?  Automounter, `blanche`, cups; using stuff in the GUI.
 * "Athena Dotfiles" -- These are weird and nonstandard compared to traditional UNIX and should be documented, including things like `.environment`
   * There's some documentation at [http://web.mit.edu/olh/Dotfiles/]

 * scripts.mit.edu -- lots of neat internals to explain

 * AFS: There should be a central documentation point to using your
   AFS space, granting access through AFS and through `web`, accessing
   files from various platforms, and so on.  Don't duplicate iAFS;
   perhaps latex2html and update it.

 Setting up servers:

 * "Client Certs" should explain, if for some perverse reason you don't
   want to use scripts.mit.edu :-), how to set up client cert
   authentication on your own machine (grab the CA out of the
   apache-ssl locker, submit a CSR to mitcert@, set up scripts' magic
   Apache modules to make your life easier)

 * Add your own here!


## Useful Links

 * [[ikiwiki/Formatting]] -- Documentation on this wiki's formatting language